I reset the server with the # RESET command and now I get the default: Has the server been wiped? Also, I can't login at all the default page doesn't get me past this page: I used to be able to get past this page which took me to a login page but now it just appears to be loading forever. What should I do? Will this be an issue for the server company to solve and also, do you think the server has been wiped?
Wait, what? What CMS are you using? Is this a Linux or Windows server? What control panel are you using?
Ok, I don't think the server has been wiped, but something may have gone wrong if Apache is taking this long to sort itself out. When you access the Plesk admin section, are you still able to see accounts with the sites configured? If you log in via FTP, do you still see the site files?
I can't login to anything. SSH using Terminal allows me to put the login string in and asks for my password, when I enter the password nothing happens. No error, no timeout nothing. Going through the IP address and :8843 sends me to a page prompting me that the site's security certificate isn't trusted (because it's outdated). Usually when I get to this page I click "Proceed Anyway" but now I click it and all I get is the loading icon, it doesn't take me anywhere or do anything other than that.
I do not believe that this is a problem that can be solved via forum posts, I think that this would be quicker to have your host look at, something has gone really wrong if you only pressed 'reset'
Even pinging the url of the page clearly displaying the Apache test page doesn't work which completely confuses me how the page can be live but the packets bounce back. Nothing I can do until tomorrow now when I can ring the host.
HTTP traffic uses TCP port 80 (by default), ping falls under ICMP traffic and that doesn't use TCP ports. Thus, you can firewall off ping but still access HTTP It's unfortunate to hear that Are you not able to call up their after-hours support? Or doesn't your contract include that? What I'd suggest you do (while this is fresh in your memory) is write down everything you did prior to hitting 'reset', no matter how silly/stupid/inconsequential each thing may seem. I've worked as a sysadmin for ISPs in the past and let me tell you - every bit of info helps as what may seem unimportant to you may be just what the technician needs to know about Also, good luck getting this sorted out, I know how it feels to have a server go wonky like this at the wrong time
I don't think such issues resolved on forums because you have to check the server by using the KVM as you mentioned you are not able to SSH to the server, so its always better to consult such issues with the server provider.......I hope you are able to access the server now