Public link with Nginx/CloudFront get 403

[Ben Rieger]

I'm trying to map public links path to a shorter path.
I'm using a Nginx reverse proxy.
The same happens with CloudFront.

This is the configuration:

---

server {
  listen 80;

  location /  {
    proxy_pass https://my-domain.atlassian.net/;
    proxy_http_version 1.1;
  }
  location /testdoc {
    proxy_pass https://my-domain.atlassian.net/wiki/external/SOME_PUBLIC_LINK_ID;          proxy_http_version 1.1;
  }
}

---

When I go to localhost:80/wiki/external/SOME_PUBLIC_LINK_ID everything works but when I go to localhost:80/testdoc I get the error "We couldn't find what you're looking for".
I can see that one of the requests to /cgraphql "internalFrontendResource" get 403.

[Srinatha Tondihal]

Hello, 

The issue is that Confluence Cloud expects the full original URL path (like /wiki/external/SOME_PUBLIC_LINK_ID). When you map /testdoc to that path via Nginx, the main page might load, but some internal requests (like /cgraphql) get confused because they rely on the original structure or domain, and that can lead to 403 errors.

A few things to consider:

• Confluence Cloud enforces strict rules for paths, origins, and CORS, so proxying to a different path often breaks resource loading or API calls.

• Using a redirect (so /testdoc just redirects the browser to the full Confluence URL) usually works better than proxying.

• If you must use a reverse proxy, try to preserve the original path structure as much as possible.