Open thegbert opened 2 years ago
Hi @thegbert
Thanks for sharing your finding.
Please can you share:
Happy to investigate, but need further information.
Apologies for not including that earlier:
Thanks!
I went through various build logs, but couldn't determine any failure or mismatch of container hash numbers yet.
Having that said, the add-on follows same build workflows as for example the hassio-addons, so I am wondering why other add-ons won't show the same behavior.
To help me continue my hunt, would you mind sharing your add-on logs after starting the add-on? Ideally also your Caddyfile? Feel free to replace your personal information in both of them.
Sure... add-on logs after starting here:
[cont-init.d] 00-banner.sh: exited 0. [cont-init.d] 01-log-level.sh: executing... Log level is set to INFO [cont-init.d] 01-log-level.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. INFO: Prepare Caddy... INFO: Use built-in Caddy v2.4.6 h1:HGkGICFGvyrodcqOOclHKfvJC0qTU7vny/7FhYp9hNw= INFO: Prepare Caddyfile... INFO: Caddyfile found at /share/caddy/Caddyfile INFO: Run Caddy... {"level":"info","ts":1644782896.9032063,"msg":"using provided configuration","config_file":"/share/caddy/Caddyfile","config_adapter":""} {"level":"warn","ts":1644782896.9101617,"msg":"input is not formatted with 'caddy fmt'","adapter":"caddyfile","file":"/share/caddy/Caddyfile","line":2} {"level":"info","ts":1644782896.914259,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["localhost:2019","[::1]:2019","127.0.0.1:2019"]} {"level":"info","ts":1644782896.9163141,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443} {"level":"info","ts":1644782896.9180372,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"} {"level":"info","ts":1644782896.9212222,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["subdomain.qualifieddomain.net"]} {"level":"info","ts":1644782896.922158,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00053dd50"} {"level":"info","ts":1644782896.922956,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/ssl/caddy"} {"level":"info","ts":1644782896.9298792,"logger":"tls","msg":"finished cleaning storage units"} {"level":"info","ts":1644782897.056298,"msg":"autosaved config (load with --resume flag)","file":"/data/caddy/autosave.json"} {"level":"info","ts":1644782897.0567362,"msg":"serving initial configuration"}
Caddyfile attached below
Hi @thegbert
Having a look at the provided information I can't determine any string config or notice any irregular log output.
Having that said, I am running out of ideas what and how to check next, so I have applied the label "Help wanted".
One last question. Please could you try another version and check if you receive the same output?
Otherwise I am uncertain how to help further :-(
Has this been solved?
No, because reason is uncertain, and no further reporting happened. Help is appreciated.
No, because reason is uncertain, and no further reporting happened. Help is appreciated.
Okay @einschmidt . Looks like caddy is trying to access setup.cgi
which is a the "Common Gateway Interface", a internal address used to control Apache Web Servers.
I would say that the reporter (@thegbert ) should explain thier setup more. Just from the logs it is hard to tell. Maybe an traffic analysis like a Wireshark dump including the suspect package?
Been receiving multiple firewall blocked requests for pulls after installing add-on in Home Assistant, My firewall lists Home Assistant as trying to post GET requests to:
Messages stopped after stopping Caddy-2 add-on.