...
The dRofus client communicates with the dRofus database via TCP port 5432 and port 8180 443 (HTTPS) for the report generator. In order to allow for such communication, these ports need to be open towards the database server.
For projects where dRofus' server is utilised, this means that any firewalls have to allow for outgoing TCP traffic on port 5432 (database traffic) and port 8180 443 (HTTPS) (reports and file uploading) against <servername> (depending which server is used)
Some clients/projects have their own dRofus servers, so traffic has to be permitted to the server specified by the user upon log in. Traffic to the database server is channelled via SSL.
| Server | IP Address | Ports | Region |
34.225.129.63 13.210.210.38 | 5432 443 8180 | USA and South America | |
adm-ca.drofus.com52.60.201.6 | 52.60.201.6 | 5432 443 8180 | Canada |
| au.drofus.com reports-au.drofus.com | 54.79.1.114 | 5432443 | Australia, New Zealand & Asia |
| db2.nosyko.no | 195.159.92.252 | 5432 8180 | Europe |
IFC Model Server
The dRofus client communicates with the IFC model server via TCP port range 9090-9095 for the Americas, TCP port range 9090-9102 for Europe and TCP port range 9090-9093 for Asia-Pacific.
For projects where dRofus' Model Server is utilized, the firewall must allow outgoing TCP traffic for at least one of these ports against <servername> (depending which server is used).
| / Norway |
| eu.drofus.com |
| 18. |
| 157. |
| 51. |
...
| 162 | 5432 | Europe / Germany |