starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #1647] Page crashes when adding host 1f5245c1-e426-5181-9d6d-e4a1b80150a6. #1235

New issue

Open

opened 2026-02-26 06:36:21 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 06:36:21 +03:00

Owner

Originally created by @ptheofan on GitHub (Dec 13, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1647

Describe the bug
Adding a host that uses a UUID v5 for subdomain crashes the page (js).

Nginx Proxy Manager Version
v2.9.12

To Reproduce
Steps to reproduce the behavior:

Go to proxy hosts (/nginx/proxy) and click to add a new proxy host
In the domain names paste the following 1f5245c1-e426-5181-9d6d-e4a1b80150a6 and type .. The page crashes (javascript gets stuck to infinite loop and eventually chrome asks to kill the page). 1f5245c1-e426-5181-9d6d-e4a1b80150a6 is a UUID v5 for whatever.example.com (can easily generate more for experimentation from https://www.uuidtools.com/v5). My idea was to put some UUIDv5 as subdomain.

Expected behavior
Continue typing and hit enter to turn it into an entry (tag)

Screenshots

Operating System
Unraid

Additional context
The problem appears to be with selectize. However, because the page crashes it makes it impossible to add the entry.

Workaround: type somewhere the complete host and copy-paste (example, copy-paste the following1f5245c1-e426-5181-9d6d-e4a1b80150a6.example.com will not crash the js)

Originally created by @ptheofan on GitHub (Dec 13, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1647 **Describe the bug** Adding a host that uses a UUID v5 for subdomain crashes the page (js). **Nginx Proxy Manager Version** v2.9.12 **To Reproduce** Steps to reproduce the behavior: 1. Go to proxy hosts (/nginx/proxy) and click to add a new proxy host 2. In the domain names paste the following `1f5245c1-e426-5181-9d6d-e4a1b80150a6` and type `.`. The page crashes (javascript gets stuck to infinite loop and eventually chrome asks to kill the page). `1f5245c1-e426-5181-9d6d-e4a1b80150a6` is a UUID v5 for whatever.example.com (can easily generate more for experimentation from https://www.uuidtools.com/v5). My idea was to put some UUIDv5 as subdomain. **Expected behavior** Continue typing and hit enter to turn it into an entry (tag) **Screenshots** ![image](https://user-images.githubusercontent.com/880939/145811082-425cd433-e686-4b1a-af5f-eb6fccc44e67.png) ![image](https://user-images.githubusercontent.com/880939/145811151-c60d58d8-4152-4cf0-a4c2-b57c6df00119.png) **Operating System** Unraid **Additional context** The problem appears to be with selectize. However, because the page crashes it makes it impossible to add the entry. Workaround: type somewhere the complete host and copy-paste (example, copy-paste the following`1f5245c1-e426-5181-9d6d-e4a1b80150a6.example.com` will not crash the js)

kerem added the

bug

label

2026-02-26 06:36:21 +03:00

kerem commented

2026-02-26 06:36:21 +03:00

Author

Owner

@FreshImmuc commented on GitHub (Dec 22, 2021):

didnt crash my dashboard, may be on your end

@FreshImmuc commented on GitHub (Dec 22, 2021): didnt crash my dashboard, may be on your end

kerem commented

2026-02-26 06:36:21 +03:00

Author

Owner

@chaptergy commented on GitHub (Dec 23, 2021):

This is due to the nested quantifiers in the regex pattern used to match the strings for selectize. More specifically this seems to be catastrophic backtracing. We would have to use a different regex pattern.

@chaptergy commented on GitHub (Dec 23, 2021): This is due to the nested quantifiers in the regex pattern used to match the strings for selectize. More specifically this seems to be [catastrophic backtracing](https://www.regular-expressions.info/catastrophic.html). We would have to use a different regex pattern.

kerem commented

2026-02-26 06:36:21 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 29, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Feb 29, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:36:21 +03:00

Author

Owner

@umutguler commented on GitHub (Feb 16, 2025):

Can confirm it happens when nesting a lot. While nesting too much may look ugly/impractical. It has its use cases & shouldn't cause the page to crash!

@umutguler commented on GitHub (Feb 16, 2025): Can confirm it happens when nesting a lot. While nesting too much may look ugly/impractical. It has its use cases & shouldn't cause the page to crash!

kerem commented

2026-02-26 06:36:21 +03:00

Author

Owner

@TheFatPanda97 commented on GitHub (Sep 18, 2025):

are there any follow up to this issue? in the current release of npm I am still getting the same issue where if the subdomain is nested more than 3 levels it freezes the entire frontend

@TheFatPanda97 commented on GitHub (Sep 18, 2025): are there any follow up to this issue? in the current release of npm I am still getting the same issue where if the subdomain is nested more than 3 levels it freezes the entire frontend

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#1235

No description provided.

Rows
Columns