KNOWLEDGE BASE

Tableau Server Gateway Service Error - Could not bind to address - No listening sockets available


Published: 26 Jun 2019
Last Modified Date: 23 Mar 2022

Issue

http://localhost redirects to ubuntu Apache landing page. TSM Web UI is only accessible at https://localhost:8850, but shows "server is starting".

 

Environment

  • Tableau Server 2019.1.1
  • Linux Ubuntu 16.04 LTS
  • Windows

Resolution

Linux:

If running Ubuntu 16.04 LTS, you may find apache2 running on port :80, inhibiting Tableau Server from being able to use the port. Disabling apache2 opens the port and stopped the behavior of being redirected to the Ubuntu Apache landing page. 

Open command line and review what service is running on port 80:    
Check status of apache2   

netstat -anbo | findstr :80
If apache2 is running, that is likely what's occupying port 80. 

To resolve the issue on Linux:
  1. Stop the service running on the port 80.
  2. Check on TSM or Tableau Server status page that gateway service got started.

Windows:

Open command line and review what service is running on port 80:
netstat -anbo | findstr :80
To resolve the issue on Windows:
  1. Use 'net stop http' will help to identify local services dependent on the http service - Say no after the list is displayed
  2. Open the services.msc
  3. Terminate the service running on port 80.
  4. Check on TSM or Tableau Server status page that gateway service got started.

Cause

Other services are running on port :80 blocking Tableau Server from accessing.
Did this article resolve the issue?