mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2688] [Express ] › ⚠ warning invalid signature #1854
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#1854
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 @schumi2004 on GitHub (Mar 16, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2688
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
In the logs i see several messages like:
[Express ] › ⚠ warning invalid signature
Nginx Proxy Manager Version
2.19.9
To Reproduce
Steps to reproduce the behavior:
Just run NPM as normal and check logs
Expected behavior
No warning messages
Screenshots
n/a
Operating System
Docker
Additional context
[3/16/2023] [1:23:37 PM] [Express ] › ⚠ warning invalid signature
[3/16/2023] [1:23:38 PM] [Express ] › ⚠ warning invalid signature
I have no idea what above messages means so no clue if it can be ignored or not.
It says warning so i guess something is wrong.
@SeanChengN commented on GitHub (Mar 18, 2023):
same problem
@jc21 commented on GitHub (Mar 18, 2023):
That error isn't part of the codebase and it's been seen before in #775 but the reporter said it fixed itself. I would think it's something related to the JWT given in the API request. Some things to try:
2.9.21docker image tagand you should see more info in the logs.
@schumi2004 commented on GitHub (Mar 21, 2023):
I moved to other solution but will test when i find some time.
@Marcbacca commented on GitHub (Mar 21, 2023):
I'm having the same issue as well in Unraid with the official image, latest 2.9.21 version. Every time in Homepage I hit refresh to access the api/logs for stats, this error pops up in the logs.
Homepage error display - API Error: Internal Error
nginx logs - [Express ] › ⚠ warning invalid signature
I should mention that I needed to previously chmod 755 the /data/logs dir in the docker because syslog was broken (was 777 and wouldn't start), not sure how those permissions were ever changed in the first place. I'm not sure if this could be related to this issue..
EDIT: With debug = 1
[3/21/2023] [11:22:31 PM] [Express ] › ⬤ debug JsonWebTokenError: invalid signature
at /app/node_modules/jsonwebtoken/verify.js:171:19
at getSecret (/app/node_modules/jsonwebtoken/verify.js:97:14)
at Object.module.exports [as verify] (/app/node_modules/jsonwebtoken/verify.js:101:10)
at /app/models/token.js:71:11
at new Promise ()
at Object.load (/app/models/token.js:65:11)
at /app/lib/access.js:228:20
at new Promise ()
at Object.load (/app/lib/access.js:226:11)
at /app/lib/express/jwt-decode.js:7:10
@swoop124 commented on GitHub (Mar 23, 2023):
Hello,
i have the same errors and did also a
DEBUG: 1and got same messagesa asMarcbacca.any News?
@SeanChengN commented on GitHub (Mar 24, 2023):
2.9.22
[3/24/2023] [9:26:49 AM] [Express ] › ⬤ debug JsonWebTokenError: invalid signature at /app/node_modules/jsonwebtoken/verify.js:171:19 at getSecret (/app/node_modules/jsonwebtoken/verify.js:97:14) at Object.module.exports [as verify] (/app/node_modules/jsonwebtoken/verify.js:101:10) at /app/models/token.js:71:11 at new Promise (<anonymous>) at Object.load (/app/models/token.js:65:11) at /app/lib/access.js:228:20 at new Promise (<anonymous>) at Object.load (/app/lib/access.js:226:11) at /app/lib/express/jwt-decode.js:7:10@henkiewie commented on GitHub (Mar 24, 2023):
I had the same error (2.9.22). Restarted the docker container that was/is using the API (in my case homepage gave an API error) and both errors were gone. Maybe it helps someone.
@Marcbacca commented on GitHub (Mar 27, 2023):
Can confirm, the patch 3-4 days ago appears to have fixed the issue. Yesterday's/today's updates haven't broken it.. seems to be fixed.
@scorpio2k2 commented on GitHub (Mar 27, 2023):
I still have the same issue:
Image used: jc21/nginx-proxy-manager latest 5b3ff21ccf9
[3/27/2023] [2:52:03 PM] [Express ] › ⬤ debug JsonWebTokenError: invalid signature
at /app/node_modules/jsonwebtoken/verify.js:171:19
at getSecret (/app/node_modules/jsonwebtoken/verify.js:97:14)
at Object.module.exports [as verify] (/app/node_modules/jsonwebtoken/verify.js:101:10)
at /app/models/token.js:65:11
at new Promise ()
at Object.load (/app/models/token.js:60:11)
at /app/lib/access.js:228:20
at new Promise ()
at Object.load (/app/lib/access.js:226:11)
at /app/lib/express/jwt-decode.js:7:10
@jc21 commented on GitHub (Mar 28, 2023):
I looked into this further, the warning is just a warning. It will happen when the JWT you use to access the API was encrypted with a different set of keys than is currently on file.
Prior to 2.10, this would be common, especially for those not using a mounted config file, as the keys would be generated after every docker container restart and wiped out.
With 2.10.0, these keys are now saved in the data folder and read from there.
I'll close this for now. If anyone experiences this with 2.10.0 or above AND think it's related to other behaviour, such as not being able to login, then please reopen.
@eriksneff commented on GitHub (Mar 30, 2023):
@jc21 thx for looking into this. Not sure what the impact is here, but I'm on npm v2.10.1 and I'm seeing this
⚠️ warning invalid signaturemessage about once a minute as I navigate through my system. Here's a screenshot that I'm not sure will help:@GVA-Guillaume commented on GitHub (Jul 12, 2023):
Last version and I have also this warning
But this is not only a warning,
because, the UI freeze it's then it's impossible to manage anything
[7/12/2023] [4:19:04 PM] [Express ] › ⬤ debug JsonWebTokenError: invalid signature
at /app/node_modules/jsonwebtoken/verify.js:171:19
at getSecret (/app/node_modules/jsonwebtoken/verify.js:97:14)
at Object.module.exports [as verify] (/app/node_modules/jsonwebtoken/verify.js:101:10)
at /app/models/token.js:65:11
at new Promise ()
at Object.load (/app/models/token.js:60:11)
at /app/lib/access.js:228:20
at new Promise ()
at Object.load (/app/lib/access.js:226:11)
at /app/lib/express/jwt-decode.js:7:10
@GVA-Guillaume commented on GitHub (Jul 12, 2023):
After some investigations two points :
strangely the problem comes from the database name, it seems that we are not able to harden the database" "npm" of the most EXPOSED service in the network, a very clear security issue, most of the Dockerfile and/or Entrepont scripts needs to be fixed