I’ve had a Webmin server running for over a year now. It is up to date, as far as I can tell, but it is starting to timeout on all of my websites and has gotten worse over the past couple of days. I’ve tried looking at the logs through the Webmin interface, but not seeing anything that is really sticking out.
From my last restart of the entire server, the sites lasted about 10 minutes before they were timing out again. I’m not afraid to dig into the terminal, but I’m confused as to where I should start troubleshooting.
Webmin seems to work fine, but it starts to lag and PuTTY has periods where it lags as well, much more than normal.
Whats are you pings like, if you set the ping with a longer count then the default (/n) and are you seeing timeouts.
If so then use tracert if the issue is between you and the server.
Also what to of website, are the all types, like plain static html or wordpress type sites.
Hi @stefan1959, the router drops ping requests. When I get more time I’ll go in and see if I can forward the ICMP packets to the server.
Some of the websites are WordPress and one is Cloudflare that is proxied through Webmin. When the sites timed out in the past, Apache still shows it is running fine in the dashboard.
So far, it is quiet and the sites are working. Ping statistics are rough though:
Packets: Sent = 17339, Received = 14938, Lost = 2401 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 3547ms, Average = 61ms
It doesn’t look promising, as it appears to crap out after it exits my ISP’s private LAN.
Tracing route to zzz.com [aa.bb.cc.dd]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * 1 ms 1 ms 100.65.51.1
3 3 ms 3 ms 3 ms 100.126.2.17
4 18 ms 17 ms 16 ms 100.126.0.81
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 35 ms 34 ms 34 ms aa-bb-cc-dd.googlefiber.net [aa.bb.cc.dd]
I’ll run a traceroute from work later this morning as well as it is on a completely separate network.
I should mention that when the the websites go down, it is down from every network, whether work, home, or cell. I can, however, connect to the VPN hosted on the same physical server without issue from those external networks.
Packets: Sent = 8246, Received = 8125, Lost = 121 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 107ms, Average = 34ms
Ping from home to VPN:
Packets: Sent = 8250, Received = 8132, Lost = 118 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 389ms, Average = 34ms
From work, this is the result, which is more like it and is what I had expected:
Packets: Sent = 31655, Received = 31647, Lost = 8 (0% loss), TTL=47
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 386ms, Average = 68ms
So I already knew that my home had problems connecting to this particular server. My ISP blames Google, and Google blames my ISP. Here’s the results from home:
Packets: Sent = 19614, Received = 15312, Lost = 4302 (21% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 328ms, Average = 34ms
So when the timeouts occur on the websites, as mentioned before, it doesn’t matter whether I’m home, at work, or on the cell. When they go down, they are truly down. I can’t even access them from the same local network on the server.
It looks like things are working so far okay today, so I’ll just keep an eye on things again.
Right, sound like a router somewhere is faulty. Your test from work I think proves it not google.
But with the website I think using using Inspect (on the browser) and network tab should show where the issue is there, if its a separate issue.
Also use page speed testing website, then its not using your network. https://pagespeed.web.dev/
I found a couple of scans that were going in the background from WordPress that seem to have been the cause. I dropped one that never should have been set up, and I set the other to use fewer resources. I haven’t seen any timeouts since.
