Allowlisting oneclick™ IP addresses
Add the IP addresses appropriate for your use case to the Allowlist (formerly Whitelist) in your firewall.
oneclick™ Core & oneclick™ Mesh
If your firewall restricts outgoing traffic,
- add the public IP address of the website you use to access oneclick™ on port 443 TCP (https) to the Allowlist.
- If you are using the oneclick™ mesh to connect to oneclick™, also add the public IP address and port 4242 UDP to the Allowlist.
| Public IP address | |
|---|---|
| Core international: oneclick.services | 168.119.21.4: 443 (TCP) |
| Core Germany: de.oneclick.services | 80.158.38.225: 443 (TCP) |
| oneclick™ Mesh Lighthouse 01 | 149.102.141.223: 4242 (UDP) |
| oneclick™ Mesh Lighthouse 02 | 37.120.175.71: 4242 (UDP) |
| oneclick™ Mesh Relay 02 | 202.61.251.49: 4242 (UDP) |
Tip: Assign "wildcards" - this will include all subdomains of the domain in your allowlist. To do this, enter a * in front of the domain, e.g. *.oneclick.services.
oneclick™ Delivery Cluster
If clients should access oneclick™
Add the ingoing IP address or the DNS entries for port 443 TCP (https) to the Allowlist (formerly Whitelist).
- Do you want to use 2-way audio e.g. for a phone system or
- do you receive an error message for the image display or
- is the transmission of moving images very slow or
- is the upload and download very slow?
Then it may be that WebRTC is not supported by your browser or is blocked by your firewall.
- Use this link to check if WebRTC works for you.
- Make sure that your firewall does not block outgoing UDP high ports and add the IP addresses or DNS entries of the turn server on port 443 (TCP & UDP) to the allowlist.
If oneclick™ should access your server
Add the outgoing IP address to the allowlist on all firewalls (Windows Firewall, hardware firewalls, network security groups, etc.) that shield your systems from the internet for the port of your use case (RDP, VNC, etc.).
Not sure which is the correct data center? Check your system data and look under "Datacenter".
| Data center | DNS entrys | Ingoing IP address | Outgoing IP address |
|---|---|---|---|
| Germany – Central | |||
| Streaming & Gateway | ocview2.oneclick.services | 168.119.21.4 | 168.119.21.5 |
| Hybrid Drive | drive.oneclick.services | ||
| Turn server | hetzner-fra-turn.oneclick.services | 168.119.21.4 | |
| Mesh Relay 01 | mesh-relay-live-01.oneclick.services | 35.204.206.63 | |
| Germany – Magdeburg | |||
| Streaming & Gateway | otc-eu-de-ocview2.oneclick.service | 80.158.19.214 | 80.158.20.29 |
| Hybrid Drive | otc-eu-de-drive.oneclick.services | ||
| Turn server | otc-eu-de-turn.oneclick.services | 80.158.54.227 | |
| Mesh Relay 01 | mesh-relay-live-04.oneclick.services | 164.30.4.237 | |
| Switzerland - Zurich | |||
| Streaming & Gateway | gc-europe-west6-ocview2.oneclick.services | 34.65.198.206 | 34.65.148.34 |
| Hybrid Drive | gc-europe-west6-drive.oneclick.services | ||
| Turn server | gc-europe-west6-turn.oneclick.services | 34.65.145.206 | |
| Mesh Relay 01 | mesh-relay-live-02.oneclick.services | 34.65.249.240 | |
| USA East Coast - Ashburn | |||
| Streaming & Gateway | hetzner-useast-ocview2.oneclick.services | 5.161.31.207 | 5.161.31.207 |
| Hybrid Drive | hetzner-useast-drive.oneclick.services | ||
| Turn server | hetzner-useast-turn.oneclick.services | 5.161.31.207 | |
| Mesh Relay 01 | mesh-relay-live-03.oneclick.services | 34.139.113.168 |