You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let’s Encrypt fails validation (returns 404) when the Apache VirtualHost is defined as *:80, and starts working properly once it's explicitly changed to <VirtualHost [public-ip]:80>. Include:
The test showing .well-known returns 404 until the change
Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: test.actinolix.net
Type: unauthorized
Detail: 85.248.128.60: Invalid response from http://test.actinolix.net/.well-known/acme-challenge/Ne_bnuI69J5gmP-7czu1EZvywH0dsAW8D3sDSYvoU4U: 404
Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.
2025-04-11 13:31:09,388:DEBUG:certbot._internal.error_handler:Encountered exception:
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/certbot/_internal/auth_handler.py", line 108, in handle_authorizations
self._poll_authorizations(authzrs, max_retries, max_time_mins, best_effort)
File "/usr/lib/python3.9/site-packages/certbot/_internal/auth_handler.py", line 212, in _poll_authorizations
raise errors.AuthorizationError('Some challenges have failed.')
certbot.errors.AuthorizationError: Some challenges have failed.
That the issue is reproducible.
That it might be worth making Virtualmin auto-detect and use bound IP in generated VirtualHost blocks
The text was updated successfully, but these errors were encountered:
bohuspollak
changed the title
Let's Encrypt fails with <VirtualHost *:80> instead of IP-bound <VirtualHost [IP]:80
Let's Encrypt fails with <VirtualHost *:80> instead of IP-bound <VirtualHost [IP]:80 in virtualmin-gpl-release-7.1-1
Apr 11, 2025
Virtualmin should create virtualhosts with the correct * or IP address based on the Apache version and state of existing virtualhosts. If not, this would break not just the LE cert request, but also any access to the websites for new domains.
Does your system perhaps have different internal and public IP addresses?
Category: Virtualmin / virtualmin-config
Version:
Versions: virtualmin-gpl-release-7.1-1.noarch
wbm-virtualmin-awstats-6.1-1.noarch
wbm-virtualmin-htpasswd-3.5-1.noarch
virtualmin-config-7.0.21-1.noarch
Let’s Encrypt fails validation (returns 404) when the Apache VirtualHost is defined as *:80, and starts working properly once it's explicitly changed to <VirtualHost [public-ip]:80>. Include:
Wrong config generated:
Should be:
where n.n.n.n is public ip.
The test showing .well-known returns 404 until the change
That the issue is reproducible.
That it might be worth making Virtualmin auto-detect and use bound IP in generated VirtualHost blocks
The text was updated successfully, but these errors were encountered: