Hello, Clients don't seem to be able to execute links off my server anymore. For example, I sent my son a link. He tried it and gets the too long to respond message. If he uses a redirection to a resource on the server I purchase from Yahoo, its the same message. But, sitting at my server, the link I sent my son in the Sent folder works and so does the redirection. My down and up speeds were greater than 40 and 20 MBS respectively. There is nothing in the error log and no accesses from anyone external is shown. The KeepAliveTimeout Apache httpd.conf parameter is set at 100. No Apache changes have been made and Apache has been rock solid for a long time. I did move from cell phone/hotspot internet connectivity to router/WIFI connectivity (Spectrum) recently. My son just got another message - 'The server is online but is not responding to connection attempts'. Any help will be appreciated on what might be going on or how to troubleshoot. I'm using Apache/2.4.39 (Win64) mod_perl/2.0.10 Perl/v5.26.3 on a current Windows 10 platform. Thanks, craigt
Can you elaborate on this a little? I tried to save a link below to a webpage executing off my home server? It tried the link when I tried to save it saying the server took to long to respond, and would not let me save the link. I reinstalled the server and got the same result.
I am not a pro, so this is just a layman's take on this but if, let's say, the person is using a proxy then s/he can get that error. Also, some browsers, after they get bogged down for having too many add-ons, can throw that error. There is a couple of other reasons why this can happen apart from your Apache setup. You should test those links on more people to see if they work for them.
My server seems to be shut down to everyone except me working on my server machine. I asked 4 friends to try to access resources on my server in different ways. They get 'the server took too long to respond' message and 'the server is online but not accepting connections' message. My down and up speeds are above 20 MBS. I reinstalled the server once with same messages occurring. Any help is appreciated. I have not run into this problem before. I've been using Apache for several years through 2 versions with no problems. I'm sort of lost on how to proceed. I don't even know if its an Apache issue. But it seems like it is.
Any slow database queries listed? On your web browser's network tab you can see how long it takes to load each bit of the web page, anything stand out as taking forever to load?
This is a no sql application. The database stuff is my own design and has worked without issue for a long time. I'm not familiar with the browser network tab, but all of the code has been working well for awhile without issue. When I sit at my server machine, everything works as it has. When the 4 people in other places on their client machines tried to access my server, they get 'the server took too long to respond' message and 'the server is online but is not accepting connections' message. I did just transition from cell phone/hotspot internet connectivity to router internet connectivity (Spectrum). And I have used a reasonably priced dedicated IP from PureVPN for internet visibility in the US for several years. The Spectrum people told me that the router has an ip and that they did not recognize the dedicated IP from PureVPN. When I check my connection properties, the only operational connection is the wireless LAN and the IPv4 IP address on my server machine is 192.168.1.3/24. The IPv6 IP field is not populated. The dedicated IP I'm connected with is 192.253.246.153 and the dedicated IP gives me WWW visibility. Could there be an incompatibility between the router and VPN IP addresses?
Yes they all use the same ISP. IPCONFIG /all shows WIFI and PureVPN adapters with correct router and dedicated IPs respectively. Why would the server be operational and not accept connections from external clients but be working as expected for me when I'm on the server machine?
The following is a list of connections from netstat -n. Proto Local Address Foreign Address State TCP 127.0.0.1:49671 127.0.0.1:49672 ESTABLISHED TCP 127.0.0.1:49672 127.0.0.1:49671 ESTABLISHED TCP 192.168.1.3:63674 184.84.169.209:443 CLOSE_WAIT TCP 192.253.246.153:49588 172.253.63.188:5228 ESTABLISHED TCP 192.253.246.153:49589 40.83.240.146:443 ESTABLISHED TCP 192.253.246.153:51273 172.67.26.25:443 ESTABLISHED TCP 192.253.246.153:51275 20.69.137.228:443 ESTABLISHED TCP 192.253.246.153:51748 40.83.240.146:443 ESTABLISHED TCP 192.253.246.153:51751 142.250.81.234:443 ESTABLISHED TCP 192.253.246.153:53046 151.101.208.193:443 ESTABLISHED TCP 192.253.246.153:53793 13.249.102.65:443 ESTABLISHED TCP 192.253.246.153:54368 142.250.64.110:443 TIME_WAIT TCP 192.253.246.153:54983 23.200.205.193:443 ESTABLISHED TCP 192.253.246.153:55320 151.101.1.69:443 ESTABLISHED TCP 192.253.246.153:56019 142.250.80.34:443 TIME_WAIT TCP 192.253.246.153:56269 142.250.65.225:443 ESTABLISHED TCP 192.253.246.153:56989 192.0.73.2:443 TIME_WAIT TCP 192.253.246.153:58662 142.250.80.98:443 TIME_WAIT TCP 192.253.246.153:59612 142.250.65.194:443 ESTABLISHED TCP 192.253.246.153:60014 142.250.64.99:443 TIME_WAIT TCP 192.253.246.153:60438 35.217.17.196:443 ESTABLISHED TCP 192.253.246.153:61981 151.101.129.69:443 ESTABLISHED TCP 192.253.246.153:62007 142.250.80.98:443 TIME_WAIT TCP 192.253.246.153:62111 66.218.87.15:443 TIME_WAIT TCP 192.253.246.153:62399 69.147.82.60:443 ESTABLISHED TCP 192.253.246.153:63853 23.200.205.193:443 ESTABLISHED TCP [::1]:9030 [::1]:52616 ESTABLISHED TCP [::1]:52616 [::1]:9030 ESTABLISHED My Apache server is listening on port 80 (listen 80 in httpd.conf). Should I be seeing a port 80 somewhere here? The 3rd line is the WIFI Router connection I think. The router IP written on a metal tag on the back of the router is 192.168.1.1 and has 24 last segment variations to try to connect with I think. Restoring Apache from a backup, done when I upgraded to the current version more than 1 1/2 years back, with external clients getting the same messages suggests the problem is not with Apache to me. What do you all think. The dedicated and router IPs not working together seems like a possibility, but I don't understand it. I'm shut down and don't know how to proceed on this. Spectrum tells me I have internet connectivity. PureVPN tells me my dedicated IP is working. I'm sort of in the middle. All I really know is that my application can only be accessed locally. External clients can no longer access the application that the server is being used to present and demonstrate. The server takes to long to respond I guess because it won't accept connections. HELP.
This Apache server is only used for this 1 application. But my access log on any night over the 10 or so years I've used Apache has had many entries tagged by IP from crackers trying to create havoc on the server. People like the Romanian Black Hats and Radio XXX from Montenegro, Serbia and many others where there every night in the server access log. Now all of that has stop. And when I've asked friends to try to invoke the application, there is no access or error log entries. Entries in the access log only occur when I invoke the application from a browser sitting on the server and the application works as it should. Its like this router based ISP with a router IP is a network concealing my Apache server using a dedicated IP, unless I invoke the application sitting at the server. But the message that 'the server is online but not accepting connections' the remote clients are getting suggest that the client request went to the server because it said it was online. The server machine I'm sitting at when the application works must be getting checked first. The IPv4 value for the WIFI connection adapter is the router IP and doesn't resolve with the URL being executed. But a PureVPN connection adapter (PPP) is found with an IPv4 value equal to the dedicated IP. The dedicated IP resolves and the application comes up. But a request from the remote client stops at the router IP which does not resolve with the application URL and the application is not executed.. I'm just trying to imagine what might be happening. Does this sound plausible to you all.
Ask your ISP if they've started blocking Port 80. If you put a small test application on the server, are the clients able to access that or is it block like the proper app?
I had the ISP unblock port 80. That is the port that Apache is listening on but it did not make a difference. I did put together a small application using the same dedicated IP and my remote clients got the same server messages.
No. The router was just installed by the ISP (Spectrum) when I started their service. My server and dedicated IP is hidden by the ISP Router IP I think.