Error 502 - Bad Gateway

[badders]

Can anyone help? I am trying to deploy my site to a Fasthosts Windows with Load Balancing and ASP.NET server. When I test the network settings I get a "502 - Bad Gateway" error.

I've checked with Fasthosts, who say the issue seems to be with ts000001.pl timing out - in the htdocs/cgi-bin directory. (Fasthosts have a 15 second timeout on scripts) The only advice they could give was to check the installation guide on their knowledgebase then to refer back to Actinic.

I've trawled through the Actinic knowledgebase and also searched this forum, but can't find a definitive solution. Can anyone help?

__________________
Andy Baddeley
Head of Immersive
NMI Security plc

[Bruce]

Andy,

If you have load balancing enabled on the windows server then you are more likely to encounter problems. This can be confirmed by Fasthost support.

You can also find information on configuring actinic in the fasthosts knowledge base. Just search for actinic, there are only 4 entries.

A search for 'Fasthosts on a Windows Server' will produce some results that may be helpful. There are people using Fasthosts on Windows servers as long as Fasthost SSL is not involved.

Kind regards,

[badders]

Thanks for the reply Bruce.

I've checked all these threads out. Someone has tried disabling load blancing and that didn't work.

None of the other threads seem to give specific information on how someone has dealt with the 502 error problem. Most are to do with either SSL or other issues. I've tried the settings someone had posted but still the same results.

AB

[badders]

I've now completely given up on getting Actinic to work on a Fasthosts Windows 2003 server. I setup a Linux server with Fasthosts and it's working perfectly...

If anyone has actually got Actinic to work on a Fasthosts Windows 2003 (no SSL) I'l love to hear how they did it!

AB