Hi all, I’m having an issue where OutSystems cannot call any external HTTPS endpoint using Consumed REST (Service Studio REST Method “Test” as well as runtime calls). This is not limited to our internal API; even public endpoints fail.
What I’m seeing:
https://stage.samsungspace.net/... → Unable to connect to the remote server
https://www.google.com/ → Unable to connect to the remote server
https://httpbin.org/get → Timeout
Context / notes:
This happens for both GET and POST methods.
The same SPACE endpoint works from my local machine via Postman (200 OK), so it doesn’t look like a request payload/header issue.
I already increased the REST method timeout (e.g., 120s / 500s) but the behavior remains.
Since even Google/httpbin fail, it seems like an OutSystems server outbound connectivity issue (firewall/proxy/DNS/SSL/TLS), but I’m not sure where to check/configure it properly.
Question: Has anyone experienced similar behavior (Consumed REST unable to reach any external HTTPS URLs)? If so, what should I check first—proxy settings, outbound firewall rules, DNS resolution, SSL/TLS trust store, or any OutSystems-specific configuration?
Thanks in advance.
Hi @JunJae Kang,
Check if the service is using TLS 1.3, if yes then there is a limitation on this.
Regards,
Sandeep.
Hi Sandeep,
Thank you for sharing your thoughts.
I tested the endpoints from my workstation using curl, and both https://stage.samsungspace.net/ and https://www.google.com/ returned HTTP/1.1 200 OK even when forcing TLS 1.2 (e.g., `curl -Iv --tlsv1.2 ...` / `--tls-max 1.2`).
Based on this, it doesn’t seem like the target service requires TLS 1.3 only. Since the same calls fail from our OutSystems environment (including public endpoints such as Google/httpbin), it seems more likely to be an outbound connectivity restriction from the OutSystems server/network (egress firewall/NAT, DNS, or similar).
Do you know any OutSystems-side settings or logs that could help confirm whether this is a server outbound/network restriction versus a TLS negotiation issue?
Best Regards,
JunJae Kang
Hi @JunJae Kang ,
This behavior points to an organization / infrastructure issue, not an OutSystems one. Some causes can be:
Outbound firewall restrictions
Missing corporate proxy
Increasing the REST timeout does not help because the connection is never established.
This should be checked with your network / infrastructure team, who can validate outbound connectivity from the OutSystems server and configure proxy/firewall/DNS as required.
@JunJae Kang : What you’re experiencing is normal and common in many enterprises. Typically, the OutSystems installation is isolated and not directly connected to external networks. In such cases, IP addresses and websites must be explicitly whitelisted so the OutSystems infrastructure can access them. This is usually handled by your security or infrastructure team.