fix(acme): Refactor ACME challenge route lifecycle to prevent port 80 EADDRINUSE errors
This commit is contained in:
19
changelog.md
19
changelog.md
@ -1,5 +1,24 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-05-19 - 19.2.4 - fix(acme)
|
||||
Refactor ACME challenge route lifecycle to prevent port 80 EADDRINUSE errors
|
||||
|
||||
- Challenge route is now added only once during initialization and remains active through the entire certificate provisioning process
|
||||
- Introduced concurrency controls to prevent duplicate challenge route operations during simultaneous certificate provisioning
|
||||
- Enhanced error handling for port conflicts on port 80 with explicit error messages
|
||||
- Updated tests to cover challenge route lifecycle, concurrent provisioning, and proper cleanup on errors
|
||||
- Documentation updated with troubleshooting guidelines for port 80 conflicts and challenge route lifecycle
|
||||
|
||||
## 2025-05-19 - 19.2.4 - fix(acme)
|
||||
Fix port 80 EADDRINUSE error during concurrent ACME certificate provisioning
|
||||
|
||||
- Refactored challenge route lifecycle to add route once during initialization instead of per certificate
|
||||
- Implemented concurrency controls to prevent race conditions during certificate provisioning
|
||||
- Added proper cleanup of challenge route on certificate manager shutdown
|
||||
- Enhanced error handling with specific messages for port conflicts
|
||||
- Created comprehensive tests for challenge route lifecycle
|
||||
- Updated documentation with troubleshooting guide for port 80 conflicts
|
||||
|
||||
## 2025-05-18 - 19.2.3 - fix(certificate-management)
|
||||
Fix loss of route update callback during dynamic route updates in certificate manager
|
||||
|
||||
|
Reference in New Issue
Block a user