The connection details seems ok.
So if postgres is accepting connection on localhost but not on your ip, it is very likely because Postgres is not configured to accept such connection.
You could check the postgres log file, I would think you should see error like:
FATAL: no pg_hba.conf entry for host "172.29.50.129", user "postgres", database "postgres", SSL off
By default Postgres is configure to accept only connection from localhost.
You would need to update postgres pg_hba.conf file to allow connection from your ip.
See http://support.ptc.com/WCMS/files/173600/en/Installing_ThingWorx_8.1_1.3.pdf page 10 for some examples.
Then restart Postgres and try again .
You should also confirm that you are able to connect using pgadmin to Postgres using the exact same details as in the Installer (that i using the ip and not localhost)
As you suggested updated pg_hba.conf file and cross checked connectivity with IP using PgAdmin.
Its working fine.Also IP address accepted for postgreSQL while installing Thingworx server.
But getting below error.
You are getting a Permission denied error.
Could you make sure that when we start the installer you don't just double click on it but instead right mouse button and select Run As Administrator ?
Do you have something running on port 8080 on the host machine ?
For example do you have ThingWorx Platform running on the host machine ?
The output of netstat -abo can be useful for that.
So you do have something running on port 8080 on the host machine, so the Analytics Server cannot run also on port 8080.
From the log files the container is being created on port 8080, which is already in used, so that is probably what is leading to the Permission Denied.
During the installation, in the page ThingWorx Analytics Server Configuration, could you try entering a free port on the host machine for the field Tomcat External Port ?
After changing the port, installation was successful.
but again network error is coming.
Could you post the analytics.log file created with command docker logs analytics > analytics.log