-
Notifications
You must be signed in to change notification settings - Fork 3k
Add wedos dns #3827
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
Add wedos dns #3827
Conversation
Signed-off-by: Dusan Cervenka <cervenka.dusan@gmail.com>
I tested this by manually updating files in my docker instance. It looks working, but the wedos certbot script need little update. |
Signed-off-by: Dusan Cervenka <cervenka.dusan@gmail.com>
Docker Image for build 2 is available on DockerHub as Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes. |
Hello, with docker image i am getting error (running certbot from cmd works well, any clue for this behavior when using npm gui?):
|
archive and live folder were created with owner root:root. When i change them to npm:npm, plugin worked well So ready for merge |
Hi @Hadatko Thanks a lot for adding this feature! I just went through setting it up for the first time and I was struggling a bit so I though I'll post here some tips for others... First of all make sure that the changes implemented in this PR are present in the docker image you're using. As of now, I used the following services:
nginx-proxy-manager:
image: 'jc21/nginx-proxy-manager:github-develop' # TODO: switch to latest; using develop so that I have access to this: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/3827
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt DNS settings to set up before starting the challenge: ![]() Challenge settings: ![]() With the challenge settings I was slightly confused with the placeholder echo -n 'my_password' | sha256sum But that didn't work. Eventually, I used my wedos WAPI password (plain text) and that worked. Note: For a while you might be stuck with a something that looks like an error in the NPM web UI. Just be patient and check your logs. Eventually the certificate landed successfully. |
Hi @vsisl , as you can see my last comment is saying that everything works and then the feature was merged. Happy to see somebody else to try this :D |
Hello, i would like to add another one certbot plugin. How can i test this change?