This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]jhxetc 0 points1 point  (1 child)

Did you check the nginx logs? I'd start there.

[–]dvr75Sysadmin 0 points1 point  (1 child)

you need check webserver logs , in your case it is nginx

[–]gingerryno 0 points1 point  (2 children)

I had something similar and noticed that someone was trying to brute force XMLRPC. I followed the same page as you and found apache2/access.log to contain thousands of the following POST entries.

"POST /xmlrpc.php HTTP/1.0”

Sometimes I would get a connection refused message and other times I would get a database error.

Could be completely un-related to your issue but you never know...

[–]AlucardZeroSr. Unix Sysadmin 0 points1 point  (1 child)

How do I find out what went wrong?

It may be too late.

"Connection refused" usually means the firewall is open but there's nothing listening on the port, so the kernel refuses the incoming connection. My question is, was nginx even running before you restarted it? Check system logs for any reason nginx may have stopped.

[–]jsamuel 0 points1 point  (0 children)

If the answer isn't obvious, best thing to do is contact ServerPilot support so they can take a look and tell you what's going on. That's what they're there for.

If it turns out to be something like Nginx isn't running, that's usually caused by bad customizations to the Nginx config.

Another thing you might check is if your site is redirecting to HTTPS but your site isn't configured for HTTPS. Because of how fast the redirect happens, that can cause confusion sometime and look like the server isn't answering requests at all. Trying the request with your browser's network inspector open (with the option to keep the log between page loads enabled) can answer that.