Actually I found out how to see the host. It's the tabsvc file in
So for sure the host server is there, but still can't connect!
So that means that it's not able to contact your Tableau Server repository database.
Assuming you already ran:
tabadmin dbpass --username readonly <YOUR PASSWORD>
...then restarted Tableau Server, it should work if the connection info is correct. Test it in Tableau Desktop--try creating a PostgreSQL connection with the same servername, database name (workgroup), port, username and password as you've specified in the vizalerts.yaml file. Play with it unti you can successfully connect in Tableau, then use the same info in the yaml file.
If it still doesn't work, you can dig into the Tableau Server logs relevant to PostgreSQL repository connections to see what the matter is. They're at:
[Tableau Install directory]\data\tabsvc\logs\pgsql
It says that no connection could be made because the target machine actively refused it in the logs.
I really appreciate your help Matt
That's weird. You should see these lines in the pg_hba.conf file located at [Tableau Install directory]\data\tabsvc\config\pg_hba.conf :
host all readonly 0.0.0.0/0 md5 host all readonly ::0/0 md5
That's stating that any attempt to connect to your postgresql server, from any host, using the readonly user will be approved so long as they have the password right. If those lines are not present, then something is wrong. If they're missing, don't add them to fix it, you will not enjoy living the life of manual config edits.
Arg it was the windows firewall on my tableau server! Thanks for all your help Matt, it's working fine now!
Glad to hear it, thanks for following up with the answer!
Can you please explain how you fix your firewall? I am getting exact same error and hope your step will help me to fix my issue.
Thanks in advance.
Basically I just went to the servers windows firewall settings and turned it off. Would recommend you check with the sys admin before you do that though.
Thanks for your reply. I was able to fix the issue.
Can you help me what exactly you have done to resolve this issue ?
Are you at #Data17 Conference ?