Comments (21)
Got it to work! Using 2.11.1
(may work on latest, but I rolled back to 2.11.1
and it works).
Follow these steps:
docker exec -it <name of container> /bin/bash
- Run
certbot
and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method) pip uninstall certbot-dns-cloudflare
- Run
certbot
and see it does not error out pip install certbot-dns-cloudflare
- Run
certbot
and see it does not error out - Try creating a SSL cert and it should work
from nginx-proxy-manager.
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
docker exec -it <name of container> /bin/bash
- Run
certbot
and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method)pip uninstall certbot-dns-cloudflare
- Run
certbot
and see it does not error outpip install certbot-dns-cloudflare
- Run
certbot
and see it does not error out- Try creating a SSL cert and it should work
For future people, if for some reason this doesn't work try doing
pip uninstall certbot-dns-cloudflare
pip install --upgrade pip
and the reinstall the plugin but specify the version
pip install --force-reinstall "certbot-dns-cloudflare==2.11.0"
and restart the container.
For some reason even if you reinstall the plugin after upgrading pip it will always pull the version that it was installed.
from nginx-proxy-manager.
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
docker exec -it <name of container> /bin/bash
- Run
certbot
and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method)pip uninstall certbot-dns-cloudflare
- Run
certbot
and see it does not error outpip install certbot-dns-cloudflare
- Run
certbot
and see it does not error out- Try creating a SSL cert and it should work
It works!
from nginx-proxy-manager.
The issue is the cloudflare-python
package, version 3.x.x is incompatible with 2.x.x, which is pinned in certbot upstream, but not here in NPM it seems. Perhaps certbot needs to be bumped in NPM. This has been adressed in #3764, hopefully dev gets merged soon...
A more technically correct fix is only pinning the cloudflare package in the container using pip install --upgrade cloudflare==2.19.*
i.e.
docker exec -it <name of container> /bin/bash
pip install --upgrade cloudflare==2.19.*
- Try creating a SSL cert and it should work
from nginx-proxy-manager.
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
docker exec -it <name of container> /bin/bash
- Run
certbot
and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method)pip uninstall certbot-dns-cloudflare
- Run
certbot
and see it does not error outpip install certbot-dns-cloudflare
- Run
certbot
and see it does not error out- Try creating a SSL cert and it should work
Confirmed, this works on v2.11.2.
from nginx-proxy-manager.
Got a slightly different error:
The 'certbot_dns_cloudflare._internal.dns_cloudflare' plugin errored while loading: No module named 'CloudFlare'. You may need to remove or update this plugin. The Certbot log will contain the full error details and this should be reported to the plugin developer.
with no mention of acme==
.
from nginx-proxy-manager.
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
1. `docker exec -it <name of container> /bin/bash` 2. Run `certbot` and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method) 3. `pip uninstall certbot-dns-cloudflare` 4. Run `certbot` and see it does not error out 5. `pip install certbot-dns-cloudflare` 6. Run `certbot` and see it does not error out 7. Try creating a SSL cert and it should work
You saved me!
It worked!
Thanks!
from nginx-proxy-manager.
The issue is the
cloudflare-python
package, version 3.x.x is incompatible with 2.x.x,which is pinned in certbot upstream, but not here in NPM it seems. Perhaps certbot needs to be bumped in NPM.This has been adressed in #3764, hopefully dev gets merged soon...A more technically correct fix is only pinning the cloudflare package in the container using
pip install --upgrade cloudflare==2.19.*
i.e.
docker exec -it <name of container> /bin/bash
pip install --upgrade cloudflare==2.19.*
- Try creating a SSL cert and it should work
Finally succeeded!!
from nginx-proxy-manager.
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
1. `docker exec -it <name of container> /bin/bash` 2. Run `certbot` and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method) 3. `pip uninstall certbot-dns-cloudflare` 4. Run `certbot` and see it does not error out 5. `pip install certbot-dns-cloudflare` 6. Run `certbot` and see it does not error out 7. Try creating a SSL cert and it should work
Thank you so much, this was driving me nuts!
from nginx-proxy-manager.
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
docker exec -it <name of container> /bin/bash
- Run
certbot
and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method)pip uninstall certbot-dns-cloudflare
- Run
certbot
and see it does not error outpip install certbot-dns-cloudflare
- Run
certbot
and see it does not error out- Try creating a SSL cert and it should work
Thank you for this fix, helped with my first installation
from nginx-proxy-manager.
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
1. `docker exec -it <name of container> /bin/bash` 2. Run `certbot` and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method) 3. `pip uninstall certbot-dns-cloudflare` 4. Run `certbot` and see it does not error out 5. `pip install certbot-dns-cloudflare` 6. Run `certbot` and see it does not error out 7. Try creating a SSL cert and it should work
Works like a charm! Thank you for this. I hope an update comes out soon to resolve it.
from nginx-proxy-manager.
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
docker exec -it <name of container> /bin/bash
- Run
certbot
and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method)pip uninstall certbot-dns-cloudflare
- Run
certbot
and see it does not error outpip install certbot-dns-cloudflare
- Run
certbot
and see it does not error out- Try creating a SSL cert and it should work
Got it to work! Using
2.11.1
(may work on latest, but I rolled back to2.11.1
and it works).Follow these steps:
docker exec -it <name of container> /bin/bash
- Run
certbot
and see it errors out saying that cloudflare-dns plugin is causing an issue (this is to confirm you have the issue I was seeing that was fixed by this method)pip uninstall certbot-dns-cloudflare
- Run
certbot
and see it does not error outpip install certbot-dns-cloudflare
- Run
certbot
and see it does not error out- Try creating a SSL cert and it should work
thank u so much! this really helps
from nginx-proxy-manager.
5. pip install certbot-dns-cloudflare
Tried on 2.11.2 and works like a charm! thank you so much!
from nginx-proxy-manager.
Same here. Seems rolling back to 2.11.1
doesn't seem to fix it either.
from nginx-proxy-manager.
neither does deleting the local image and restarting it. I have made certs using cloudflare on this yesterday
from nginx-proxy-manager.
I wonder if wiping the local storage may fix it? I didn't try that yet.
from nginx-proxy-manager.
That didn't work either on 2.11.1
.
from nginx-proxy-manager.
Same here. I'm trying with 2.11.x, 2.10.x and 2.9.x and it doesn't work either.
from nginx-proxy-manager.
ill give that a try!
from nginx-proxy-manager.
okay, now im going insane, i think. i did not have to do any of that, just went back to my old database.sqlite file and it worked just like that. i hate days like these. becuase you dont know what happened and what fixed it
from nginx-proxy-manager.
The issue is the
cloudflare-python
package, version 3.x.x is incompatible with 2.x.x,which is pinned in certbot upstream, but not here in NPM it seems. Perhaps certbot needs to be bumped in NPM.This has been adressed in #3764, hopefully dev gets merged soon...A more technically correct fix is only pinning the cloudflare package in the container using
pip install --upgrade cloudflare==2.19.*
i.e.
1. `docker exec -it <name of container> /bin/bash` 2. `pip install --upgrade cloudflare==2.19.*` 3. Try creating a SSL cert and it should work
This does NOT work on NPM on v 2.11.1 and running the pip install.
from nginx-proxy-manager.
Related Issues (20)
- Docker not create rules for ports in iptables HOT 1
- IP Address Whitelist/Blacklist only valid while set to docker network HOT 2
- Two "Add SSL Certificate" buttons, with different meanings
- Allow editing ssl certificate renewal info after the fact
- How to deal with bind issues with default/standard ports - New Ports? HOT 2
- let's encrypt certbot requests should not use --preferred-challenges dns,http if "use a DNS challenge" is not requested HOT 1
- Update certbot-dns-aliyun to 2.0
- pip install certbot-dns-aliyun timeout HOT 1
- How to redirect FROM a subfolder to a backend service HOT 5
- Unable to Connect HOT 1
- NPM docker - Network unreachable when connecting to acme-v02.api.letsencrypt.org
- selected force ssl not active after creation phase (web or api) - need to activate it manually afterwards HOT 1
- rce vulnerability in npm HOT 1
- Clone Button for Proxy Host
- Nginx Proxy Manager "502 Bad Gateway- openresty" HOT 1
- A bug with your project, about high to critical. Contact me by email: [email protected] or Linkin: https://www.linkedin.com/in/bart-tran-949937171/
- WTF :login 502 HOT 7
- DNS Challenge fails with stalled credentials
- [emerg] cannot load certificate
- Unreachable upstream prevents server from starting
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nginx-proxy-manager.