| Domain | Port | Description |
|---|---|---|
| update.logsign.com | 80, 443 | Update / Callhome |
| update2.logsign.com | 80, 443 | Update / Callhome |
| license.logsign.com | 80, 443 | License validation |
| repv2.logsign.com | 80, 443 | Threat Intelligence (TI) update |
| update.innotim.com | 80, 443 | Logsign update |
| update2.innotim.com | 80, 443 | Logsign update |
| remotes.logsign.com | 443 | Remote access / management |
| ppa.launchpad.net | 80, 443 | Ubuntu PPA packages |
| security.ubuntu.com | 80, 443 | Ubuntu security updates |
| archive.ubuntu.com | 80, 443 | Ubuntu packages |
| us.archive.ubuntu.com | 80, 443 | Ubuntu packages mirror |
| esm.ubuntu.com | 80, 443 | Ubuntu Extended Security Maintenance (ESM) |
| storage.googleapis.com | 443 | Cloud storage / dependencies |
Notes
- Both HTTP (port 80) and HTTPS (port 443) are listed for compatibility.
- If port 80 is not allowed, port 443 can be used exclusively for update operations.
- In this case, Ubuntu repositories defined in
/etc/apt/sources.listmust be updated to use HTTPS instead of HTTP to ensure successful package updates. - It is recommended to define firewall rules as Service/Application (HTTP/HTTPS) for flexibility and compatibility.