Main Area and Open Discussion > Living Room

GoDaddy Blocking Access to Website

(1/2) > >>

Stoic Joker:
Okay got a bit of a weird one here. We have a client that wanted some coding done to their website that is hosted on GoDaddy. I loaded the site in several browsers (IE/Edge/FF) to check its behavior ... And it loaded fine. Then I connected to the CP to get the FTP access information, connected via FTP, and downloaded the site (~160MB) to work on locally. After which the site will no longer load in a browser from within the building.

Now I say "From within the building" for a reason. None of the computers behind our companies IP address can access the client's website any longer...at all. I can get to the CP.. I can get to the FTP.. I can ping the domain name and get a response from the sites correct IP address... But it won't load in any web browser, on any machine, running any OS, from anywhere in the building ... However it will load just fine on my phone...if I get off of the companies wireless network. :huh:

So... WTF did I pissoff on GoDaddy's hosting system that caused it to (apparently...) blacklist the companies IP address??? There is an IP Blocklist option in the PC...but it doesn't list - us as blocked - anything useful.

So has anyone ever heard of or seen this kind of crazy assed shenanigans from a web host before?? I've got a gun-to-my-head deadline and really need to get past this..

Thanks in Advance,

Stoic Joker

wraith808:
I'd say quit trying to figure it out, and contact them.

Stoic Joker:
I'd say quit trying to figure it out, and contact them.-wraith808 (June 27, 2017, 05:04 PM)
--- End quote ---

That's on tomorrow's to-do list. But it's compounded by the fact I'll be calling on behalf of the client, and will possible need to engineer my way past GD support identity verification ... Assuming they have any.

So I was hoping there was an alternate (configuration based) option that I could get at more easily ... Since I have CP access to the account.

Normally I'm quite good at the SE type stuff, but lately the office environment has turned into a constantly toxic epic shit-storm. So I - like most of the staff - spend most of my days stressed to the max because the owner has turned into the vitriolic red queen from Alice in Wonderland prowling the office looking for something/anything to scream at or about. *Shrug* It's really just too fucking hard to think straight in that type of atmosphere. But I'd like to get this client's project done before I completely shutdown and start focusing on looking for another job.

(Assuming you've seen the commercial) PW: Ihatemyjob1  :D

mouser:
Sometimes the blacklisting tools are just there to temporarily block an ip for a few minutes -- you might just want to check it again in a bit.

wraith808:
I'd say quit trying to figure it out, and contact them.-wraith808 (June 27, 2017, 05:04 PM)
--- End quote ---

That's on tomorrow's to-do list. But it's compounded by the fact I'll be calling on behalf of the client, and will possible need to engineer my way past GD support identity verification ... Assuming they have any.

So I was hoping there was an alternate (configuration based) option that I could get at more easily ... Since I have CP access to the account.

Normally I'm quite good at the SE type stuff, but lately the office environment has turned into a constantly toxic epic shit-storm. So I - like most of the staff - spend most of my days stressed to the max because the owner has turned into the vitriolic red queen from Alice in Wonderland prowling the office looking for something/anything to scream at or about. *Shrug* It's really just too fucking hard to think straight in that type of atmosphere. But I'd like to get this client's project done before I completely shutdown and start focusing on looking for another job.

(Assuming you've seen the commercial) PW: Ihatemyjob1  :D
-Stoic Joker (June 27, 2017, 05:48 PM)
--- End quote ---

Sounds pretty bad.  Sorry I couldn't be more help; when I had a similar problem, one time it was the firewall on the server, so they had to correct it, and the other time it was the firewall in the company.  Have you checked that?

Navigation

[0] Message Index

[#] Next page