-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App not reachable: Lets encrypt plugin fails & ports of container not exposed #291
Comments
I think the |
Here is the output:
|
What is the ip of your dokku host? |
For some reason, it was not possible to route to the lego container for the acme challenge. I was able to get around this by rewriting the plugin a bit. A fix will be coming, but I'm moving this to the letsencrypt repository for now. |
Instead, mount a directory that nginx can serve directly. Closes #291
Description of the problem
I installed dokku, created a new app try to generate an SSL certificate with Let's encrypt which fails.
Command:
dokku letsencrypt:enable project-explorer-backend
Error:
Could not obtain certificates: error: one or more domains had a problem: [api.backend.dataleap.dev] acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: 65.109.23.49: Invalid response from ...
Environment Information
My setup is rather simple:
Getting Started
page// +heroku goVersion 1.18
in go.mod (no docker file).Diagnostics:
Command:
dig -t A api.backend.xxx.dev
; <<>> DiG 9.10.6 <<>> -t A api.backend.xxx.dev
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64513
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;api.backend.xxx.dev. IN A
;; ANSWER SECTION:
api.backend.xxx.dev. 60 IN A XX.XXX.XX.XX
;; Query time: 72 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Wed Jan 18 19:04:20 CET 2023
;; MSG SIZE rcvd: 69
=> DNS settings seem to be correct. Subdomain is reachable.
Command:
docker ps
=> I think it's odd that no port is exposed of the app container.
Command:
dokku nginx:show-config project-explorer-backend
Output:
Command:
dokku proxy:ports project-explorer-backend
Output:
dokku report project-explorer-backend
outputThe text was updated successfully, but these errors were encountered: