• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Apache & nginx Settings for ... not saved anymore

Linulex

Silver Pleskian
Username: Linulex

TITLE

Apache & nginx Settings for ... not saved anymore

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

obsidian, 18.0.31 up1, centos 7.9 and centos 8.2

PROBLEM DESCRIPTION

Adding anything to any of the fields

Additional directives for HTTP
Additional directives for HTTPS
Additional nginx directives

in "Apache & nginx Settings" is not saved when pressing "OK" or "apply"

STEPS TO REPRODUCE

enter something valid in any of the fields

Additional directives for HTTP
Additional directives for HTTPS
Additional nginx directives

in "Apache & nginx Settings"

can even be as simple as a comment line
#test

and ok or apply

ACTUAL RESULT

leave "Apache & nginx Settings" page, go back to "Apache & nginx Settings" page: change isn't there anymore

change was not saved to /var/www/vhosts/system/domain.name/conf/ ... filename

replace domain.name with the domain you are testing on
replace filename with the section that was changed: vhost.conf, vhost_ssl.conf or vhost_nginx.conf

EXPECTED RESULT

changed are saved (and applied) to configuration files

ANY ADDITIONAL INFORMATION

changing: vhost.conf, vhost_ssl.conf or vhost_nginx.conf directly and the going to plesk "Apache & nginx Settings" page reflects the change. So the files are read correctly, but changes are not saved.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug and fix
 
From developer:

The issue has no confirmation. The client needs to look at the application logs (panel.ini with debug mode). And also view the web server logs (nginx & apache). It is possible that the webserver configurations already have incorrect values.
 
I found the problem and it is a problem in the plesk test to check if the correct value has been entered.

When adding to panel.ini

nginxCacheSizeMax = 67108864

The problem exists and there is a message

{"formMessages":{"nginx":{"nginxCache":{"nginxCacheSize":{"notBetweenStrict":"\"67108864\" is not strictly between \"0\" and \"67108864\""}}}},"status":"success","statusMessages":[]}

When chaning it to
nginxCacheSizeMax = 134217728

The problem is gone.

I think it should be possible to have the default value as the max value. after all that what it means: the maximum value that can be entered.

regards
Jan
 
Back
Top