Overview
A common question when migrating to AppManager or troubleshooting issues is whether any URLs should be whitelisted or ports open to ensure stable AppManager operations. To ensure stable and efficient communications, you have to ensure that https://appmanager.gfi.com is reachable and a few local ports are not blocked.
Solution
The only strict requirement is that https://appmanager.gfi.com should be reachable from the server where the GFI Agent is installed. Make sure you can reach this URL on HTTP port (443) in a browser or with a curl.
- Let your internal devices initiate TCP connections to *:443
- Let your internal devices initiate UDP from :41641 to *:*
- Let your internal devices initiate UDP to *:3478
Summary
To ensure the proper functionality of AppManager, it is essential that the URL https://appmanager.gfi.com is accessible from the server where the GFI Agent is installed. This URL should be reachable via HTTP on port 443. Additionally, for optimal performance and connection speed, it is recommended to allow internal devices to initiate TCP connections to any destination on port 443, and UDP connections from local port 41641 to any remote port, as well as UDP connections to remote port 3478.
FAQ
-
What is the primary URL requirement for AppManager's functionality?
The primary requirement is that the URL https://appmanager.gfi.com must be accessible from the server where the GFI Agent is installed, specifically over HTTP port 443. -
Are there specific TCP or UDP port configurations recommended for AppManager?
Yes, for optimal performance, it is recommended to let internal devices initiate TCP connections on port 443, and UDP connections from local port 41641 to any remote port, as well as to remote port 3478. -
Can the HTTPS port 443 alone ensure proper operation of AppManager?
Yes, HTTPS port 443 is sufficient for all operations of AppManager, but additional UDP port settings can enhance connection speed and performance.