mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2054] warning: insert into certificate (...) - ER_DATA_TOO_LONG: Data too long for column 'nice_name' at row 1 #1485
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#1485
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 @marrobHD on GitHub (May 15, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2054
Describe the bug
Occurs when too much Domain Names are configured in Proxy host and trying to create ssl cert.
Nginx Proxy Manager Version
v2.9.18
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should insert fine in database.
Additional context
@nicoleonwien commented on GitHub (Feb 9, 2023):
Is there any chance to get this fixed?
@Shocktrooper commented on GitHub (Oct 27, 2023):
I just got this as well. I created a valid http redirect but when I tried to create a cert it complained.
@github-actions[bot] commented on GitHub (Apr 29, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Shocktrooper commented on GitHub (Jul 30, 2024):
👍
@github-actions[bot] commented on GitHub (Apr 2, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Shocktrooper commented on GitHub (Apr 3, 2025):
👍
@github-actions[bot] commented on GitHub (Dec 29, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Shocktrooper commented on GitHub (Dec 30, 2025):
👍