-
Notifications
You must be signed in to change notification settings - Fork 30
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
Internal server error/domain already in use #283
Comments
That's not a bug, this behavior is wanted, since otherwise modsec will cause a memory leak. |
Not quite sure I understand what’s going on here, so the latest tag version has made it so users are unable to modify or add a new host? |
No the changes are done, but because of the connection los (nginx gets killed and relaunched) the frontend reports an error |
you can check the file in your root file system, it is changed, I know not a good solution, but the memory leak of modsec basically made my server freez while reloading nginx |
@dontcrash can you confirm that it gets changed on disk? |
Yes files are changed, not really an ideal solution though :/ |
#296 seems to be caused by the same |
same issue here |
@dontcrash does this issue still persist for you? Since for me, it vanished, after switching from kill to nginx own stop command. |
Will close, since I can't confirm this anymore |
2.10.3+cabf78f
When editing it creating a new proxy host, it tells me there has been an internal server error.
The text was updated successfully, but these errors were encountered: