[GH-ISSUE #963] Proxy host the NPM itself and the login page only reloads when enter email and password #811

New issue

Closed

opened 2026-02-26 06:34:31 +03:00 by kerem · 16 comments

kerem commented 2026-02-26 06:34:31 +03:00

Owner

Copy link

Originally created by @ReasonMan77 on GitHub (Mar 20, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/963

**Describe the bug

• A clear and concise description of what the bug is.**

I am running NPM in Portainer on a RPi. I have made a proxy host of the proxy itself. When I enter the DNS name of the proxy or clicking on the proxy host link the login page appears but when I enter the email address and password the login page just reloads like nothing happened. No problems to login to NPM when enter the ip address instead of the DNS name. I have tried both http and https and still same result.
In the Portainer logs of nginx_app_1 I can see that there is problem - don't know how to solve it though. This warning appears every time I try to login when using the DNS name.

[3/20/2021] [6:57:56 PM] [Express ] › ⚠ warning Existing token contained invalid user data,
[3/20/2021] [6:53:09 PM] [Express ] › ⚠ warning Existing token contained invalid user data,
[3/20/2021] [6:52:53 PM] [Express ] › ⚠ warning Existing token contained invalid user data,
[3/20/2021] [6:19:20 PM] [Express ] › ⚠ warning Existing token contained invalid user data,
[3/20/2021] [6:18:44 PM] [Express ] › ⚠ warning Existing token contained invalid user data

I have other proxy hosts that is working w/o any issues. It is just the proxy itself that has this problem.

No difference when testing several web browsers.

- What version of Nginx Proxy Manager is reported on the login page?
2.81
2.80

Operating System
Using RPi Raspberry OS

Additional context
I have tested using Firefox, Safari, Brave on several Macbook Pro's.
Changed the admin password.
Portainer version 2.1.1.

Originally created by @ReasonMan77 on GitHub (Mar 20, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/963 ****Describe the bug** - A clear and concise description of what the bug is.** I am running NPM in Portainer on a RPi. I have made a proxy host of the proxy itself. When I enter the DNS name of the proxy or clicking on the proxy host link the login page appears but when I enter the email address and password the login page just reloads like nothing happened. No problems to login to NPM when enter the ip address instead of the DNS name. I have tried both http and https and still same result. In the Portainer logs of nginx_app_1 I can see that there is problem - don't know how to solve it though. This warning appears every time I try to login when using the DNS name. [3/20/2021] [6:57:56 PM] [Express ] › ⚠ warning Existing token contained invalid user data, [3/20/2021] [6:53:09 PM] [Express ] › ⚠ warning Existing token contained invalid user data, [3/20/2021] [6:52:53 PM] [Express ] › ⚠ warning Existing token contained invalid user data, [3/20/2021] [6:19:20 PM] [Express ] › ⚠ warning Existing token contained invalid user data, [3/20/2021] [6:18:44 PM] [Express ] › ⚠ warning Existing token contained invalid user data I have other proxy hosts that is working w/o any issues. It is just the proxy itself that has this problem. No difference when testing several web browsers. **- What version of Nginx Proxy Manager is reported on the login page?** 2.81 2.80 **Operating System** Using RPi Raspberry OS **Additional context** I have tested using Firefox, Safari, Brave on several Macbook Pro's. Changed the admin password. Portainer version 2.1.1.

kerem 2026-02-26 06:34:31 +03:00

• closed this issue
• added the
  stale
  bug
  labels

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@l4rm4nd commented on GitHub (Mar 26, 2021):

Guess this is a looping error, where JWT authentication breaks. I don't think you can proxy the proxy manager by itself.

<!-- gh-comment-id:808426084 --> @l4rm4nd commented on GitHub (Mar 26, 2021): Guess this is a looping error, where JWT authentication breaks. I don't think you can proxy the proxy manager by itself.

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@maxdd commented on GitHub (Mar 30, 2021):

happens the same to me as well

<!-- gh-comment-id:810071980 --> @maxdd commented on GitHub (Mar 30, 2021): happens the same to me as well

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@ReasonMan77 commented on GitHub (Apr 4, 2021):

18:22 in this video this guy make it work to proxy the proxy itself. Have tried this but it is not working for me.
https://youtu.be/UfCkwlPIozw?t=1102

<!-- gh-comment-id:813004680 --> @ReasonMan77 commented on GitHub (Apr 4, 2021): 18:22 in this video this guy make it work to proxy the proxy itself. Have tried this but it is not working for me. https://youtu.be/UfCkwlPIozw?t=1102

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@l4rm4nd commented on GitHub (Apr 17, 2021):

Just tried it by myself. I am running the newest NPM docker image on my RPi 4.

Just added a new proxy host as usual. Instantly worked, cannot reproduce an issue. Can successfully login by having valid SSL certificates.

Btw, my NPM container uses a macvlan network interface and not the default docker bridge or host network. Idk, maybe this info is relevant.

<!-- gh-comment-id:821862982 --> @l4rm4nd commented on GitHub (Apr 17, 2021): Just tried it by myself. I am running the newest NPM docker image on my RPi 4. Just added a new proxy host as usual. Instantly worked, cannot reproduce an issue. Can successfully login by having valid SSL certificates. Btw, my NPM container uses a macvlan network interface and not the default docker bridge or host network. Idk, maybe this info is relevant.

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@corvock commented on GitHub (Dec 8, 2021):

So I have been fighting with something similar. As background I had always done this on machines that were fully internal and never had a need to put an access list on the proxy. I was banging my head because the recent instance was a mixed use proxy, and while i am using a .pvt domain to hit the proxy, i figured I'd be safe putting an access list on that only allowed internal subnets. When i had that set up i would get the login screen and it would just reload. My logs showed my machine making requests for /api/tokens and just /api/, but would only end up reloading the login page. When i took off the access list I was able to log in. Since port 80 isn't exposed to the internet I am not overly concerned, but it was a bother as to why it didn't work.

<!-- gh-comment-id:989314585 --> @corvock commented on GitHub (Dec 8, 2021): So I have been fighting with something similar. As background I had always done this on machines that were fully internal and never had a need to put an access list on the proxy. I was banging my head because the recent instance was a mixed use proxy, and while i am using a .pvt domain to hit the proxy, i figured I'd be safe putting an access list on that only allowed internal subnets. When i had that set up i would get the login screen and it would just reload. My logs showed my machine making requests for /api/tokens and just /api/, but would only end up reloading the login page. When i took off the access list I was able to log in. Since port 80 isn't exposed to the internet I am not overly concerned, but it was a bother as to why it didn't work.

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@eitch commented on GitHub (Jan 11, 2022):

I've had the same issue. And it seems to be an issue if access lists with a password is active. If i just allow local IP and deny the rest, then external access is denied, i can access the panel from LAN and the login itself works as well.

<!-- gh-comment-id:1010451726 --> @eitch commented on GitHub (Jan 11, 2022): I've had the same issue. And it seems to be an issue if access lists with a password is active. If i just allow local IP and deny the rest, then external access is denied, i can access the panel from LAN and the login itself works as well.

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@flavietto commented on GitHub (Apr 7, 2022):

I have the same issue. If use an access list with a password system get into loop. Someone have found a solution?

<!-- gh-comment-id:1091956617 --> @flavietto commented on GitHub (Apr 7, 2022): I have the same issue. If use an access list with a password system get into loop. Someone have found a solution?

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@Jamyz commented on GitHub (Apr 12, 2022):

I have the same problems

<!-- gh-comment-id:1096145684 --> @Jamyz commented on GitHub (Apr 12, 2022): I have the same problems

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@l4rm4nd commented on GitHub (Apr 13, 2022):

Cannot reproduce any looping bugs. Just specify the docker container name of your NPM instance and it should work.

<!-- gh-comment-id:1098079493 --> @l4rm4nd commented on GitHub (Apr 13, 2022): Cannot reproduce any looping bugs. Just specify the docker container name of your NPM instance and it should work. 

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@rkbest13 commented on GitHub (Jun 23, 2022):

same problem. I am using latest image as well. my npm runs on docker behind pfsense with Pure NAT.

<!-- gh-comment-id:1164478592 --> @rkbest13 commented on GitHub (Jun 23, 2022): same problem. I am using latest image as well. my npm runs on docker behind pfsense with Pure NAT.

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@Jamyz commented on GitHub (Oct 4, 2022):

Cannot reproduce any looping bugs. Just specify the docker container name of your NPM instance and it should work.

Doesnt work for me

<!-- gh-comment-id:1266744571 --> @Jamyz commented on GitHub (Oct 4, 2022): > Cannot reproduce any looping bugs. Just specify the docker container name of your NPM instance and it should work. > >  Doesnt work for me

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@bartekj commented on GitHub (Oct 21, 2022):

I was also facing exactly the same issue. My NPM is running as a VM behind mikrotik router with a default NAT (masquerade). Ports forwarded with simple dst-nat to the npm internal ip.

For me adding a custom location / to the proxy host with this config solved the problem.

proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;

Funny thing, when I wanted to test this again by removing the custom location I've stopped getting warnings.

[10/21/2022] [12:12:11 AM] [Express  ] › ⚠  warning   Existing token contained invalid user data

Still willing to keep the custom location in my config.

<!-- gh-comment-id:1286789040 --> @bartekj commented on GitHub (Oct 21, 2022): I was also facing exactly the same issue. My NPM is running as a VM behind mikrotik router with a default NAT (masquerade). Ports forwarded with simple dst-nat to the npm internal ip. For me adding a custom location `/` to the proxy host with this config solved the problem. ``` proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; ```  Funny thing, when I wanted to test this again by removing the custom location I've stopped getting warnings. ``` [10/21/2022] [12:12:11 AM] [Express ] › ⚠ warning Existing token contained invalid user data ``` Still willing to keep the custom location in my config.

kerem commented 2026-02-26 06:34:31 +03:00

Author

Owner

Copy link

@derekoharrow commented on GitHub (Oct 24, 2022):

I've solved this by turning off any access lists - i.e. making it publicly accessible. Of course, this means you need to rely on the NPM login & security itself.

<!-- gh-comment-id:1289136521 --> @derekoharrow commented on GitHub (Oct 24, 2022): I've solved this by turning off any access lists - i.e. making it publicly accessible. Of course, this means you need to rely on the NPM login & security itself.

kerem commented 2026-02-26 06:34:32 +03:00

Author

Owner

Copy link

@dexogen commented on GitHub (May 12, 2023):

I've run into this problem several times and each time I had to completely reinstall NPM with all hosts reconfigured.
Surprisingly, this caused only partial problems, such as the inability to log in to Portainer or NPM (which tried to proxy itself), but the rest of the functionality of the sites was available.

As @derekoharrow pointed out above - disabling access lists solved the problem in an amazing way.

I began to dig deeper and discovered an absolutely stupid reason, after which everything worked for me again with access lists. These are the fields:

My browser was using autocomplete when I clicked the tabs and turned on authorization. And for some reason, even clearing the fields and resaving the list did not always disable authorization. I also needed to manually delete an entry from the mysql database (access_list_auth table) and replace 1 with 0 in the access_list table for that list.

<!-- gh-comment-id:1545782984 --> @dexogen commented on GitHub (May 12, 2023): I've run into this problem several times and each time I had to completely reinstall NPM with all hosts reconfigured. Surprisingly, this caused only partial problems, such as the inability to log in to Portainer or NPM (which tried to proxy itself), but the rest of the functionality of the sites was available. As @derekoharrow pointed out above - disabling access lists solved the problem in an amazing way. I began to dig deeper and discovered an absolutely stupid reason, after which everything worked for me again with access lists. These are the fields:  My browser was using autocomplete when I clicked the tabs and turned on authorization. And for some reason, even clearing the fields and resaving the list did not always disable authorization. I also needed to manually delete an entry from the mysql database (access_list_auth table) and replace 1 with 0 in the access_list table for that list.

kerem commented 2026-02-26 06:34:32 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Mar 16, 2024):

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

<!-- gh-comment-id:2001056968 --> @github-actions[bot] commented on GitHub (Mar 16, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented 2026-02-26 06:34:32 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 27, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2832901751 --> @github-actions[bot] commented on GitHub (Apr 27, 2025): Issue was closed due to inactivity.

kerem referenced this issue 2026-02-26 06:35:40 +03:00

[GH-ISSUE #1358] X-forwared-for shows Cloudflare IP instead of real IP #1077

kerem referenced this issue 2026-02-26 06:35:40 +03:00

[GH-ISSUE #1358] X-forwared-for shows Cloudflare IP instead of real IP #1077

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

develop

dependabot/npm_and_yarn/backend/liquidjs-10.25.7

dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987

dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41

dependabot/npm_and_yarn/backend/basic-ftp-5.3.0

dependabot/npm_and_yarn/test/follow-redirects-1.16.0

dependabot/npm_and_yarn/test/axios-1.15.0

dependabot/npm_and_yarn/frontend/lodash-4.18.1

dependabot/npm_and_yarn/backend/lodash-4.18.1

dependabot/npm_and_yarn/test/lodash-4.18.1

dependabot/npm_and_yarn/frontend/vite-7.3.2

dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21

dependabot/npm_and_yarn/frontend/lodash-es-4.18.1

dependabot/npm_and_yarn/frontend/happy-dom-20.8.9

dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0

dependabot/npm_and_yarn/frontend/picomatch-4.0.4

dependabot/npm_and_yarn/backend/picomatch-2.3.2

dependabot/npm_and_yarn/frontend/yaml-1.10.3

dependabot/npm_and_yarn/test/flatted-3.4.2

dependabot/npm_and_yarn/test/tar-7.5.11

dependabot/npm_and_yarn/frontend/immutable-5.1.5

master

dependabot/npm_and_yarn/test/glob-10.5.0

dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1

dependabot/npm_and_yarn/test/form-data-4.0.4

v3-abandoned

bump-freedns

openidc

ssl-passthrough-hosts

static-content

v2.14.0

v2.13.7

v2.13.6

v2.13.5

v2.13.4

v2.13.3

v2.13.2

v2.13.1

v2.13.0

v2.12.6

v2.12.5

v2.12.4

v2.12.3

v2.12.2

v2.12.1

v2.12.0

v2.11.3

v2.11.2

v2.11.1

v2.11.0

v2.10.4

v2.10.3

v2.10.2

v2.10.1

v2.10.0

v2.9.22

v2.9.21

v2.9.20

v2.9.19

v2.9.18

v2.9.17

v2.9.16

v2.9.15

v2.9.14

v2.9.13

v2.9.12

v2.9.11

v2.9.10

v2.9.9

v2.9.8

v2.9.7

v2.9.6

v2.9.5

v2.9.4

v2.9.3

v2.9.2

v2.9.1

v2.9.0

v2.8.1

v2.8.0

v2.7.3

v2.7.2

v2.7.1

v2.7.0

v2.6.2

v2.6.1

v2.6.0

v2.5.0

v2.4.0

v2.3.1

v2.3.0

v2.2.4

v2.2.3

v2.2.2

v2.2.1

v2.2.0

v2.1.2

v2.1.1

v2.1.0

2.0.14

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.0

v2.0.0

1.1.2

1.1.1

1.0.1

Labels

Clear 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

Mirrored from GitHub Pull Request

  

question

  

stale

  

troll

  

upstream issue

  

v2

  

v2

  

v2

  

v3

  

wontfix

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

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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

No description provided.