Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 (Internal Server Error) cant-create-new-server-editable-fields-arent-showing-up #633

Closed
mapl opened this issue Nov 27, 2015 · 31 comments · Fixed by #637
Closed

500 (Internal Server Error) cant-create-new-server-editable-fields-arent-showing-up #633

mapl opened this issue Nov 27, 2015 · 31 comments · Fixed by #637

Comments

@mapl
Copy link

mapl commented Nov 27, 2015

I am having exactly the same issue as posted:

https://community.pufferpanel.com/topic/296-cant-create-new-server-editable-fields-arent-showing-up/

Applied the latest patch but did not correct the issue.

@DaneEveritt
Copy link
Contributor

Did this just suddenly start happening? System information? Errors from the logs?

@mapl
Copy link
Author

mapl commented Nov 27, 2015

I just upgraded to 0.8.3 as described. I am seeing this behavior when trying to create a new server

-A required plugin variable was left blank when completing this server setup.- is displayed at the top of the page and youu see the post error in the crome debugger when entering the page and on every change in the plugin selection

@mapl
Copy link
Author

mapl commented Nov 27, 2015

@DaneEveritt
Copy link
Contributor

Is there anything logged in info.log rather than exception.log? I really can't think of any reason why this would be happening, and the error log provided isn't really helpful at all.

Anything logged in the browser console as well? (Right Click --> Developer Tools)

If you know how to use the developer tools, try to look at the XHR requests for plugin-variables, like below, if not, just see if there are any warnings on it.

@mapl
Copy link
Author

mapl commented Nov 28, 2015

here we go :)

http://pastebin.com/a0kQUbU3

@DaneEveritt
Copy link
Contributor

It is saying there is a server error, but it is also returning the correct information...

What.

@mapl
Copy link
Author

mapl commented Nov 28, 2015

it seems like a nice conundrum :)

@demon-goxa
Copy link

I have the same issue 😰

@DaneEveritt
Copy link
Contributor

@DaneEveritt
Copy link
Contributor

@cwmp @demon-goxa — can you try doing the commands below and then check your info and exception logs after reproducing the bug?

cd /srv/PufferPanel
git fetch
git cherry-pick 13c4122

@demon-goxa
Copy link

The same error 👿
http://pastebin.com/vSkjbkVT

@DaneEveritt
Copy link
Contributor

Can you message me exception--2015-11-30--06-16--17f50b615f.html on the forums please?

@mapl
Copy link
Author

mapl commented Nov 30, 2015

error: could not apply 13c4122... potential fix for #633
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'

git status:

On branch master
Your branch is up-to-date with 'origin/master'.
You are currently cherry-picking commit 13c4122.
(fix conflicts and run "git cherry-pick --continue")
(use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
(use "git add ..." to mark resolution)

    both modified:   src/routes/admin/server/routes.php

no changes added to commit (use "git add" and/or "git commit -a")

Ive removed from the routes.php

<<<<<<< HEAD

13c4122... potential fix for #633

but the issue is the same.. same error...

exception log:
http://pastebin.com/seipHNiB

@DaneEveritt
Copy link
Contributor

@cwmp — it appears your cherry-pick did not work as you might have edited the routes.php file that it is attempting to change.

@DaneEveritt
Copy link
Contributor

Also, I need the info.log not the exception.log

@mapl
Copy link
Author

mapl commented Dec 1, 2015

I reset it back to master and tried checky picked the change..and getting this. Ive never manually touched the routes.php file before.

Sorry, I have no info.log at all

@DaneEveritt
Copy link
Contributor

That is strange, there should be an info log returned. @demon-goxa did you also encounter this after upgrading, or was it after doing a fresh install?

The problem I am having with this bug is that a.) I can't replicate it at all and b.) the stack traces are not leading to any specific file that would be causing it, which is why I was hoping there was an info.log. The Debugger::log function logs to that file, and not to exception.log as far as I know, so it seems like something else is triggering the error. And as @cwmp seemed to have confirmed, there is a response being sent back to the browser, it just have a 500 code attached for some reason.

@DaneEveritt
Copy link
Contributor

@cwmp — I'm wondering if this could be caused by APC. I haven't used it enough to know if that could be the issue, and I'd be surprised if it was. Can you try disabling it and see if that resolves the issue?

@mapl
Copy link
Author

mapl commented Dec 1, 2015

I actually see alot of ..PHP Notice: Undefined property: stdClass::$debugging in... errors in the apache log

more:
http://pastebin.com/BnbeFjXD

@mapl
Copy link
Author

mapl commented Dec 1, 2015

Im sorry, but what you mean with APC?

@DaneEveritt
Copy link
Contributor

The notices are an issue with some of the configuration code, but that wouldn't be causing the error your are seeing. APC (Alternative PHP Cache) is enabled on your system, try disabling it.

I doubt it is the reason for these problems, but it wouldn't hurt to go ahead and disable it.

@mapl
Copy link
Author

mapl commented Dec 1, 2015

Ill give you an overview of the servers php info

http://pastebin.com/2dY548pp

@DaneEveritt
Copy link
Contributor

Can you try running a fresh install of PP on this system and see if the error still occurs?

@mapl
Copy link
Author

mapl commented Dec 3, 2015

I did a complete new installation (deleting Pufferpanel Directory and sql Pufferpanel DB) and have the same error.
because I am using a virtual host on apache on non standard port and with https, I needed to alter the
1.master_url
2.assets_url
3.main_website

to < httpS > instead of < http > in the sql DB because the URL Settings in Pufferpanel irgnores and resets the changes.

After that, I went straight to the < New Server > tab and received the same <500 (Internal Server Error)>

to give

@DaneEveritt
Copy link
Contributor

The AJAX call uses a relative path, it doesn't matter that it is HTTPS.

I'll investigate this more, no idea why it is happening though.

@tecnobrat
Copy link
Contributor

I am also experiencing the same thing, totally reinstalled everything. Same exact behaviour.

@tecnobrat
Copy link
Contributor

If it helps, I'm on Ubuntu 14.04.

@tecnobrat
Copy link
Contributor

I cherry-picked down your changes, and now I have an info.log with this:

[2015-12-02 21-13-52] Klein\Exceptions\ResponseAlreadySentException: Response has already been sent in /srv/PufferPanel/vendor/klein/klein/src/Klein/AbstractResponse.php:397  @  http://mc.tecnobrat.com/admin/server/new/plugin-variables  @@  exception--2015-12-02--21-13--66dc4cca9b.html

@tecnobrat
Copy link
Contributor

Please see the above mentioned PR. Fixes it for me.

LordRalex added a commit that referenced this issue Dec 3, 2015
$response->json sends the response immediately, fixes #633
@LordRalex
Copy link
Member

Please validate the fix works @cwmp

@mapl
Copy link
Author

mapl commented Dec 3, 2015

confirmed! It is working as expected now! Thanks so much! no more errors

git checkout master
git pull

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants