My Viewport doesn't work with a proxy server setup

Symptom

If your Confluence installations runs behind a reverse-proxy or load balancer, you should make sure that both Confluence and the proxy are configured correctly. Some advanced setups, for example running a viewport on a different domain than Confluence, require that values like the URL scheme, the server name, and the server port are correctly passed to the viewport by Tomcat, the enclosing container.

PDF or Word exports from within viewports cannot be downloaded if the viewport domain is different from the Confluence base URL’s domain

Common effects of an incomplete configuration are:

• Viewports with a custom domain name are not reachable

• Confluence rejecting certain requests whose server name does not match the name of the host. 

  • For example: POST requests to /rest/webResources/1.0/resources that fail with a status code of 403

Learn more about how to setup custom domains and reverse proxies in Viewport.

Scroll Viewport Proxy Debugger

Scroll Viewport offers a proxy debugger UI which helps you to debug your proxy settings.

You can reach the proxy debugger via:

<confluence-base-url>/plugins/servlet/scroll-viewport/proxy-debugger

Example output

The debugger UI will output information about the following settings for example like this:

Value = the current value Viewport receives.

Expected = the value Viewport expects to receive.