IIS Reverse Proxy 502 error

%3CLINGO-SUB%20id%3D%22lingo-sub-1848707%22%20slang%3D%22en-US%22%3EIIS%20Reverse%20Proxy%20502%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1848707%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20setup%202%20Reverse%20Proxy%20servers%20behind%20a%20load%20balancer%20using%20IIS.%20Node1%20has%20been%20fully%20installed%20and%20configured%20and%20works%20fine%20but%20Node2%20after%20being%20installed%20and%20fully%20configured%20returns%20a%20502%20error.%20After%20enabling%20IIS%20logging%20there%20is%20no%20substantial%20issue%20that%20can%20be%20seen.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20researched%20the%20502%20error%20and%20tried%20the%20various%20troubleshooting%20approaches%20but%20to%20no%20avail.%20We%20have%20bypassed%20the%20Load%20Balancer%20and%20accessed%20the%20node%20directly%20and%20everything%20works%20fine.%20Could%20this%20be%20a%20routing%20issue%3F%20(All%20URL's%20are%20accessible%20from%20the%20node%20in%20question%2C%20re-write%20rules%20are%20exactly%20like%20Node1%20and%20all%20server%20communications%20from%20Node%202%20are%20fine)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20experienced%20this%20before%3F%20or%20can%20anyone%20offer%20some%20guidance%20in%20further%20troubleshooting%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1848707%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

Hi 

 

We have setup 2 Reverse Proxy servers behind a load balancer using IIS. Node1 has been fully installed and configured and works fine but Node2 after being installed and fully configured returns a 502 error. After enabling IIS logging there is no substantial issue that can be seen. 

 

We have researched the 502 error and tried the various troubleshooting approaches but to no avail. We have bypassed the Load Balancer and accessed the node directly and everything works fine. Could this be a routing issue? (All URL's are accessible from the node in question, re-write rules are exactly like Node1 and all server communications from Node 2 are fine)

 

Has anyone experienced this before? or can anyone offer some guidance in further troubleshooting the issue.

 

Regards

 

0 Replies