5 replies to this topic

[Stephen R]

I tried to see if this bug has been reported elsewhere, but couldn't find anything. I can't connect to the https port on gamedev.net, which meant I couldn't log in. I was able to get around this by changing the the facebook login url to http (which should probably also not be allowed?). This was also the case when I tried to log in last night.

curl -v https://www.gamedev.net
* About to connect() to www.gamedev.net port 443 (#0)
* Trying 77.235.62.204... Connection refused
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host

[rip-off]

HTTPS is working for me. I resolve www.gamedev.net to 50.28.81.19., but it was resolving to 77.235.62.204 for me last night.

[Stephen R]

Hmm, maybe my ISP is caching an old record. nslookup for my ISPs DNS server, and google's.

$ nslookup www.gamedev.net
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
www.gamedev.net canonical name = gamedev.net.
Name: gamedev.net
Address: 77.235.62.204


$ nslookup www.gamedev.net 8.8.4.4
Server: 8.8.4.4
Address: 8.8.4.4#53
Non-authoritative answer:
www.gamedev.net canonical name = gamedev.net.
Name: gamedev.net
Address: 50.28.81.19

[Matias Goldberg]

HTTPS Seems to be working for me.

[Michael Tanczos]

It was a server issue that cropped up last night that went overlooked. It should be operational now.

If you live in Europe gamedev.net is 77.235.62.204, otherwise it is 50.28.81.19. The European server is a reverse proxy cache that caches a lot of our site content and gives European users quicker response times to the site.

[Stephen R]

Cheers for the quick resolution.