/
502 Bad Gateway Externally Site Cannot Be Reached Internally

502 Bad Gateway Externally Site Cannot Be Reached Internally

Owned by Knowledge Assistant
about 4 hours ago
1 min read
Description of Issue

All sites on an IIS Server are displaying Site Cannot Be Reached or 502 Bad Gateway

Context

  • IIS

  • Munis

  • Cashiering

  • Web Server

  • TCM

Cause

All hosted sites are deployed below the Default Web Site which has been stopped.

Resolution

  1. Connect to affected web server

  2. Open IIS Manager

  3. Expand Server > Sites

  4. Select Default Web Site  in left panel

  5. Under Manage Web Site on right side select Start  if possible

Additional Information