Running Weblate behind Caddy

[Karmalakas]

I'm trying to run Weblate on a TrueNAS SCALE as a custom app. I also have Caddy running there and all other apps seem to work fine, but even after solving all permission issues I can't make Weblate to work. I keep getting 502 error

Here's full Caddy log entry:

{
  "level": "error",
  "ts": 1737223268.1558733,
  "logger": "http.log.error",
  "msg": "dial tcp 192.168.1.11:18080: connect: connection refused",
  "request": {
    "remote_ip": "192.168.1.1",
    "remote_port": "43609",
    "client_ip": "192.168.1.1",
    "proto": "HTTP/2.0",
    "method": "GET",
    "host": "weblate.example.com",
    "uri": "/",
    "headers": { <...> },
    "tls": {
      "resumed": false,
      "version": 772,
      "cipher_suite": 4865,
      "proto": "h2",
      "server_name": "weblate.example.com"
    }
  },
  "duration": 0.00077199,
  "status": 502,
  "err_id": "vz3b75b11",
  "err_trace": "reverseproxy.statusError (reverseproxy.go:1373)"
}

I've tried with IP_BEHIND_REVERSE_PROXY: true in Weblate docker-compose config and without. Also tried header_up Host {host} in Caddyfile and without. Tried a bunch of other different combinations almost not knowing what I'm doind at that point...

I also have ports defined:

services:
  weblate:
    ports:
      - 80:18080

Upon Weblate startup I see this in the logs:

2025-01-18 18:28:31.395172+00:00nginx stdout | 127.0.0.1 - - [18/Jan/2025:18:28:31 +0000] "GET /healthz/ HTTP/1.1" 502 150 "-" "curl/7.88.1"
2025-01-18 18:28:31.395387+00:00nginx stderr | 2025/01/18 18:28:31 [crit] 333#333: *1 connect() to unix:/run/gunicorn/app/weblate/socket failed (2: No such file or directory) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /healthz/ HTTP/1.1", upstream: "http://unix:/run/gunicorn/app/weblate/socket:/healthz/", host: "localhost:8080"
2025-01-18 18:28:34.422613+00:00gunicorn stderr | [2025-01-18 18:28:34,410: INFO/328] Starting gunicorn 23.0.0
2025-01-18 18:28:34.422668+00:00gunicorn stderr | [2025-01-18 18:28:34,415: INFO/328] Listening at: unix:/run/gunicorn/app/weblate/socket (328)

Otherwise no noticeable errors

Although later, when all initial stuff happens, I see /healthz returns 200

2025-01-18 18:29:01.501412+00:00nginx stdout | 127.0.0.1 - - [18/Jan/2025:18:29:01 +0000] "GET /healthz/ HTTP/1.1" 200 12 "-" "curl/7.88.1"
2025-01-18 18:29:31.604977+00:00nginx stdout | 127.0.0.1 - - [18/Jan/2025:18:29:31 +0000] "GET /healthz/ HTTP/1.1" 200 12 "-" "curl/7.88.1"
2025-01-18 18:29:32.116685+00:00celery-celery stderr | [2025-01-18 18:29:32,116: INFO/MainProcess] Task weblate.utils.tasks.ping[f8d01fb0-9d3f-4e87-89a0-ff3c93edccd4] received
2025-01-18 18:29:32.270328+00:00check stderr | System check identified some issues:
2025-01-18 18:29:32.270374+00:00check stderr | 
2025-01-18 18:29:32.270384+00:00check stderr | INFOS:
2025-01-18 18:29:32.270391+00:00check stderr | ?: (weblate.I021) Error collection is not set up, it is highly recommended for production use
2025-01-18 18:29:32.270437+00:00check stderr | 	HINT: https://docs.weblate.org/en/weblate-5.9.2/admin/install.html#collecting-errors
2025-01-18 18:29:32.270447+00:00check stderr | ?: (weblate.I028) Backups are not configured, it is highly recommended for production use
2025-01-18 18:29:32.270454+00:00check stderr | 	HINT: https://docs.weblate.org/en/weblate-5.9.2/admin/backup.html
2025-01-18 18:29:32.270477+00:00check stderr | 
2025-01-18 18:29:32.270498+00:00check stderr | System check identified 2 issues (33 silenced).

P. S. Where does Weblate try to send an email during startup? I was getting an error it couldn't send one until I managed to configure that correctly

[nijel]

You should use 127.0.0.1:18080 for Docker (or specify IP address in port mapping in docker compose).

[Karmalakas]

Are you saying I should define like this?

services:
  weblate:
    ports:
      - 18080:18080

I thought 80 is the default port Weblate listens to 🤔 Or should I just remove this ports config at all? I'll try it a bit later

[Karmalakas]

I had ports the other way around and 80 🤦‍♂️ This fixed it:

    ports:
      - 18080:8080