Comments (2)
x1ddos
commented on May 5, 2024
Hey @bof thanks for reporting this. On my way to the office now. Will investigate when I get there.
from acme.
bof
commented on May 5, 2024
blush testing a different client and running into exactly the same issue of staging not working but prod working... I debugged a bit more on my side and found that it was all my fault.
We run some kind of firewall side blocking which, among other things, is not too happy about requests coming in from certain cloud providers, and it turns out that the letsencrypt staging and production endpoints use totally different providers for their checking - and we blocked the staging ones.
This was a bit weird to see because even when using the staging endpoint I did/do see challenge requests (webroot mode) coming in from the same IPs as production - but obviously there are more requests than that, and the other ones blocked, so bang...
Anyway... case closed for me, and I need to switch to DNS-01 (and a different client apparently) anyway for acmev2/wildcard reasons
from acme.
Related Issues (20)
- Add support for wildcard certificates/ multiple CN names HOT 2
- ECDSA keys HOT 12
- Error when trying to reg HOT 3
- Remove acme package files and move cmd/acme to the top HOT 1
- Reverse proxy
- allow to listen on Unix socket
- allow to explicitly name host and cert files
- Provide the option to auto-generate the certificate's private key using RSA instead of ECDSA
- dns challenge feature with support for external dns tools like the dehydrated project
- Account.key path is not created when using acme reg -gen HOT 1
- Usability: reg fails when you take your time to read the license first... HOT 2
- Usability: default for -d when already registered ? HOT 2
- Reg fails if the config dir isn't created HOT 2
- example.com: acme: identifier authorization failed and 409 urn:acme:error:malformed: Registration key is already in use
- golang ListenAndServeTLS
- Add support for wildcard certificates - ACME v2
- How can acme be configured to use a different CA (other than LetsEncrypt) ??
- identifier authorization failed
- ACMEv1 sunset at Let's Encrypt breaks `acme`
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 acme.