Ports to open in firewall
Elar Tammeraja
3-20-17
Which ports should be open in firewall in order to successfully run Standard ERP installation?
Aldevinas Katkus
5-5-17
Created byElar Tammeraja14:36 3 Oct 2018
Computer running Standard ERP installation needs to allow (only) outbound TCP/IP traffic to ports 80, 443, 444, 1401 and 2000 In case customer wants to limit to specific IP then this is the list of addresses: hansaworld.com:80 (ip - 54.195.252.100) 169
I guess downloads.hansaworld.com:80 should be added to this list, because installing CN fails with the error message about this address
Paul Timms
7-4-18
Should these ports be allowed from just the server, or should they be allowed from the clients too?
Paul Timms
7-5-18
And related to this, some systems only allow an IP address to be set rather than a domain. Are the IP addresses for these domains static? And if they do change due to a server move, will this be announced so customers with rules in place can update them?
Dejan R.
7-11-18
Created byPaul Timms12:47 4 July 2018
Should these ports be allowed from just the server, or should they be allowed from the clients too?
Hi Paul.
all above port should be allowed from server. From client should be allowed hansaworld.com:80
Dejan R.
7-11-18
Created byPaul Timms16:01 5 July 2018
And related to this, some systems only allow an IP address to be set rather than a domain. Are the IP addresses for these domains static? And if they do change due to a server move, will this be announced so customers with rules in place can update them?
Hi Paul.

We never change these IP addresses.
Regards
Elar Tammeraja
10-3-18
Computer running Standard ERP installation needs to allow (only) outbound TCP/IP traffic to ports 80, 443, 444, 1401 and 2000

In case customer wants to limit to specific IP then this is the list of addresses:

hansaworld.com:80 (ip - 54.195.252.100)
169.50.37.53:443
169.51.66.84:443
169.51.66.84:1401
downloads.hansaworld.com:80 (ip - 176.34.184.145)
downloads.hansaworld.com:443 (ip - 176.34.184.145)
cloudcontroller.hansaworld.net:444  (ip - 52.28.241.85)
- Finland: cloudcontroller.fin.hansaworld.net:500 (ip - 54.247.191.191)
- Australia: cloudcontroller.aus.hansaworld.net:444; (ip - 54.253.250.145)
- Latvia: cloudcontroller.lat.hansaworld.net:444 (ip - 54.247.96.79)
cloudcontroller.hansaworld.net:2000  (ip - 52.28.241.85)
- Finland cloudcontroller.fin.hansaworld.net:2000 (ip - 54.247.191.191)
- Australia cloudcontroller.aus.hansaworld.net:2000 (ip - 54.253.250.145)
- Latvia: cloudcontroller.lat.hansaworld.net:2000 (ip - 54.247.96.79)
Paul Timms
10-12-18
Are we certain that the client only needs access to hansaworld.com on port 80? I have seen several instances where e-mail validation works, but users are not then able to log in using their Standard ID, only their old username and password. The server is in the cloud and has full access to all the required IPs and ports, which suggests to me that something else is required on the client's firewall.

This appears also to have an impact on global users. When they try to switch company, they get "Very long string in getfield" errors. However, when I log in to their system as a global user, I can switch companies without any errors.

"We never change these IP addresses."
This isn't quite true, two of the IP addresses have changed recently, although it sounds like it wasn't HW who changed them.
Aldevinas Katkus
12-3-18
our client cannot use standard id and the firewall log shows serp tries to coonect to 169.50.37.57 port 443.
shall we open this too?
Aldevinas Katkus
12-3-18
the same for 52.28.241.85:80
Paul Timms
8-2-19
Once again, an IP address has changed without warning, causing some clients to not be able to log in. This time, https://lookup.hansaworld.com has changed from 79.125.108.192 to 169.50.37.53.


Please can we have advance notice of any changes to domain IPs so that customers can ensure their firewalls are updated before the change happens?
Martin A.
8-21-19
Hi Paul,

Sorry for late reply.

Sent this to Bjanka.

Regards,
Martin
Paul Timms
8-23-19
Hi Martin

Thanks. Our customer may have given us false information about the change of IP in this instance.

Paul
Martin A.
8-29-19
Hi Paul,

Got this from Bjanka:
Lookup's IP changed to 169.50.37.53 on 2018-09-20, which is a year ago.

But he is right, we should inform them if that happens again. It definitely didn't change on August 2nd 2019

Have a nice day ahead!

Thanks,
Martin
Aldevinas Katkus
7-26-21
Have these IPs changed?
Our client has failed requests:
2021-07-25 19:51:02 /THREAD(5) service call: LOOKUP to: 169.50.37.53:443 failed with: communications error
2021-07-25 19:51:02 ARA Unable to establish connection to: 18.156.208.209:1401 timed out
2021-07-25 19:51:13 /THREAD(5) service call: LOOKUP to: 79.125.3.115:443 failed with: communications error
Paul Timms
3-27-23
Is there an updated list of firewall requirements? For example, a white paper on cloud node setup mentions ports 5038, 5060 and 5061, but these are all common telephony ports.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
Andis Blicāns, Grasko
The above applies to the window when it is opened for the first time. If the window is already open and I choose Window/Restore Position, the window takes the correct position. Namely, the upper left ...
00:43 18 July 2024
Neil
Version: 2024-03-16 Server: Linux Client: MacOS Sonoma I am seeing multiple users in different locations getting logged off many times per day when idle sometimes after a few minutes of being awa...
20:09 17 July 2024