makeplane
[bug]: https is not working on latest version in community edition
Is there an existing issue for this?
- [x] I have searched the existing issues
Current behavior
Version: v1.1.0
Installed in digital ocean.
https is now working: {"level":"warn","ts":1761650626.974629,"logger":"http.auto_https","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
Logs {"level":"info","ts":1761650626.9300778,"msg":"maxprocs: Leaving GOMAXPROCS=2: CPU quota undefined"} {"level":"info","ts":1761650626.9310203,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":1853153280,"previous":9223372036854775807} {"level":"info","ts":1761650626.9362805,"msg":"using config from file","file":"/etc/caddy/Caddyfile"} {"level":"info","ts":1761650626.95336,"msg":"adapted config to JSON","adapter":"caddyfile"} {"level":"warn","ts":1761650626.953873,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/Caddyfile","line":9} {"level":"info","ts":1761650626.9728487,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]} {"level":"info","ts":1761650626.9746244,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc0007d5880"} {"level":"warn","ts":1761650626.974629,"logger":"http.auto_https","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80} {"level":"warn","ts":1761650626.9770522,"logger":"http","msg":"HTTP/2 skipped because it requires TLS","network":"tcp","addr":":80"} {"level":"warn","ts":1761650626.9770768,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":80"} {"level":"info","ts":1761650626.9770794,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]} {"level":"info","ts":1761650626.977462,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"} {"level":"info","ts":1761650626.977478,"msg":"serving initial configuration"} {"level":"info","ts":1761650626.9822085,"logger":"tls","msg":"storage cleaning happened too recently; skipping for now","storage":"FileStorage:/data/caddy","instance":"5786b8d8-8cb8-4eb0-aa5d-ccca7d247d48","try_again":1761737026.9822054,"try_again_in":86399.999999344} {"level":"info","ts":1761650626.982329,"logger":"tls","msg":"finished cleaning storage units"}
Steps to reproduce
https://plane.example.com
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
v1.1.0
Have you tried adding a valid email address to CERT_EMAIL env
Also change SITE_ADDRESS with the full URL
For e.g. -
CERT_EMAIL="email [email protected]"
SITE_ADDRESS="https://plane.example.com"
@akshat5302 I faced the same issue. Adding schema and domain name to SITE_ADDRESS fixed the problem.
