• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2528
  • Last Modified:

receiving 502 Bad Gateway error when attempting to connect to IIS server... BUT can connect with IP Address fine!

Hello experts.

I cannot connect to my server using  http://www.quiss.com.au/knob (502 Bad Gateway error)

but I can connect using http://202.134.235.46/quiss/knob

I can't connect to anything on the server at all

e.g.

http://www.quiss.com.au/knob

http://www.quiss.com.au/quiss/knob

The zone file on my ISP/registrar's server seems to be fine and when I ping http://www.quiss.com.au it seems to pick up the IP.

I'm guessing it has something to do with firewall or IIS settings on my server. Please help!



0
Clever_Bob
Asked:
Clever_Bob
2 Solutions
 
bignewfCommented:
Hi Clever Bob,

I will need more info on this-  IIS logs which will show connection errors
Windows event logs on IIS server
and try WC3 Extended logging
Also, protocol analyzer such as wireshark to analyze http requests
Is there a proxy or ISA server upstream in this network?
Have your changed the IP address on the IIS virtual directories
or made any changes and not restarted IIS?
As a test, you could try opening port 53 (DNS) outbound in your firewall to allow DNS requests through
0
 
Praveen DMInfra Team LeadCommented:
Hi...
Plz check thi for a possible solution...

http://www.checkupdown.com/status/E502.html
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now