nginx.conf rules have been updated. Please restart nginx server …

Hello @martinsdzerve

Thank you for reaching out and I am happy to help!
In some Nginx environments, after any update in the nginx.conf rules, the nginx needs to be restarted in order for the changes to take place.
W3 Total Cache adds the rules to the nginx.conf depending on the configuration, and for example, if the gizp is enabled, the W3TC adds the rules to the nginx.conf.
What you are referring to is a reminder. So with the gzip example, you can check the website and see if the files are gzipped

Content-Encoding: gzip

If the rulesa are applied, you can dismiss the notification.

I hope this explains the behavior.

Thanks!

Hello.

Regarding to this one: “W3 Total Cache adds the rules to the nginx.conf depending on the configuration, and for example, if the gizp is enabled, the W3TC adds the rules to the nginx.conf.”

I don’t think plugin is able to change any system related files, including nginx.conf. Otherwise it would be a security-breach or mis-configured system. And this is why I asked – Does this message “by default” appear when the plugin is first installed, or does it only appear when the plugin really makes nginx.conf changes?

In my opinion it is just “by default”.
I think this message is useless, because it is misleading info, but maybe I am wrong ??

• This reply was modified 8 months, 3 weeks ago by martinsdzerve.
• This reply was modified 8 months, 3 weeks ago by martinsdzerve.

Hello @martinsdzerve

W3 Total Cache needs to add rules to the configuration file.
However, thank you for your thoughts and we’ll make sure to check this and show the notification if the changes are not taking place.

Thanks!