Configuration of your corporate firewall
GoBright users and devices several types of connections to function correctly.
Nearly every function use HTTPS to communicate outbound to the GoBright portal. But in some cases there might be exceptions for your specific case (e.g. when using on-premise Exchange).
In the overview below the different connections are show, these following ports and exceptions must be configured to make optimal use of the system.
Notes:
- 'Outbound' is from your corporate firewall to the GoBright platform
- 'Inbound' is from the GoBright platform inbound into your corporate network
| Applicability | Port / Name | Type | Usage |
| Always | Outbound 80 (optional) |
HTTP |
Optional redirecting HTTP to HTTPS for user convenience |
| Always | Outbound 443 |
HTTPS |
Traffic over HTTPS to the GoBright platform |
| When using Interact devices | Outbound 8883 |
MQTT |
Traffic over MQTT over TLS to the GoBright platform |
|
|
|||
| Always | *.brightbooking.eu |
URL |
For calls to the GoBright platform from devices |
| Always | *.gobright.com | URL | For calls to the GoBright platform from devices |
| Always | *.gobright.cloud | URL | For calls to the GoBright platform from devices |
| When using displays, Interacts or Gateways | NTP (UDP 123) DNS (UDP+TCP 53) |
NTP DNS |
Devices rely on NTP to get a correct date & time & DNS to reach the internet. |
| When using on-premise Exchange | Inbound 443 | HTTPS | GoBright platform connecting to the EWS of the on-premise Exchange |
| When using on-premise Exchange | Outbound 443 to *.gobright.cloud | HTTPS | Sending change notifications from on-premise Exchange to GoBright platform |
Please consult your IT department whether the connections above are allowed and accessible.
Advanced: Filtering inbound/outbound traffic based on IP-addresses
We publish our public IP-addresses, for advanced filtering requirements. If you implement ip filtering on your firewalls and systems, see the guidance below, and make sure to be subscribed to our status page for any changes in the IP addresses.
Change process of IP addresses
The IP addresses are static, but in some cases we need to commission or decommission IP addresses. This will be published as 'maintenance' on our status page, typically at least 1 week before the change becomes active.
Please make sure to subscripe to the status page, by signing up via the 'get updates' button on the status page, you will be updated if maintenance is published (e.g. if IP addresses change).
Notes:
- 'Outbound' is from the corporate firewall to the GoBright platform, e.g. a user or GoBright device connecting to the GoBright platform.
- 'Inbound' is from the GoBright platform to the internet, e.g. GoBright platform connecting to Office 365 / Microsoft 365 to synchronize data.
| Direction | IP address | State | Notes |
| Outbound | 13.69.68.10 |
Active |
- |
| Outbound | 52.137.36.77 |
Active |
- |
| Outbound | 52.166.220.108 |
Active |
- |
| Outbound | 52.236.160.173 | Active | - |
| Outbound | 20.93.228.151 | Active | - |
| Inbound | 52.233.130.50 | Active | |
| Inbound | 52.233.128.61 | Active | |
| Inbound | 52.233.135.180 | Active | |
| Inbound | 52.233.131.224 | Active | |
| Inbound | 52.233.135.227 | Active | |
| Inbound | 52.233.129.243 | Active | |
| Inbound | 52.233.128.247 | Active | |
| Inbound | 51.105.186.108 | Active | In use since: December 24, 2021 |
| Inbound | 51.105.189.190 | Active | |
| Inbound | 51.105.189.241 | Active | |
| Inbound | 51.105.190.95 | Active | |
| Inbound | 51.105.191.129 | Active | |
| Inbound | 51.105.191.194 | Active | |
| Inbound | 20.50.160.22 | Active | |
| Inbound | 20.50.160.101 | Active | |
| Inbound | 20.50.160.125 | Active | |
| Inbound | 20.50.160.226 | Active | |
| Inbound | 20.50.161.8 | Active | |
| Inbound | 20.50.161.228 | Active | |
| Inbound | 20.50.161.239 | Active | |
| Inbound | 20.50.162.22 | Active | |
| Inbound | 20.50.162.51 | Active | |
| Inbound | 20.50.162.110 | Active | |
| Inbound | 20.50.162.162 | Active | |
| Inbound | 20.50.162.165 | Active | |
| Inbound | 20.50.162.180 | Active | |
| Inbound | 20.50.162.200 | Active | |
| Inbound | 20.50.163.110 | Active | |
| Inbound | 20.50.163.135 | Active | |
| Inbound | 20.50.163.143 | Active | |
| Inbound | 20.50.163.167 | Active | |
| Inbound | 20.50.163.240 | Active | |
| Inbound | 20.50.163.255 | Active | |
| Inbound | 20.50.164.22 | Active | |
| Inbound | 20.50.164.48 | Active | |
| Inbound | 20.50.164.54 | Active | |
| Inbound | 20.50.164.119 | Active | |
| Inbound | 20.50.2.45 | Active | |
| Inbound | 20.76.202.176 | Active | In use since: December 8, 2022 |
| Inbound | 20.76.202.219 | Active | |
| Inbound | 20.76.202.251 | Active | |
| Inbound | 20.76.203.229 | Active | |
| Inbound | 20.76.205.16 | Active | |
| Inbound | 20.76.205.70 | Active | |
| Inbound | 20.101.200.78 | Active | |
| Inbound | 20.101.200.94 | Active | |
| Inbound | 20.101.200.121 | Active | |
| Inbound | 20.101.200.155 | Active | |
| Inbound | 20.101.200.187 | Active | |
| Inbound | 20.101.200.225 | Active | |
| Inbound | 20.101.200.229 | Active | |
| Inbound | 20.101.200.231 | Active | |
| Inbound | 20.101.200.232 | Active | |
| Inbound | 20.101.200.244 | Active | |
| Inbound | 20.101.200.245 | Active | |
| Inbound | 20.101.201.1 | Active | |
| Inbound | 20.101.201.4 | Active | |
| Inbound | 20.101.201.5 | Active | |
| Inbound | 20.101.201.11 | Active | |
| Inbound | 20.101.201.14 | Active | |
| Inbound | 20.101.201.21 | Active | |
| Inbound | 20.101.201.31 | Active | |
| Inbound | 20.101.201.33 | Active | |
| Inbound | 20.101.201.34 | Active | |
| Inbound | 20.101.201.38 | Active | |
| Inbound | 20.101.201.60 | Active | |
| Inbound | 20.101.201.73 | Active | |
| Inbound | 20.101.201.110 | Active | |
| Inbound | 20.50.2.79 | Active |
To see IP addresses we have used before, but are now decommissioned, please click the accordion below.