IP Addresses to Whitelist for CodeScene On-Premise
Overview
An on-premise CodeScene server needs outbound HTTPS access to portal.codescene.com on port 443 to activate and verify its license. Without it, you'll typically see a "Connect timed out" error at first activation, or a failed license check when the license is renewed.
This article is for administrators running CodeScene on-premise behind a firewall or proxy.
What to whitelist
Allow the hostname below wherever your firewall supports it. CodeScene's IP addresses can change, so a hostname rule is more robust than an IP rule.
The three IP addresses are the ones CodeScene uses for outgoing traffic (AWS region eu-west-1). They are stable today but may change, so always check the live list at codescene.io/meta.html or codescene.io/meta.json before updating firewall rules.
Behind a proxy? Set the proxy under Configuration → License → Proxy Server (host, port, username, password, or Kerberos) so CodeScene can reach the license service (guide).
No internet access at all? An admin can enable Global Offline Mode under Configuration → License. Offline mode only lasts for the current subscription term; CodeScene needs internet access again to verify a renewed license (guide).
Check the connection
From the CodeScene server, run
curl -I https://portal.codescene.com. Any HTTP response means the firewall allows the connection; a timeout means it is still blocked.If you use a proxy, run the same test through it, e.g.
curl -I -x http://<proxy-host>:<port> https://portal.codescene.com.In CodeScene, go to Configuration → License and activate or re-check the license. If it still fails, contact CodeScene support with the error message and your server logs.
Additional resources
Was this helpful?
Still need help? Ask the team