I have a site registered with Godaddy and hosting with Enom. The domain was pointed to Enom's nameservers on 1/14/15 and was fine until 1/17/15. It's a wordpress site and on 1/17/15, without doing anything to it, it went down and I could not access it via FTP either. It was literally down all day. The strange thing is, it seemed to be accessible on cellphones, but not PCs. On 1/18/15 I was able to access it via FTP & via all browsers.
On 1/18 it went down again and suddenly came back up. (I checked at 6pm and it was back up and running fine.) Checked 1/19 and all is good again.
When I was unable to access the site via FTP (Filezilla), I got the following error: "connection attempt failed with eai_nodata - no address associated with codename"
When I tried on all browsers, I received a DNS lookup failed.
This is the strangest thing I have encountered. Does anyone have any idea if this is a problem coming from the Registar or the hosting company? Any suggestions or ideas are welcome.
Thank you.
your phone is on Wi-Fi of same network as your PC or on mobile phone network?
If on a different network so check if it happens only in your computer or in other computers to (You could check with proxy sites ,hidemyass for example).
If its only on your PC, sounds like its a problem with your internet provider with the DNS/IP of your server.
I had the same issue, one time after a few days it solved itself. In some other case i had, it was something in the internet provider actually (the DNS was blocked or something or not updated or something like that).
The reason it sounds like that is because in your phone your site is up, but could be its something else.
Related
I noticed that my uploaded files became unavailable yesterday morning. I didn't change the settings.
It doesn't work in browsers and mobile apps, but it is wired because it works in different regions.
I tried to run the curl -I https://firebasestorage.googleapis.com/v0/b/bucket... but I just got the HTTP/2 400 error and nothing else. When I link an URL for example into the Slack chat, then the URL works but when I try to open it from a browser or in a mobile application it doesn't work.
I got this message.
UPDATE: It works from VPN and 4g but doesn't work on wifi. This is totally weird.
Thanks for the help.
This issue is caused because your ISP is blocking connections to Firebase. There other user who have reported the same issue with Hungarian Telekom mobile (¿is that the ISP you are using?). The solution is to contact the ISP and tell them to allow those connections. This also explains why using a VPN works.
I am having a mild panic attack and could use some help.
I was emailed by Google telling me I need to change my machine type in my VM Instance. So I logged in, it told me I needed to stop the instance to make that change. I stopped the instance and then realized I'm not using the deprecated F1-Micro, so I just hit Play to restart the instance.
It restarts, has the reassuring green symbol, but my wordpress site can't be accessed.
I tried connecting via SSH and it seems like the data is there, I can navigate to the wordpress folder.
Can someone please advise on what I need to do to get the site running?
Thanks!
EDIT: More Info
Checking status of NGINX server shows it is "active (running)"
When visiting the web address, it loads for a very long time and then goes to an error page that just says "This site can't be reached the site took too long to respond. try checking connection and the proxy and the firewall. ERR_CONNECTION_TIMED_OUT"
I found the issue.
The Google documentation suggests your IP address will remain. Whether that is standard or not, my IP address changed, so once I updated my DNS records I was back online.
We have a lamp word press intranet site running, however, the first time I load the site it doesn't load and says the page cannot be displayed. When I refresh the site it loads. Is this a problem with our server or dns or what?! We have no proxy and sometimes get this error message as well ERR_CONNECTION_RESET. Any ideas?
I suppose the best way forward is to first figure out which part of the process is failing, browser, computer or web server.
Determine the most likely point of failure
If the fault occurs on more than one computer, and with different browsers then it not likely to be browser or computer issue. Therefore the next step is to look at the webserver.
if it looks like a computer or browser issue
If its only failing on one computer or browser the try flushing your browser cache, if that fails then it could be a network setup issue. You could try setting you computers DNS network settings to point to your internet router and to your web servers IPs.
if it seems like a web server issue
1) Check settings of your network, try setting DNS to router and webserver.
2)If you have a spare computer install fresh webserver and try using new test webserver to see if you get the same problems
and if all else fails get windows PC install WAMP;) or the ultimate solution switch it off and go the pub.
I've been working on a client site for a few months now and I'm suddenly having a lot of trouble accessing it.
Chrome tells me:
This webpage is not available
Google Chrome's connection attempt to [client] was rejected. The website may be down, or your network may not be properly configured.
The website is available on any other computer, whether on the same wireless connection or not.
My traceroute shows a hop to localhost and then it stops. Interestingly enough, if I remove the "www" the site loads, and the traceroute without www works normally.
I've tried resetting my wireless adapter. I've tested this on multiple wireless networks and it just does not work on my computer.
I had this problem a few nights ago and it mysteriously worked for about a day and then the problem resumed this morning.
I do not have any proxy settings in Chrome. I've tried cycling the adapter, renewing the lease, and trying other routers. Just now, I also tried on ethernet and the problem persists. The problem also persists over users and browsers.
I don't notice any other sites affected. I am currently using a Mac. If I use Parallels to use Windows, it has no problem connecting to the site or tracing properly.
Does anyone have any troubleshooting suggestions?
Have you tried to flush the routing table on your machine?
/usr/bin/sudo /sbin/route flush
In a testing environment, I self-signed a cert and installed it on a web site in IIS 6. This is using .NET 2.0. Cert seems fine (minus the fact that client services don't fully trust it as one would expect). I can do whatever I want to by hitting the site locally from the server on HTTPS or HTTP.
The problem is coming in when accessing this site remotely. If the page has an exception on it, the connection drops. Not return an error, but just flat-out drops, where the browser says it couldn't find the site (this is after it churns for a few seconds, where I can see TCP traffic from the client IP coming in).
The interesting part is that I can create a blank ASPX page, with nothing on it, and it's fine over HTTPS. But the minute I put throw new Exception(); on the page, it goes back to dropping. By the way, it seems to act completely normal if I hit the same page using HTTP instead.
So I'm a bit stuck. Anyone seen something like this?
My first inclination is to go after the proxy/firewall rules between my remote client machine and the server, but I want to make sure it's not something I could fix before I bug other teams.
EDIT ...looks to be a firewall whitelisting problem. Others on my subnet have the same problem, but people in other locations can hit it just fine.
This is not a proxy or firewall issue, because the Yellow Screen Of Death is just text which transmits through any firewall just fine. Here are a couple things that I would try first.
Make sure that the fact that you are using HTTPS isn't the root cause of the problem, such as the problem isn't caused in your program, by handling HTTPS. Such as some special handling of Error code.
Create a new cert and see if the same issues occures.
Try to reproduce this issue on another machine, it could just be a configuration issue.
Try getting a real cert from GoDaddy, they are only 29.99.
That is all that I can come up with right now. One thing that you didn't mention was which version of IIS you were using, which will be helpful.
Have your thrown the exception and then tested the page using regular HTTP? Is the same thing happening, or does it only happen if you throw an exception and access it using HTTPS?