[GH-ISSUE #5135] Certificate expiration date displayed incorrectly in UI (timezone/date format issue) #3123

New issue

Open

opened 2026-02-26 07:37:54 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 07:37:54 +03:00

Owner

Originally created by @Ricardowec51 on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5135

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes / No
Are you sure you're not using someone else's docker image?
- Yes / No
Have you searched for similar issues (both open and c## Description
When renewing a Let's Encrypt certificate in Nginx Proxy Manager v2.13.5, the certificate expiration date is displayed incorrectly in the Certificates UI. The date format/timezone conversion appears to be buggy.
Steps to Reproduce
1. Create or renew a Let's Encrypt certificate via Nginx Proxy Manager
1. 1. Go to the Certificates section
1. 1. Observe the certificate expiration date
1. Expected Behavior
1. The expiration date should match the actual certificate expiration date (in ISO format: YYYY-MM-DD HH:MM:SS)
1. Actual Behavior
1. The certificate expiration date is displayed with incorrect date format conversion. When checking the audit log JSON data, the actual expiration is:
1. - "expiresOn": "2026-04-12 15:43:30" (April 12, 2026 - correct ~90 days from issue date)
1. But in the UI it displays as:
1. - "domingo, 12/4/2026, 3:43:30 p. m." (which appears to be DD/MM/YYYY format confusion)
1. This suggests the date is being incorrectly converted from the ISO format, mixing up day/month or timezone information.
1. Version Information
1. - Nginx Proxy Manager v2.13.5 (Latest)
1. - Browser: Chrome/Safari
1. - Host system: Docker
1. Impact
1. - Users may believe their certificate is about to expire soon (in 3 days) when in reality it's valid for ~4 months
1. - This causes unnecessary alarm and multiple certificate renewals
1. - Could lead to service disruptions if users take action based on incorrect expiration dates
1. Additional Context
1. The certificate itself is correctly issued by Let's Encrypt with proper 90-day validity. The bug is purely in the UI date display/conversion logic.
1. Please fix the date formatting to correctly handle ISO format dates and timezone conversions.losed)?
- Yes / No

Describe the bug

Nginx Proxy Manager Version

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Operating System

Additional context

Originally created by @Ricardowec51 on GitHub (Jan 12, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5135  **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes / No - Are you sure you're not using someone else's docker image? - Yes / No - Have you searched for similar issues (both open and c## Description - When renewing a Let's Encrypt certificate in Nginx Proxy Manager v2.13.5, the certificate expiration date is displayed incorrectly in the Certificates UI. The date format/timezone conversion appears to be buggy. - - ## Steps to Reproduce - 1. Create or renew a Let's Encrypt certificate via Nginx Proxy Manager - 2. 2. Go to the Certificates section - 3. 3. Observe the certificate expiration date - 4. - 5. ## Expected Behavior - 6. The expiration date should match the actual certificate expiration date (in ISO format: YYYY-MM-DD HH:MM:SS) - 7. - 8. ## Actual Behavior - 9. The certificate expiration date is displayed with incorrect date format conversion. When checking the audit log JSON data, the actual expiration is: - 10. - `"expiresOn": "2026-04-12 15:43:30"` (April 12, 2026 - correct ~90 days from issue date) - 11. - 12. But in the UI it displays as: - 13. - `"domingo, 12/4/2026, 3:43:30 p. m."` (which appears to be DD/MM/YYYY format confusion) - 14. - 15. This suggests the date is being incorrectly converted from the ISO format, mixing up day/month or timezone information. - 16. - 17. ## Version Information - 18. - Nginx Proxy Manager v2.13.5 (Latest) - 19. - Browser: Chrome/Safari - 20. - Host system: Docker - 21. - 22. ## Impact - 23. - Users may believe their certificate is about to expire soon (in 3 days) when in reality it's valid for ~4 months - 24. - This causes unnecessary alarm and multiple certificate renewals - 25. - Could lead to service disruptions if users take action based on incorrect expiration dates - 26. - 27. ## Additional Context - 28. The certificate itself is correctly issued by Let's Encrypt with proper 90-day validity. The bug is purely in the UI date display/conversion logic. - 29. - 30. Please fix the date formatting to correctly handle ISO format dates and timezone conversions.losed)? - Yes / No **Describe the bug**  **Nginx Proxy Manager Version**  **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior**  **Screenshots**  **Operating System**  **Additional context**

kerem added the

bug

label

2026-02-26 07:37:54 +03:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#3123

No description provided.

Rows
Columns