Skip to main content

http not working anymore

carock
For some reason since yesterday, almost all of my websites stopped working with http. If I put a self-signed cert on them and then they work https, but not with http. Another strange thing is none of the http requests are logged as if Apache doesn't know anything about them anymore. I get an ERR_SOCKET_NOT_CONNECTED in Chrome and a simple this page cannot be displayed in IE. Anyone else have this problem or an idea I can work with? Thanks, Chuck

Comments

6 comments

Date Votes
  • Anupam SG
    What level of access do you have on the server in question? From the error it looks like the server is not accepting connections on port 80(default port for HTTP), but it is on 443(port for HTTPS).
    0
  • cPanelLauren
    Hi @carock Yea, if you have root access to the server this will be easier to investigate as you'll have access to the logs, if not I would suggest contacting your provider to assist you further. Thanks!
    0
  • carock
    Full access. Netstat shows the server listening on port 80 tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 22061/httpd tcp 0 0 :::80 :::* LISTEN 22061/httpd I have 14 IP's assigned to this interface, eth0, and only 2 of them seem to be working. No site on any of the other IP's on this network interface are though. Eth1 is working fine with a different IP block and 14 IP's assigned to sites. I checked the default gateway on that IP block and it only shows one MAC address for each of the non-working IP's and it's this server. So no IP conflicts with another computer. httpd.conf shows each of the IP's in it and all virtualhost entries look the same. No "extra" configs in userdata for any of them either. I can SSH into any of the IP's and they all work and it's this server. Dovecot, Exim all other services seem to be fine on the IP's that aren't working in Apache. I put a self-signed cert on one of the sites and used Fiddler to watch the connections. The https shows a 200 connection result and a TLS 1.2 handshake, but gives this error: Authentication failed because the remote party has closed the transport stream. When I use http, it returns a 504 response and Fiddler displays this: The server did not return a complete response for this request. Server returned 0 bytes. I'm out of troubleshooting tricks at this point. I guess I'll try moving all the sites to the working IP's and ditch the others. If no one else is having this problem, I don't think it deserves a cPanel ticket. Chuck
    0
  • cPanelLauren
    Hi @carock That's pretty strange indeed, I don't know if you've moved the sites or are in a position to test but if you restart ipaliases do you continue to have issues? Have you checked with your provider in regard to any potential routing changes? Though I don't know if that would be possible since you can access the IP's.
    0
  • carock
    I am the provider :( unfortunately... I ended up moving most of the sites to a new server and only have the ones working remaining. If I run into this again, I will try the ipaliases restart and if that doesn't work a reboot. Maybe somebody was trying to attack it and broke something. Thank you everyone for the help. Chuck
    0
  • Bob1965
    you should also check with the data center and make sure they don't have a firewall installed. The data center would be able to block port 80 on specific IP's.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post