Nginx restart

  • Resolved rafaelzrt

    (@rafaelzrt)


    10 months, 1 week ago

    Hello, I have configured W3TC and received the message:
    “nginx.conf rules have been updated. Please restart nginx server to provide a consistent user experience.”

    We have restarted the server. But the message persisted.

    I searched your docs but couldn’t find some information. In some servers I don’t have an easy access to restart it and I would like to understand better some points:

    1. What does this restart can affect and which configurations it will benefit? I see that configuring W3TC bring several benefits in performance even without the restart. So I would like to know what to expect with these restarts.
    2. After restarting the server one time, the message persisted. Does that means that it still needs restart or this message have the behavior to persist and only disappear when I hide it?
    3. My website still doesn’t load Webp images after they were configured and converted. I checked and the images are on my files, so they were successfully converted but still are not used by the wordpress. Restarting is something necessary for this feature?

    Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @rafaelzrt

    Thank you for reaching out and I am happy to help!
    This W3TC notification happens when W3 Total Cache detects the Nginx server, and after the settings are changed, and rules applied in the nginx.conf, on some environments (not all) the restart of the nginx service is needed.

    1. The answer to this is above, however, if all the rules are applied correctly (Browser Cache and Page Cache in most cases), there is no need for a restart and you can dismiss the notification.
    2. As mentioned before, you can dismiss this notification at any time. Its there to remind you that you may need to restart the server if the rules are not applied.
    3. If you find that your original image has been converted to WebP, but other image sizes are missing WebP versions, you may need to double-check that your WordPress environment supports the WebP format.
      While the original image is converted via our API service, the different sizes (e.g. Large, Medium, Thumbnail) are created by your own server. For this, you must have WordPress 5.8 and the appropriate libGD or ImageMagick package available on your server.
      To check if your WordPress environment supports WebP, navigate to Site Health > Info > Media Handling and double-check that WebP is listed in the supported file formats for the library shown in the Active editor. If you find these are missing the WebP extension, consult your system administrator to set up the correct packages.

    The W3TC uses rewrite to serve images as webp. Can you please share the website URL and the page that have images converted so I can check this for you?

    Thanks!

    Thread Starter rafaelzrt

    (@rafaelzrt)

    Thank you @vmarko for the support.

    1. Is there a way I can troubleshoot to see if I need a restart on the changes I did on the configuration? I restarted and dismissed the notification. It wasn’t clear to me if this notification will appear again if needed to restart.

    3. I’ve found out that the active editor WP_Image_Editor_Imagick doesn’t have the Webp in supported file formats. I’m asking the server support if they can enable it. I don’t have access to it but it would be nice if I could pass them some orientation on how to do it. I’m working on several servers and in some of them they ask me more specific orientations.

    If you want to check: https://dev.aquabureau.com.br/dedalus/br/

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Nginx restart’ is closed to new replies.