the reverse proxy
tuck only talks https, through a proxy you trust. here's nginx with certbot.
-
save this as
/etc/nginx/sites-available/tuck.conf, with your domain:server {listen 80;listen [::]:80;server_name tuck.example.com;client_max_body_size 32m;location / {proxy_pass http://127.0.0.1:8080;proxy_http_version 1.1;proxy_set_header Host $host;proxy_set_header X-Forwarded-For $remote_addr;proxy_set_header X-Forwarded-Proto $scheme;proxy_set_header Connection "";}} -
turn it on and add https:
sudo ln -s /etc/nginx/sites-available/tuck.conf /etc/nginx/sites-enabled/sudo nginx -t && sudo systemctl reload nginxsudo certbot --nginx -d tuck.example.comsay yes when certbot offers to redirect to https.
-
tell tuck to trust the proxy, in
.env:TUCK_TRUSTED_PROXIES=172.16.0.0/12then
docker compose up -dagain.
:::tip still says "https only"?
run docker compose logs tuck | grep audit to see the address requests come from, and put that in TUCK_TRUSTED_PROXIES.
:::