Weird Error

Posts: 341 · Posted: Tue Nov 28, 2006 12:39 am

Today I received a very weird error I have never received before from the server:

Code:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /xml/create_captchas.

Reason: Error reading from remote server

Apache/2.0.52 (Red Hat) mod_fastcgi/2.4.2 DAV/2 FrontPage/5.0.2.2635 mod_ssl/2.0.52 OpenSSL/0.9.7a SVN/1.3.2 Server at mydomain.com Port 80

What does this mean?

Posts: 410 · Posted: Wed Nov 29, 2006 2:48 pm

Since FrontPage is mentioned, might it be that server doesn't have FrontPage extensions? Such would be a rare event.

(a dummy's guess)

Posts: 60 · Posted: Wed Nov 29, 2006 5:21 pm

Was this error seen on this server, or your own server? I was testing a new captcha on monday, and it could be quite possible there was an error there, but i was working on the 'test' forum... so if it affected the live forums, i need to make sure I didn't 'misplace' anything.

Posts: 341 · Posted: Wed Nov 29, 2006 10:52 pm

Darell,
that was on my srvr - you see my own captcha system is low overhead in that I creat a bunch of images (24) with easily readable text, but warped and gradiant with common phrases like place etc. and then I save those files with their text.gif. I run a script that creates a random number symbolic link to the file, and then enters it in the database. A random captcha image is retrieved, and not generated. Good to hear you're testing a new captcha system.

Posts: 3 · Posted: Mon Dec 11, 2006 1:07 pm

So comprug did you solve ur problem?
I'm interesting final of this story Smile

Posts: 341 · Posted: Mon Dec 11, 2006 9:42 pm

Actually, I did solve my problem. I use a special configuration which involves for APACHE to proxy requests to port 4101 where the app is processed. I restarted the service at port 4101, yet Apache didn't acknowledge that the proxy server had come back. after restarting my vserver, and waiting for Apache to recognize the proxy server, the 502 Gateway error was gone. Since I am (or users of this) are at most 5 in 60,000 clients support didn't know what this was until I told them about my use of this service at port 4101. Once they knew, they resolved it quickly.