Permission denied

Help Hub
1

Hi Guys,

i am having some trouble and would like to see if i can get help here!

we have an SQL - SAP server on our network . when using Postman on Local network everything works good. but when trying via WAN i am getting permission denied.

Server Firewall is off

Port forwarding is working Fine

image
image1010Ă—939 18.1 KB

image
image1918Ă—1012 101 KB

2

Hi @dm-narsingh :waving_hand:. Welcome to the Postman Community :postman:.

Do you have a firewall or VPN installed? This looks like something on your network is blocking this traffic.

3

Thanks for sharing the screenshots. Here’s a quick breakdown of what I’m seeing:

  • First Screenshot:
    This appears to show an invalid certificate. I’m not sure if your request is using http or https, but if SSL verification is causing the issue, you can try disabling it in the settings.

  • Second Screenshot:
    This one is different—it shows a 403 Forbidden error. That usually means you don’t have permission to access the resource or path you’re trying to reach.

The good news is that the server is responding and seems to recognize your identity, so your JWT authentication token looks fine. This would normally generate a 401 error if this was the issue.

One quick question: when you mention WAN, are you referring to something inside your network or over the Internet? Firewalls or VPNs could be interfering, but since the server is replying and just denying access, that might not be the root cause.

1 Like
4

From WAN, “permission denied” usually means:

  1. Enable TCP/IP in SQL Server Configuration Manager and set the port (default 1433).

  2. Allow SQL Server Authentication (Mixed mode).

  3. Make sure the user login has CONNECT rights and isn’t IP-restricted.

  4. Test from a real external network (not the same LAN) — some routers block NAT loopback.

  5. SAP/SAP Router config must allow your WAN IP.

  6. Check ISP isn’t blocking port 1433 (telnet <public-ip> 1433).

If local works but WAN doesn’t → it’s almost always SQL/SAP network permissions or ISP block, not Postman.

5

@security-operator-91

That might be true if you’re connecting directly to the SQL database. But in this case, it looks like the person is trying to access the database using an API over HTTPS, which typically uses port 443.

The error message “permission denied” is coming from the API.

A 403 error as shown in the posters screenshot means the server received the request and the authentication was successful, but the user doesn’t have permission to access the requested resource.

A 404 error means the authentication worked, but the resource or path doesn’t exist.

A 401 error means the authentication failed completely.

If the request was badly formatted, you’d usually get a 400 error.

All of these usually mean that the server is contactable and is returning status codes.

If the server couldn’t be reached at all, you might see a 500 error or no response at all due to a timeout.

This may be related to a WAN, LAN, or firewall issue; however, at first glance, it appears that the authentication token being used does not have the necessary permissions to access the requested resource or path.