kamal: Deployment with 2.6.0 fails after upgrading to kamal proxy 0.9.0 with custom ports
In some of our projects we run caddy as reverse proxy in front of kamal-proxy on port 8080 and 8443 instead of the default ports 80 and 443. This worked fine until we were forced to upgrade kamal-proxy to 0.9.0 with kamal 2.6.0. Maybe there’s a new way to tell kamal that the proxy should be initialized with custom ports.
In the past we configured the custom ports with a .kamal/proxy/options file on the server:
--publish 8080:80 --publish 8443:443 --log-opt max-size=10m
With kamal-proxy 0.9.0 and kamal 2.6.0 it seems that this option file now leads to broken healthcheck configuration of the app. Instead of using the proxy configuration from the kamal deployment file the kamal deployment mechanism of the configured app seems to fall back to the kamal defaults (port 80 and /up endpoint). This is really strange.
Kamal proxy gets updated but automatic deployment of the app fails. Website is broken and no easy fix.
What am I doing wrong? Is there a new way to tell kamal that the proxy should use custom ports? Why does it brake the healthcheck configuration of the deployment. I don’t get it 😦
The Proxy configuration in the kamal deployment file looks like this:
proxy:
ssl: false
host: testtesttesttest.dev
app_port: 3000
healthcheck:
path: /healthz
interval: 2
timeout: 2
Why does the app_port in kamal-proxy deploy fall back to port 80?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15
2.6.1 is working fine with my minimal setup:
@djmb With kamal 2.6.1 everything works again! Thanks for the fast fix!
Thanks @marekls - seems like #1559 might have fixed it then? I’ve just released that in Kamal 2.6.1, so would be good to know if everything is working ok there.
If it is that doesn’t explain what the issue was though. Maybe related to the version of activesupport or something like that?