Webinoly is just the perfect tool for NGINX experts. Give it a try!
0 votes
by Rookie
Updated Webinoly last night (probably at least a year since last time).

Now I get Internal Server Error 500 on all WP-sites when trying to login. Just viewing them works but login does not. Multiple sites all setup with Webinoly. DO Droplet on LTS 18.04.

Where shall I begin to look and diagnose this problem?
by Expert
Look into your server logs.
by Rookie

OK, the only log error I can find is (inside /var/log/nginx/error.log):

could not build optimal fastcgi_params_hash, you should increase either fastcgi_params_hash_max_size: 512 or fastcgi_params_hash_bucket_size: 64; ignoring fastcgi_params_hash_bucket_size

Is this it? If so, where exactly do I change these values?

by Rookie

This is what /etc/nginx/fastcgi_params looks like now:

fastcgi_param  QUERY_STRING       $query_string;
fastcgi_param  REQUEST_METHOD     $request_method;
fastcgi_param  CONTENT_TYPE       $content_type;
fastcgi_param  CONTENT_LENGTH     $content_length;

fastcgi_param  SCRIPT_NAME        $fastcgi_script_name;
fastcgi_param  REQUEST_URI        $request_uri;
fastcgi_param  DOCUMENT_URI       $document_uri;
fastcgi_param  DOCUMENT_ROOT      $document_root;
fastcgi_param  SERVER_PROTOCOL    $server_protocol;
fastcgi_param  SCRIPT_FILENAME        $request_filename;
fastcgi_param  HTTPS              $https if_not_empty;

fastcgi_param  GATEWAY_INTERFACE  CGI/1.1;
fastcgi_param  SERVER_SOFTWARE    nginx/$nginx_version;

fastcgi_param  REMOTE_ADDR        $remote_addr;
fastcgi_param  REMOTE_PORT        $remote_port;
fastcgi_param  SERVER_ADDR        $server_addr;
fastcgi_param  SERVER_PORT        $server_port;
fastcgi_param  SERVER_NAME        $server_name;

# PHP only, required if PHP was built with --enable-force-cgi-redirect
fastcgi_param  REDIRECT_STATUS    200;
fastcgi_param   HTTP_PROXY      "";
fastcgi_param   HTTP_PROXY      "";
fastcgi_param   HTTP_PROXY      "";
fastcgi_param   HTTP_PROXY      "";
fastcgi_param   HTTP_PROXY      "";
by Rookie
I'm running no less than 5 we domains on this specific Webinoly stack. Please advice!
by Rookie
Browsing Stack Overflow I get a tip that there could be too many and differentiating fastcgi_params in my server settings.
Did Webinoly somehow move or change these directives between version 1.3-ish and today?
by Expert

Please, read the documentation.

  • Webinoly has the "log" command to see your logs in real-time.
  • I'm sure you have more than one log file.
  • See the error log for each individual site.
  • See the PHP logs.
  • Check for NGINX errors sudo nginx -t.
  • Run the Webinoly verify command.
  • Be sure your server is updated.
  • The fastcgi message you are getting is just a "warning", not an error, so it's not the cause of your issue.
And don't take me wrong, but nobody will be able to help you if you just come here to say you have a problem and you don't even describe with details your issue. A "500 error" can be caused by a lot of things, there are no magical answers.
by Rookie
I'm sorry. When I wrote the original post I had no idea how general of an error 500 was. I've learned a lot these past days but I have not yet found the culprit.

Webinoly updates and/or verifies without problem. And nginx -t doesn't really show anything serious. I guess I will have to find out about and look into more different log files.
by Rookie
Might this be the real error logged by Webinoly log?

2019/11/22 23:08:46 [crit] 52446#52446: *18154 pread() "/etc/nginx/" failed (21: Is a directory), client:, server: domain.se, request: "GET /wp-admin/ HTTP/1.1", host: "domain.se"

Command nginx -t tells me /etc/nginx/nginx.conf is both syntax ok and test is successful.
by Expert
Yes, that message means that some path or filename used in an include statement, is not valid or is corrupted.

Also, "Webinoly updates" are not the same as "server updates". Read the docs!
by Rookie

OK - problem is now solved. But I'm not sure what I did, I did reinstall nginx fully and I did turn all off httpauth in Webinoly. And whitelisted my own IP. But I'm not sure what exactly did the trick. The includes mentioned above was probably not wrong after all.

The Webinoly log command was most useful anyway.

Please log in or register to answer this question.

Welcome to the Community site for Webinoly.

Our Optimized LEMP Web Server is a powerful set of commands for doing just about anything you could wish.

With Webinoly you can set up your NGINX web server in just one step.

* * * * * * *

To report a bug, please create a new issue on GitHub or ask a question here with the bug tag.
Webinoly Support Paypal Donations

PayPal · GitHub Sponsors · Bitcoin

It is very important that any visitor to the site read the disclaimer, terms of use and privacy and legal statement before start browsing.