NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Certificate expiration date displayed incorrectly in UI (timezone/date format issue)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker 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
-
- Create or renew a Let's Encrypt certificate via Nginx Proxy Manager
-
-
- Go to the Certificates section
-
-
-
- Observe the certificate expiration date
-
-
-
-
Expected Behavior
-
-
- The expiration date should match the actual certificate expiration date (in ISO format: YYYY-MM-DD HH:MM:SS)
-
-
-
Actual Behavior
-
-
- The certificate expiration date is displayed with incorrect date format conversion. When checking the audit log JSON data, the actual expiration is:
-
-
"expiresOn": "2026-04-12 15:43:30"(April 12, 2026 - correct ~90 days from issue date)
-
-
-
- But in the UI it displays as:
-
-
"domingo, 12/4/2026, 3:43:30 p. m."(which appears to be DD/MM/YYYY format confusion)
-
-
-
- This suggests the date is being incorrectly converted from the ISO format, mixing up day/month or timezone information.
-
-
-
Version Information
-
-
-
- Nginx Proxy Manager v2.13.5 (Latest)
-
-
-
- Browser: Chrome/Safari
-
-
-
- Host system: Docker
-
-
-
-
Impact
-
-
-
- Users may believe their certificate is about to expire soon (in 3 days) when in reality it's valid for ~4 months
-
-
-
- This causes unnecessary alarm and multiple certificate renewals
-
-
-
- Could lead to service disruptions if users take action based on incorrect expiration dates
-
-
-
-
Additional Context
-
-
- 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.
-
-
- 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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the Certificates section using a renewed Let's Encrypt certificate, then compare the audit log's expiresOn value with the rendered UI date. Trace the Certificates UI date-formatting and timezone-conversion entry point; done means the displayed expiration matches the certificate's actual date without day/month or timezone confusion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100