Gateway Timeout

Madgic · Post by **Madgic** » 11 Nov 2003, 23:49

I've been trying to access a website and keep getting this message:

Gateway Timeout
The following error occurred:

 A gateway timeout occurred. The server is unreachable. Retry the request. 


-----------------------------------------------------------------------
Please contact the administrator. 

 :?: 

Help?

Chromium · Post by **Chromium** » 12 Nov 2003, 00:10

I got that error too a while ago.I fiddled with my Security settings ,reinstalled my Tcp/Ip protocol,deleted all my cookies,refreshed the history,reinstalled Internet explorer,formatted my harddrive,bought another modem,replaced my monitor,sold my motherboard and bought anoter pc from some dude in Florida.

And still the problem persisted...

I think it's either the website itself or perhaps you should check your security settings....

Madgic · Post by **Madgic** » 12 Nov 2003, 00:19

I think it must be the website. www.forumsigs.com Just can't access it although all my pics are working. Even did a Google search to see if they'd changed their name again, but got the timeout error message from their link too.

Ah well, can't post any new joke pics tonight!

lancelot · Post by **lancelot** » 12 Nov 2003, 09:44

They turn into a pumpkin at Twelve! They are up now.

Madgic · Post by **Madgic** » 13 Nov 2003, 05:07

Lancelot

I suppose you only know about shopping malls eg Gateway

. . .

where babes hang out?!

05h45

Should have Asked Jeeves in the first place! Did a search and found this, so I thought I'd post it here for the improvement of your General Knowledge!

504 - Gateway timeout

Introduction
A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request.

This usually means that the upstream server is down (no response to the gateway/proxy), rather than that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.

504 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '504'.

Resolving 504 errors - general
This problem is entirely due to slow IP communication between back-end computers, possibly including your Web server. Only the people who set up the network at the site which hosts the Web server can fix this problem.

Resolving 504 errors - CheckUpDown
Use of proxies and caching is increasing on the Web. Our CheckUpDown robot will always try to 'drill through' to the real computer that actually hosts your Web site, but we do not have complete control over where our HTTP request actually ends up. If only one link in the chain of computers dealing with our HTTP request is broken, then an error such as 504 can easily occur.

Please contact us (email preferred) whenever you encounter 504 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of your Web server software so that they can review the flow of IP data traffic between various computers under their control. However this is not an easy error to sort out, because the ebb and flow of Internet traffic makes this type of error very transient.

I can see clearly now

It's probably Telkom's lousy slow service slowing everything down! Oh for more bandwidth!

lancelot · Post by **lancelot** » 13 Nov 2003, 07:55

Look Madgic I know that you are grouchy at 05:00 in the morning after a long nights work? Anyway Jeeves told you the same thing that the babes at the Gateway Mall told me, that is that there is nothing you can do about it but to hang in there and try again later!

Babes Rule OK!

jee · Post by **jee** » 13 Nov 2003, 07:57

Lance,

Babes don't like to "hang in there"!

lancelot · Post by **lancelot** » 13 Nov 2003, 08:10

Is this some sort of Durban Darlings Conspiracy? I am going into my corner to cry and..........

jee · Post by **jee** » 13 Nov 2003, 08:31

There, there, smooch, smooch - have another tissue...

Post by **Cameron_Losco** » 13 Nov 2003, 11:46

So is the problem solved or not?

Madgic · Post by **Madgic** » 16 Nov 2003, 05:55

Cameron Losco wrote:

So is the problem solved or not?

Yes, it is, thank you Cameron. But, no doubt it will happen again, usually when I've run out of space on my own websites or when I need something I've got stored at Forumsigs. C'est la vie!

lancelot wrote:

Look Madgic I know that you are grouchy at 05:00 in the morning after a long nights work?

Moi? Grouchy? First thing in the morning?

You're lucky you're in Cape Town, darlin' or I'd rattle your armor real good! I'm a little ray of sunshine in the morning . . .

Madgic · Post by **Madgic** » 16 Nov 2003, 07:23

Damn! I spoke too soon! The same thing just happened again! A couple of hours ago everything was OK, now the only pic working from Forumsigs is Maboots avatar! Plus I can't access the site again - gateway timeout. What I don't understand is why my avatar still works but anything else doesn't?