Proxy Server Troubleshooting

This chapter provides advice on locating and solving problems with the WebSTAR Proxy Server.

Proxy Server Troubleshooting

Check these entries if your Proxy server does not respond as expected.

See also How to Get Help , WebSTAR Debug Plug-In and General Server Troubleshooting Guidelines .

The WebSTAR Proxy server isn't working correctly

Check to see if the browsers are configured to work with your Proxy server. There is an option in browsers to specify a server and port to act as a Proxy, consult the browser documentation for specifics.
If your Proxy server is behind a firewall, the network administrator needs to ensure that specific ports are available for access. Or configure the specific IP address for the server machine to be outside the firewall.
The Proxy server is crashing. You may have too many connections. The maximum total connections that WebSTAR can handle, under Open Transport, is 498 (although very few sites would have the kind of bandwidth to come close to supporting that number). This total includes HTTP, FTP and Proxy servers, plus the 2 connections allocated to the Admin application.

Browsers display truncated downloads

If the origin server is very busy and the download is delayed for longer than the Proxy Timeout value, it will close the connection to the server. To increase the timeout value, see Proxy Connections .

Error 500 host could not be found

This may happen the first time a particular host is contacted, because the DNS server did not respond in time. It is a problem with slow DNS servers, and cannot be fixed by the proxy.