mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2027] ER_DATA_TOO_LONG: Data too long for column 'forward_domain_name' at row 1 #1466
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#1466
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 @strickes on GitHub (Apr 25, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2027
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
I'm using Nginx Proxy Manager as a forwarding service for long domain names. However we got one domain that seems to long for the "forward_domain_name" table :D (the forwarded Domain is 279 Chars long)
Nginx Proxy Manager Version
2.9.18
To Reproduce
Steps to reproduce the behavior:
Expected behavior
creation of the vhost with long forwarding URLs
Screenshots
see frontend error
Operating System
Ubuntu 20.04
Additional context
n/a
@prashantsomashekar commented on GitHub (Apr 26, 2022):
I noticed it just hang and crash (browser notification: wait or kill) when attempting to input a long name.
@strickes commented on GitHub (Jun 20, 2022):
any news? Seems like it's an issue with the column (https://stackoverflow.com/questions/18897420/data-too-long-for-column-why)
@github-actions[bot] commented on GitHub (Feb 17, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 3, 2025):
Issue was closed due to inactivity.