-
Notifications
You must be signed in to change notification settings - Fork 183
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
[HELP] Not possible to create an SSL certificate #386
Comments
i have the same issue [mydomain.com] acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: 12.34.56.78: Invalid response from http://mydomain.com/.well-known/acme-challenge/ulhLOyyun5LCNDLDLtLA3nm0bnW7-LuVvFdqTdNaq1o: 404 Portforwarding for 80 and 443 is active |
@yeungalan Can you help check if the latest version of Zoraxy ACME module got any issue regarding http-01 challenge? Though, from what I observed, these issues mostly come from inbound network settings. In your case, I would recommend keep using NPM if it works in your specific network environment (and maybe use Zoraxy as a 2nd layer proxy). NPM is more compatible with de-facto or "wired" network setups as it is a much more mature and old project. |
checking |
looks like DNS01 and HTTP01 both broke, maybe due to @tobychui 's recent code change |
|
|
Hey @tobychui can you rollback your change |
Steps to recreate the issue
|
Fuck you, no.
Cannot reproduce such issue on Windows build v3.1.3. Using a completely fresh install (start with just a single exe file) and immediate visit Will be testing http-01 on ramnode now. |
Hi,
I’ve installed the latest version of Zoraxy as a Docker container, and the necessary ports are open.
Now, I wanted to secure my DNS address with an SSL certificate, but I keep getting the following error.
Error: one or more domains had a problem: [DOMAIN.ddns.net] acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: 99.999.99.99: Invalid response from http://DOMAIN.ddns.net/.well-known/acme-challenge/7k9pJWEaLAxLMDVBsUffVCDv1ykyckWNpfoBulj4fq8: 404
As a test, I set up the DNS address with SSL using Nginx, and that worked without any issues.
Does anyone have an idea what might be causing this?
Best regards,
The text was updated successfully, but these errors were encountered: