There are 3 updates, 1 comment.
 
 
XWiki Docker images / cid:jira-generated-image-avatar-8e0d83b2-d04a-44c5-84a3-09f2a493f2e0 XDOCKER-340 Open

Tomcat Configuration for Reverse Proxy

 
View issue   ยท   Add comment
 

3 updates

 
cid:jira-generated-image-avatar-84a1d5e8-02ac-4c7c-adb5-dbaee544bf58 Changes by Vincent Massol on 17/Jul/26 17:13
 
Assignee: Vincent Massol
Resolution: Invalid
Status: Open Closed
 
 

1 comment

 
cid:jira-generated-image-avatar-84a1d5e8-02ac-4c7c-adb5-dbaee544bf58 Vincent Massol on 17/Jul/26 17:12
 

Hi Andreas, thanks for the report. This turns out to be a configuration question rather than a bug in the XWiki Docker image, so let me clarify the two things that are tripping you up and point you to the right resources.# Docker published port vs. Tomcat's port. With -p 8084:8080 (or ports: ["8084:8080"] in Compose), Docker maps host port 8084 to container port 8080. Tomcat inside the container always listens on 8080 - changing the published host port does not change Tomcat's connector. So you should not set the connector's port or proxyPort to 8084. This is standard Docker port-mapping behaviour (see Docker's own documentation).

  1. What proxyName/proxyPort do. They do not change which port Tomcat listens on; they tell Tomcat what host/port to report to XWiki so it generates correct links. They must match the public address your browser uses to reach the reverse proxy - e.g. proxyName="mywiki.example.com", proxyPort="443", scheme="https", secure="true". Neither 8080 nor 8084 is correct here unless users connect directly to that port. The recommended approach is to let Tomcat read the X-Forwarded-* headers from your proxy via a RemoteIpValve instead of hardcoding these values. This is standard Tomcat/XWiki configuration, fully documented here: https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/InstallationWAR/InstallationTomcat/#HHTTPreverseproxy
  2. The "Connection refused" error is almost certainly unrelated to proxyName/proxyPort - it indicates a network-reachability problem between your reverse proxy and the container. A common cause is the proxy targeting localhost:8080 while XWiki runs in a different container (it should target the XWiki service/container name on a shared Docker network, port 8080).

Note that the screenshots attached to this issue didn't render. Since this is a configuration/support question rather than a defect in the image, I'm closing it as Invalid. If you're still blocked after checking the above, the best place to get help is the XWiki forum (https://forum.xwiki.org/) - please paste your reverse-proxy config, the ports/network section of your docker-compose.yml, and the full "Connection refused" stack trace as text.