-
Notifications
You must be signed in to change notification settings - Fork 13
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
unexpected fastcgi_read_timeont parameter appears on line 63 or 66 of the host nginx configuration #58
Comments
So is the issue that your template contains |
no, the problem is different. The algorithm:
At this point, a valid nginx configuration file is created, which already includes the
In script "S":
-save this file.
After that, in fact, on line 66 of the nginx host configuration, a line suddenly appears with the Maybe opening the nginx configuration file from a install script and replacing some of the lines in it is not correct, should I use some special functions? But no information found how to do it in correct way. |
Ah, I think Virtualmin is getting confused by the modification of the Nginx config by an external process in the middle of domain creation. Why not instead do the customization at the end of the creation process, via a post-creation script? See https://www.virtualmin.com/documentation/developer/prepost/ |
Hello!
We use virtualmin api to create domains with custom template and installation script configured.
We use our custom post-installation script to install our web service (similar to installing WordPress product for example)
The problem is: after running the post-installation script from template and modifying the nginx configuration, on line 63 earlier, and line 66 today, an additional line "fastgi_read_timeout 60" unexpectedly appears o_O
After we noticed this bug, we counted the lines and left empty and commented lines 63-66 in our nginx config template and removed from nginx confiuration the original fastgi_read_timeout parameter to avoid parameter duplication. So it allows the system to work, but does not solve the bug.
The installation script executes after creating the domain and reads the nginx configuration file and replaces the typical PHP location section in it, adds configuration sections (about 150 lines) adapted for the correct operation of our web service.
The configuration is correct and the web services on it work successfully, it is being validated by the nginx successfully.
We have a suspicion that some parsing mechanisms of either the virtualmin kernel or the nginx plugin do not work correctly. Please tell us in which direction we can to dig deeper.
Environment:
OS Debian Linux 11
Webmin 2.0.21
Virtualmin 7.7 (LEMP bundle)
Nginx website 2.30
Nginx ssl website 1.19
nginx hosts configurations are stored in different "sites-enabled" files.
The text was updated successfully, but these errors were encountered: