{"action":"created","issue":{"url":"https://api.github.com/repos/abiosoft/caddy-docker/issues/145","repository_url":"https://api.github.com/repos/abiosoft/caddy-docker","labels_url":"https://api.github.com/repos/abiosoft/caddy-docker/issues/145/labels{/name}","comments_url":"https://api.github.com/repos/abiosoft/caddy-docker/issues/145/comments","events_url":"https://api.github.com/repos/abiosoft/caddy-docker/issues/145/events","html_url":"https://github.com/abiosoft/caddy-docker/issues/145","id":365337474,"node_id":"MDU6SXNzdWUzNjUzMzc0NzQ=","number":145,"title":"Serving on a interface that isn't specified inside the configuration file","user":{"login":"Starz0r","id":3914271,"node_id":"MDQ6VXNlcjM5MTQyNzE=","avatar_url":"https://avatars0.githubusercontent.com/u/3914271?v=4","gravatar_id":"","url":"https://api.github.com/users/Starz0r","html_url":"https://github.com/Starz0r","followers_url":"https://api.github.com/users/Starz0r/followers","following_url":"https://api.github.com/users/Starz0r/following{/other_user}","gists_url":"https://api.github.com/users/Starz0r/gists{/gist_id}","starred_url":"https://api.github.com/users/Starz0r/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Starz0r/subscriptions","organizations_url":"https://api.github.com/users/Starz0r/orgs","repos_url":"https://api.github.com/users/Starz0r/repos","events_url":"https://api.github.com/users/Starz0r/events{/privacy}","received_events_url":"https://api.github.com/users/Starz0r/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-10-01T07:24:47Z","updated_at":"2018-10-04T06:50:58Z","closed_at":null,"author_association":"NONE","body":"Before, I was not really sure where to post this between [Caddy](https://caddyserver.com), [Portainer](https://portainer.io), Let's Encrypt forums, and here, but I think after my findings today, I think opening the issue here is the best course of action.\r\n\r\nCurrently I'm experiencing an issue where using this image in Docker deployed from a Portainer interface gives me some issues, and has the Caddy executable exiting even though my certificates are returned successfully. I can successfully reproduce the issue on an DigitalOcean droplet on Debian 9.5 for x86-64 by pulling the image and running it, then editing the Caddyfile as follows and restarting the container.\r\n\r\n```\r\ndocker.domain.tld {\r\n     tls username@domain.tld\r\n\r\n     proxy / localhost:port {\r\n          transparent\r\n          websocket\r\n     }\r\n}\r\n```\r\n\r\nRestarting with this configuration yields the following issue that ends up in the logfile.\r\n\r\n```urn:ietf:params:acme:error:malformed - Error creating new order :: DNS name does not have enough label```\r\n\r\nThis error is pretty generic, and searching around for it yield not many result. But after many hours researching and asking around I came to the conclusion that this error is from this image ignoring some of my Caddyfile settings. When I attach a shell to the container and look for my certs, I can find that they are sent over successfully, meaning there is no issue there, so it seems that this image might have some defaults of it's own that still have some priority. \r\n\r\nI have a big suspicion that this image is requesting a cert for either `localhost` or `0.0.0.0` or `127.0.0.1`, which are all invalid by ACME standards. I'm not really sure why this is, even after I set my own Caddyfile which removes the `0.0.0.0` entry from the top of the file. Is there any way I can prevent it from attempting to register an invalid domain name? Everytime it does this, Caddy exits instead of just staying alive and not serving requests to that IP, meaning it will never actually try serving from interfaces I actually want."},"comment":{"url":"https://api.github.com/repos/abiosoft/caddy-docker/issues/comments/426904911","html_url":"https://github.com/abiosoft/caddy-docker/issues/145#issuecomment-426904911","issue_url":"https://api.github.com/repos/abiosoft/caddy-docker/issues/145","id":426904911,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNjkwNDkxMQ==","user":{"login":"Starz0r","id":3914271,"node_id":"MDQ6VXNlcjM5MTQyNzE=","avatar_url":"https://avatars0.githubusercontent.com/u/3914271?v=4","gravatar_id":"","url":"https://api.github.com/users/Starz0r","html_url":"https://github.com/Starz0r","followers_url":"https://api.github.com/users/Starz0r/followers","following_url":"https://api.github.com/users/Starz0r/following{/other_user}","gists_url":"https://api.github.com/users/Starz0r/gists{/gist_id}","starred_url":"https://api.github.com/users/Starz0r/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Starz0r/subscriptions","organizations_url":"https://api.github.com/users/Starz0r/orgs","repos_url":"https://api.github.com/users/Starz0r/repos","events_url":"https://api.github.com/users/Starz0r/events{/privacy}","received_events_url":"https://api.github.com/users/Starz0r/received_events","type":"User","site_admin":false},"created_at":"2018-10-04T06:50:58Z","updated_at":"2018-10-04T06:50:58Z","author_association":"NONE","body":"@abiosoft Yeah, it's an issue with this container. I decided to do a test by manually by obtaining the certificates and keyfile by hand, then asking Caddy to load it instead of giving it my email. The default behavior would be for this to successfully load my certs, then do nothing else, instead it loads my certs successfully AND does something else, which I'm not entirely sure of. I think it's trying to grab a certificate for `0.0.0.0`, but Let's Encrypt isn't keen on giving me the info on what site was attempted or what the info on the attempt was.\r\n\r\nSo yeah, it's something with the default behavior on this container. I hope this can be fixed soon! "}}
{"actor":{"display_login":"Starz0r"}}