mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #3719] Internal Error: josepy.errors.DeserializationError: Deserialization error: Expecting value: line 1 column 1 (char 0) #2457
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2457
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @blade1989 on GitHub (Apr 23, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3719
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
When requesting a certificate for a domain, from the
Add Let's Encrypt Certificatemodal, I get anInternal Errormessage, with the following message:In the docker compose logs, the following entry is found:
The letsencrypt logs shows the following:
Nginx Proxy Manager Version
v2.11.1
To Reproduce
Steps to reproduce the behavior:
SSL CertificatesAdd SSL CertificatesLets's EncryptExpected behavior
My newly requested Let's Encrypt certificate
Screenshots
Operating System
Ubuntu 22.04
Additional context
Docker installation
@blade1989 commented on GitHub (May 6, 2024):
@jc21 I updated to the latest NGINX Proxy Manager, v2.11.2. But, the same issue persist. My certs wil expire in less than 2 weeks, any help is greatly appreciated!
@github-actions[bot] commented on GitHub (Dec 28, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Jan 18, 2026):
Issue was closed due to inactivity.