restart server

Hi @lucytech

Most probably WebP is not generated for some thumbnails.

Are you looking for WebP for image.jpg (example) or image-123×456.jpg (example, replace 123×456 with some other numbers – width/height of the thumbnail)?

If the latter one, it means WebP is not generated for the specific thumbnail and you should try to generate it from Imagify Settings page.

Server should not be restarted as it would not change anything in fact.

Restarting it should not affect other websites (maybe just for the very short time, but should not be dramatic), but there is no need to do it for Imagify related tasks.

Let me know if it is possible to share your website URL so we could check.

Best Regards
Marko

Hi @lucytech

Can you tell me what method of displaying WebP you are using?

It looks like it is rewrite rules method, which would not work if you didn’t add NGINX rules for WebP to nginx.conf.

The image you mentioned is background image, so it would not work with “<picture” tag method.

Can you confirm you use rewrite rules? Once you add NGINX rules (you can see them once you activate the option in Imagify Settings), you have to reset NGINX so it takes effect.

Best Regards
Marko

Hi @lucytech

These are rules to add to nginx.conf:

location ~* ^(/.+)\.(jpg|jpeg|jpe|png|gif)$ {
  add_header Vary Accept;

  if ($http_accept ~* "webp"){
    set $imwebp A;
  }
  if (-f $request_filename.webp) {
    set $imwebp  "${imwebp}B";
  }
  if ($imwebp = AB) {
    rewrite ^(.*) $1.webp;
  }
}

There is no need to restart NGINX every time, it is only when you add the code to nginx.conf file.

There won’t be issues as long as the code is added properly (you can add it at the end of the file). It would be good to test websites by visiting them, just to be sure it is all good. If not, you can remove this code and reset the NGINX again (and let us know if this happen).

Best Regards
Marko