-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
core_letsencrypt is not using the exposed port config key when http challenge is selected #2702
Comments
Same problem. I have port 8000 configured, but the logs report:
|
I did this today. The port you configure changes what port the add-in listens on, not what port the certbot uses. No idea if this is by design or not, but I simply worked around it by forwarding port 80 on my router to port 8000. It worked. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the issue you are experiencing
Even if the config key to change the external port is setup, the url used to validate the installation is not using it:
Detail: 1.2.3.4: Fetching http:https://foo.my.domain/.well-known/acme-challenge/xxxxx: Timeout during connect (likely firewall problem)
full log:
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Let's Encrypt
What is the version of the add-on?
4.12.7
Steps to reproduce the issue
System Health information
Aucune correction n'est actuellement disponible
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: