Support for Nginx?

Hi tlozano,

We do not currently support Nginx because the plugin depends heavily on .htaccess rewrite rules, which Nginx doesn’t support.

While it’s technically possible to make those rewrite rules for Nginx, we cannot guarantee the plugin keeps working on future changes.

Our philosophy is that every plugin should work out-of-the-box, this is unfortunately not possible for Nginx sites, because the rewrite rules have to be added manually by an administrator.

We might change our minds about this subject in the future, but for now we ‘ve chosen to support Apache only.

I spoke with Flywheel hosting and they would love to learn more about this plugin and would apply the necessary nginx rewrite information if you could provide it. I would much rather use this plugin than one of the other paid options.

Hi QNTM Marketing,

Thank you for your interest in this plugin.

I don’t have the rewrite rules for nginx yet, but I’ll try to supply you with that information soon. I changed my mind about supporting nginx.

I expect to be able to supply the nginx rewrite rules within 1 month.

Oh good news! Thank you so much

Hi,
And does the plugin work with the LiteSpeed server?

I am currently getting the message: “Rewrite rules not working, please make sure you use Apache with mod_rewrite enabled”.

• This reply was modified 1 year, 7 months ago by Gyurmey.

Hi,

I expect to bring an update which supports nginx within 1 week.

@gyurmey Litespeed Server uses it’s own Rewrite Rule technology, though it works similar to Apache. But I guess this plugin is not working with Litespeed as Litespeed server has it’s own optimizations and rules. We’re unfortunately not able to support every platform, as every platform has it’s own specialties.

You can try to enable AutoLoad .htaccess on Context/Directory Level, the instructions you can find here: Rewrite Rules – OpenLiteSpeed. Maybe it works, but I’m not sure about it.

Hi, I released a new version, with instructions for nginx. Please let me know if you encounter any issues.

I just do a fast test, but it doesn’t work for me.

I get a message in the settings like this: “Rewrite rules not working, please see the plugin installation section:?https://www.ads-software.com/plugins/fastware-webpavif/#installation“

But I have not Rewrite rules because I have not apache, only Nginx.

I put the new Nginx config into http section of nginx.conf and into the domain.conf into the server section, just before original location /

I can not see the dir /wp-content/cache/fastware-webpavif so I think it is not converting.

The served images still are .jpg

I’ll try it tomorrow with more time.

Thank you for your work.

• This reply was modified 1 year, 7 months ago by tlozano.

@tlozano maybe a silly question, but did you restart nginx after changing the config?

The rewrite rules test on the configuration page should work on nginx too with the latest plugin version.

>>I can not see the dir /wp-content/cache/fastware-webpavif so I think it is not converting.
Thats right, this directory is created at the first conversion.

YEAH!! Is working! The problem was my test site; I set up another test site from scratch and I think it’s working (now in test). I can see the new files in the cache directory. I was having a problem with cron; on the “real site” there is a system cron via crontab, but on the “test site” the system cron doesn’t work and I had to set the “wordpress cron” to true. I test the site and now I can see an image served in webp format. I don’t know why only one, and only webp, not avif, but I’ll try further. In the cache directory there are some files with the “skip” extension, such as

horizontal-rgb-105×42-1.jpg.avif.skip and

horizontal-rgb-105×42-1.jpg.webp.skip

, do you know why? Thank you.

UPDATE:

Ok, the Skip files are when the converted file is greater than original file. If I set que quality to 85% there is a lot of converted ans served files, in webp and avif format, so It is working fine. Thank you.

• This reply was modified 1 year, 6 months ago by tlozano.

Hi @tlozano ,

Glad to hear it works. I’ll add a cron-checker on the config page to see quicker what the problem might be in case it doesnt work.

I think that cron check is not necessary; I’m not sure about it. It start to work after configure nginx from zero but the files was not converted, then I start the cron and the conversion start, but in a production site, the cron will be working, by system cron or config.php.

Thank you

Hello, I have Hestiacp with NGINX, I follwed your installation istruction but it shows this messagge:

WebP/AVIF image request failed, please check:
Apache: check whether mod_rewrite is enabled.
Nginx: follow the installation instructions in:?https://www.ads-software.com/plugins/fastware-webpavif/#installation.

Simulate WebP/AVIF image request X

I add map directive on nginx.conf and location directive on web custom template.

Pls let me know.

Thanks!

Hi @stefacchio,

Thank you for your feedback.

In some cases the simulated WebP/AVIF request fails because the site cannot connect to itself (which is common in docker configurations). Can you check this first? (you can check the loopback-requests on the health page of WordPress)

But of course something in your nginx configuration can also go wrong. Can you share your full nginx configuration so I can take a look what might go wrong?

(Our rewrite rules should work with a default nginx configuration.)

• This reply was modified 1 year, 5 months ago by richarddegoffau.

hello @richarddegoffau

I checked loopback request on and it passed the test: (I’ve Italian wp)

Il tuo sito può eseguire richieste di loopbackPrestazioni

Le richieste di loopback sono utilizzate per attivare gli eventi programmati, e sono utilizzate anche dagli editor inclusi per i temi e i plugin per verificare la stabilità del codice.

Here my nginx.conf

# Server globalsuser www-data;worker_processes auto;worker_rlimit_nofile 65535;error_log /var/log/nginx/error.log;pid /run/nginx.pid;include /etc/nginx/modules-enabled/*.conf;

# Worker

configevents { worker_connections 1024; use epoll; multi_accept on;}http { # Main settings sendfile on; tcp_nopush on; tcp_nodelay on; client_header_timeout 180s; client_body_timeout 180s; client_header_buffer_size 2k; client_body_buffer_size 256k; client_max_body_size 256m; large_client_header_buffers 4 8k; send_timeout 60s; keepalive_timeout 30s; keepalive_requests 100000; reset_timedout_connection on; server_tokens off; server_name_in_redirect off; server_names_hash_max_size 512; server_names_hash_bucket_size 512; charset utf-8; # FastCGI settings fastcgi_buffers 8 256k; fastcgi_buffer_size 256k; fastcgi_busy_buffers_size 256k; fastcgi_temp_file_write_size 256k; fastcgi_connect_timeout 30s; fastcgi_read_timeout 300s; fastcgi_send_timeout 180s; fastcgi_cache_lock on; fastcgi_cache_lock_timeout 5s; fastcgi_cache_background_update on; fastcgi_cache_revalidate on; # Proxy settings proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass_header Set-Cookie; proxy_buffers 32 4k; proxy_buffer_size 8k; proxy_connect_timeout 30s; proxy_read_timeout 300s; proxy_send_timeout 180s; # Log format log_format main '$remote_addr - $remote_user [$time_local] $request ' '"$status" $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for"'; log_format bytes '$body_bytes_sent'; log_not_found off; access_log off; # Mime settings include /etc/nginx/mime.types; default_type application/octet-stream; # Compression gzip on; gzip_static on; gzip_vary on; gzip_comp_level 6; gzip_min_length 1024; gzip_buffers 16 8k; gzip_http_version 1.1; gzip_types text/plain text/css text/javascript text/js text/xml application/json application/javascript application/x-javascript application/xml application/xml+rss application/x-font-ttf image/svg+xml font/opentype; gzip_proxied any; gzip_disable "MSIE [1-6]\."; # Cloudflare ips include /etc/nginx/conf.d/cloudflare.inc; # SSL PCI compliance ssl_session_cache shared:SSL:20m; ssl_session_timeout 60m; ssl_buffer_size 1400; ssl_protocols TLSv1.2 TLSv1.3; ssl_prefer_server_ciphers on; ssl_ciphers "ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS"; ssl_dhparam /etc/ssl/dhparam.pem; ssl_ecdh_curve secp384r1; ssl_session_tickets off; resolver 62.149.132.4 62.149.128.4 valid=300s ipv6=off; resolver_timeout 5s; # Error pages error_page 403 /error/404.html; error_page 404 /error/404.html; error_page 410 /error/410.html; error_page 500 501 502 503 504 505 /error/50x.html; # Proxy cache proxy_cache_path /var/cache/nginx levels=2 keys_zone=cache:10m inactive=60m max_size=1024m; proxy_cache_key "$scheme$request_method$host$request_uri"; proxy_temp_path /var/cache/nginx/temp; proxy_ignore_headers Expires Cache-Control; proxy_cache_use_stale error timeout invalid_header http_502; proxy_cache_valid any 1d; # FastCGI cache fastcgi_cache_path /var/cache/nginx/micro levels=1:2 keys_zone=microcache:10m max_size=1024m inactive=30m; fastcgi_cache_key "$scheme$request_method$host$request_uri"; fastcgi_cache_methods GET HEAD; fastcgi_cache_use_stale updating error timeout invalid_header http_500 http_503; fastcgi_ignore_headers Cache-Control Expires Set-Cookie; add_header X-FastCGI-Cache $upstream_cache_status; # Cache bypass map $http_cookie $no_cache { default 0; ~SESS 1; ~wordpress_logged_in 1; } # ACCEPT WEBP IMAGE FORMAT map $http_accept $webp_suffix { default ""; "~*webp" ".webp"; } # File cache (static assets) open_file_cache max=10000 inactive=30s; open_file_cache_valid 60s; open_file_cache_min_uses 2; open_file_cache_errors off; # Wildcard include include /etc/nginx/conf.d/*.conf; include /etc/nginx/conf.d/domains/*.conf;}

this is a default configuration created by HestiaCP with nginx, php-fpm and web template “WordPress”

• This reply was modified 1 year, 5 months ago by Stefano.
• This reply was modified 1 year, 5 months ago by Stefano.