mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #3630] 3 errors in consle #2405
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#2405
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 @FengAY on GitHub (Mar 13, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3630
使用管理器申请SSL证书的时候点击SAVE没有任何反应并且控制台报错3条
When using the manager to apply for an SSL certificate, nothing happens when clicking SAVE and the console reports 3 errors.
`An invalid form control with name='' is not focusable. <input type="text" autocomplete="off" tabindex id="input-domains-selectized" required style="width: 4px;">
An invalid form control with name='forward_host' is not focusable. <input type="text" name="forward_host" class="form-control text-monospace" placeholder value autocomplete="off" maxlength="255" required>An invalid form control with name='forward_port' is not focusable. <input name="forward_port" type="number" class="form-control text-monospace" placeholder="80" value required>@lovesasha commented on GitHub (Apr 20, 2024):
我也遇到了同样的错误,等待解决。。。
@FengAY commented on GitHub (Apr 21, 2024):
我已经找到原因了.我出现的原因是我的SSL证书已经申请下来了,但是没有加到proxy host那边,只要点击proxy
host下你需要代理的列表的最右侧那三个小点,再点击Edit 找到SSL,按照流程做就好了.
Sasha @.***> 于2024年4月20日周六 15:10写道:
@github-actions[bot] commented on GitHub (Oct 27, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Oct 30, 2025):
Issue was closed due to inactivity.