Re: [squid-users] Error 502 - Bad Gateway - www.allplanlernen.de

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Thu, 29 Dec 2011 13:21:20 +1300

>> Hallo, Mario,
>>
>> Du meintest am 28.12.11:
>>
>>> i am running Squid 3.1.0.14 and when i try to access
>>> www.allplanlernen.de i get a 502 error.
>>
>> Same here (squid 3.2.0.14):
>>
>> 502 Bad Gateway
>> nginx/0.7.67
>>
>>> It works without squid.
>>
>> Same here, too.
>>
>>> Does anyone know why?
>>
>> Seems to be a malformed web site.
>>
>> I've tested (without squid)
>>
>> lynx www.allplanlernen.de/themen/impressum.html
>>
>> and got the informations; looking with a browser (behind squid) onto
>> the
>> side gets
>>
>> Internal Error (check logs)
>>
>> and that's an error message for the website administrator, not for
>> me.
>>
>> Viele Gruesse!
>> Helmut

 On Wed, 28 Dec 2011 18:45:38 +0200, Eliezer Croitoru wrote:
> On 28/12/2011 17:58, Helmut Hullen wrote:
> Works on squid 3.2.0.8
> Eliezer
>

 The nginx server seems to be rotating through several states.

 For a few requests I get a web page saying:
   502 Bad Gateway
   ----------------
   nginx/0.7.67

 Then that changes to no page at all on a 500 status saying:
   Internal Error (check logs)

 (No HTML just the ASCII message as body.)

 Bypassing Squid and going directly I get a successful page load for a
 few seconds.

 Then this appears:

 HTTP/1.1 500 Internal Server Error
 Server: nginx/0.7.67
 Date: Thu, 29 Dec 2011 00:01:57 GMT
 Content-Type: text/html; charset=utf-8
 Connection: close
 Set-Cookie: PLAY_ERRORS=;Path=/
 Content-Length: 417

 <!DOCTYPE html>

 <html>
     <head>
         <title>Application error</title>
         <meta http-equiv="Content-Type" content="text/html;
 charset=utf-8"/>
     </head>
     <body>
                             <h1>Oops, an error occured</h1>
                             <p>
                     This exception has been logged with id
 <strong>68koe2246</strong>.
                 </p>
                         </body>
 </html>

 Note that *all* of these errors are internal problems with either nginx
 or the server behind it.

 Amos
Received on Thu Dec 29 2011 - 00:21:30 MST

This archive was generated by hypermail 2.2.0 : Thu Dec 29 2011 - 12:00:05 MST