1 Reply Latest reply on Apr 3, 2020 4:35 PM by Heyward Drummond

    Tableau MAPS(Satellite) /Connection Error


      Hi Folks


      As you can see below on the left is a report with satellite map which works fine , then on the right is the same map keeps scrolling.  I have white listed all the below urls on node1 and node2 tableau server , reference Accessing base maps in 2019.2 onwards  .But i am getting this issue on and off . Can any one guide me on how i can fix this .


      FYI: Other reports with maps does work.










      • mapbox.com
      • www.mapbox.com
      • api.tiles.mapbox.com
      • a.tiles.mapbox.com
      • b.tiles.mapbox.com
      • c.tiles.mapbox.com
      • d.tiles.mapbox.com



      Thank you!




        • 1. Re: Tableau MAPS(Satellite) /Connection Error
          Heyward Drummond

          When I have seen this in customer servers, it's almost always a firewall that is blocking access to the map servers.


          One way to test is this:


          1. install the same version Tableau Desktop on the Tableau Server

          2. Try to load the same workbook on Desktop and observe

          3. If it works great, it means that the query to the outside world worked without firewall using a user account (since you have to register a license)

          4. If you get the same blocking, then it is that firewall blocking all traffic on the server


          You can force client side browser. It may have been turned off by using this command:

          tsm configuration set -k vizqlserver.browser.render -v false.  (that turns it off and makes the server go out to the map servers)


          tsm configuration set -k vizqlserver.browser.render -v true (turns it one and send mapping to the browser of the client for rendering)


          Try this: at the end of the browser url that is circling, add this



          That will test if client side rendering is on or off

          see here: Configure Client-Side Rendering - Tableau


          It's worth checking your firewall again. It might be a combination of local Windows Server firewall and/or the network firewall or a faulty proxy server not working properly.


          It's worth using a network trace tool to see the flow of traffic out from that server.



          1 of 1 people found this helpful