mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #214] Error popup when routing nginx container itself- Expectation Failed #188
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#188
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 @CXZ7720 on GitHub (Oct 21, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/214
Checklist
[v] Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?[v] Are you sure you're not using someone else's docker image?
[v] If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
Describe the bug
When I try to delete user, the alert message popups and it says Expectation Failed
To Reproduce
Steps to reproduce the behavior:
0. Proxy Nginx Container itself to subdomain :
nginx.example.comand access through the domain.Similar error popup shows in deleting proxy rules, 404 rules, etc.
Expected behavior
Delete users
Screenshots

Operating System
Ubuntu 18.04 LTS,
AMD 2700X, DDR4 32GB
Nginx Proxy Manager v2.0.14
Additional context
Docker version 19.03.3, build a872fc2f86
User Agent Strings :
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.89 Safari/537.36
@chaptergy commented on GitHub (May 11, 2021):
As this issue is very old and I can't reproduce it, I will close this.