This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error 500

We seem to be getting quite a few error 500s from various websites. From reading this seems to be a problem with the website but if I route through another router to the internet, the pages load fine so it has something to do with Astaro. An example of a site that we can't access through Astaro is www.yellowpages.com.au we receive the following error:

HTTP ERROR: 500 Internal Server Error
RequestURI=/siteEntry.do;jsessionid=20mftdhjapsho.yp2001_22123

Powered by Jetty://

There are quite a few other sites with a similar message when trying to access them.

We have http proxy using AD/NT authentication on Standard, the authentication doesn't make a difference.
We have tried with caching on and off - no difference.
We are using 6.101
I have tried adding yellowpages.com.au to the whitelist under cobian Filter and have tried with Cobian Filter off completely.

Any other ideas?

Jon

This thread was automatically locked due to age.

0 RFCat_vk_01 over 20 years ago

I just tried the yellow pages by clicking on the url in your message and it went through without an issue.
I have most of the proxies in operation and the http proxy is setup for https.

Ian M [:)]
Cancel
Vote Up 0 Vote Down

Cancel
0 VelvetFog over 20 years ago

I too tried your www.yellowpages.com.au link. It works fine from here.
I'm at my office, in behind an Astaro 6.101 box configured for transparent proxy.
Cancel
Vote Up 0 Vote Down

Cancel
0 SecApp over 20 years ago

Based on these results, sounds like packet loss or corruption on your circuit. You could see how the wget utility retrieves pages. It is much more resilient and will attempt retries. It requires you to download some files, but it's a handy utility.

If you see wget restarting at different spots in the page download, I would call your telco next (after you checked that the cables don't have any bulges in them, and know that all other intermediate network hardware, like switches and whatnot, are solid...)
Cancel
Vote Up 0 Vote Down

Cancel
0 SecApp over 20 years ago in reply to SecApp

Even simpler suggestion; what is a ping saying?
Try options to enlarge the packet size;
see if there is any packet loss...
Cancel
Vote Up 0 Vote Down

Cancel
0 flyingkiwi over 20 years ago in reply to SecApp

I have tried wget and I received the following:

C:\temp>wget --proxy=on www.yellowpages.com.au
--11:32:36--  http://www.yellowpages.com.au/
           => `index.html'
Connecting to 192.168.0.75:8080... connected.
Proxy request sent, awaiting response... 302 Moved Temporarily
Location: http://www.yellowpages.com.au/siteEntry.do;jsessionid=2sj5vk9awqlgx.yp
2003_22121 [following]
--11:32:36--  http://www.yellowpages.com.au/siteEntry.do;jsessionid=2sj5vk9awqlg
x.yp2003_22121
           => `siteEntry.do'
Connecting to 192.168.0.75:8080... connected.
Proxy request sent, awaiting response... 500 Internal Server Error
11:32:36 ERROR 500: Internal Server Error.

Doesn't help me much...no worries pinging the address.
Also due to having another router connected to same ADSL connection with different public ip address I have tested the connection (ISP) and it works fine, doesn't work through Astaro for some reason...probably simple...

Jon
Cancel
Vote Up 0 Vote Down

Cancel
0 flyingkiwi over 20 years ago in reply to flyingkiwi

Got it!!!!

Needed to turn anonymity from standard to none...don't know how this affects the security but at least it now works!

Jon
Cancel
Vote Up 0 Vote Down

Cancel
0 SecApp over 20 years ago in reply to flyingkiwi

Thanks for sharing that solution with us; I'm sure we'll be seeing a lot more posts about that one...
Cancel
Vote Up 0 Vote Down

Cancel
0 VelvetFog over 20 years ago in reply to flyingkiwi

I have never turned on the anonymity settings on my ASL boxes. It is good to know that it can cause problems.

As a general rule, when you are getting errors such as your HTML 500 error in your browser, browse the site using Firefox instead of Internet Explorer. Firefox has far better built in diagnostics, and can tell you the line number in the HTML code where the failure occured, while Internet Explorer will just leave you guessing, staring at the 500 error.
Cancel
Vote Up 0 Vote Down

Cancel