-
Notifications
You must be signed in to change notification settings - Fork 230
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
Registration with allowfrom set does not work? #45
Comments
All I can think of is using reverse proxy in front of acme-dns and / or corresponding configuration values of:
For debugging reasons I think adding the IP address that we're matching against would be beneficial to have in the error message. |
Thanks for the quick reply!
Is how my configuration is currently set, I also tried switching
As you mentioned, putting a reverse proxy in front of it then setting the config that way is a potential workaround however. I agree, having the IP address you're matching against in the debug message would definitely be very beneficial here. Thanks for the work you've put in to this project by the way! |
I just added logging for the IP address being matched in #46 . It's now available in |
Awesome, thank you! I just tried running the same request again, both on the server locally and from an external permitted location, and it seems the IP isn't being retrieved:
I'd assumed that when Cheers |
This seems to be a bug indeed. acme-dns is supposed to use the request.RemoteAddr if |
Unless I'm doing something really stupid here, I don't seem to be able to be able to update domains when allowfrom has been set during registration.
I use
ip addr
to retrieve all the CIDR ranges assigned to my server, then register as follows:Note: IP addresses have been partially replaced with XXX/XXXX, the real values however are used for the commands.
I then attempt to update that sub-domain:
However the update fails. acme-dns displays the following:
If I register without seting allowfrom, everything works fine:
Am I missing something here, or is it broken?
The text was updated successfully, but these errors were encountered: