Container Jira behind nginx proxy timing out on gadget url/internal connections

Question

I have a docker cluster running jira, but I can't seem to get the gadget URL to pass. I have the base URL set to "jira.xxx" My docker compose file looks like ``` services: jira: image: container_name: jira networks: - jira_network ports: - 8070:8070 volumes: ... extra_hosts: - "jira.xxx:" nginx-proxy: image: nginx:latest container_name: nginx-proxy networks: - jira_network ports: - 80:80 - 443:443 volumes: ... depends_on: - jira networks jira_network: driver: bridge ``` My nginx proxy is standard with ``` server{ listen 443 ssl; server_name jira.xxx ssl stuff location / { proxy_pass http://jira:8070; proxy_set_header Host $host; proxy_set_header ... (x real ip, x forwarded for, x forwarded proto }} server { listen 80; server_name jira.xxx; return 301 https://$host$request_uri; } ``` The server works perfectly for everything but the gadget. If I remote into the jira container and attempt a "curl -v jira.xxx" then I can see that it hits the host IP as expected, but then the connection times out. Any ideas?

Lucas Modzelewski _Lumo_ · Answer

I asked chat GPT, here is what it suggested: It sounds like your nginx proxy might be hitting a timeout or buffering issue when Jira gadgets are loaded. Here are a few things to check in your nginx configuration: ✅ Increase proxy timeout values → Add or adjust these settings in your nginx config: proxy_read_timeout 300; proxy_connect_timeout 300; proxy_send_timeout 300; ✅ Increase buffer sizes → Sometimes gadgets fail due to insufficient buffer: proxy_buffers 16 64k; proxy_buffer_size 128k; ✅ Check max body size (if POST requests are failing) client_max_body_size 10m; ✅ Pass correct headers → Ensure you’re passing these to avoid breaking the gadgets: proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; ✅ Jira base URL → Make sure Jira’s base URL (in Jira system settings) matches the public URL behind nginx. If you apply these and still hit timeouts, check: Jira server logs (atlassian-jira.log) nginx error logs