Problem with Access List and API App

[Jamyz]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? No
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug In Access Lists

• Satisfy Any & Pass Auth to Host are ON.
• Authorization created with an Username and Password
• Access with allow an IP fix and deny for all

Nginx Proxy Manager Version 2.9.18

Expected behavior When i connect I have the box Authoriztion to enter the user and password. Works fine. But When i try to login (nginxproxymanager or portainer for example) it´s impossible if the ip different from Access

When i try to login in portainer i have this error : **level=info msg="2022/04/11 02:03:01 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]" INFO 2022/04/11 02:03:01 [INFO] [cmd,main] Starting Portainer version 2.11.1

level=info msg="2022/04/11 02:03:01 [DEBUG] [internal,init] [message: start initialization monitor ]" level=info msg="2022/04/11 02:03:01 [INFO] [http,server] [message: starting HTTPS server on port :9443]" level=info msg="2022/04/11 02:03:01 [INFO] [http,server] [message: starting HTTP server on port :9000]" level=info msg="2022/04/11 03:51:53 http error: A valid authorisation token is missing (err=Unauthorized) (code=401)" level=info msg="2022/04/11 05:34:46 http error: A valid authorisation token is missing (err=Unauthorized) (code=401)"**

With nginxproxymanager : [4/12/2022] [6:18:16 AM] [Express ] › ⚠ warning Existing token contained invalid user data [4/12/2022] [6:18:23 AM] [Express ] › ⚠ warning Existing token contained invalid user data [4/12/2022] [6:18:29 AM] [Express ] › ⚠ warning Existing token contained invalid user data

Maybe is because, portainer, homebridge, nginxproxymanager and other use api. So how use api with portainer for example ?

Operating System Docker on Raspberry Pi 3

[GVA-Guillaume]

Hi , i have the same problem Existing token contained invalid user data

[rahul1996pp]

you can fix this issue by adding this in .conf that you can found in this path "/data/nginx/proxy_host"

proxy_set_header Authorization $http_authorization;

[github-actions[bot]]

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