[GH-ISSUE #1271] crypto - code: 40401- request timeout #7822

New issue

Closed

opened 2026-03-12 22:55:48 +03:00 by kerem · 2 comments

kerem commented

2026-03-12 22:55:48 +03:00

Owner

Originally created by @firengate on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1271

Hello!

After upgrading to the new version and waiting for nginx-ui to automatically deauthorize the session after it times out, attempting to log in again results in a "Request timeout" error.

curl 'http://192.168.110.124:9000/api/crypto/public_key'
-H 'Accept: /'
-H 'Accept-Language: en-US;q=0.8,en;q=0.7'
-H 'Connection: keep-alive'
-H 'Content-Type: application/json'
-H 'Cookie: token='
-H 'DNT: 1'
-H 'Origin: http://192.168.110.124:9000'
-H 'Referer: http://192.168.110.124:9000/'
-H 'Sec-GPC: 1'
-H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36'
--data-raw '{"timestamp":1753705061,"fingerprint":"3fce14bbcb918b815f9b7d8c4172c536"}'
--insecure

Nginx UI Response
{"scope":"crypto","code":40401,"message":"request timeout"}

I tried installing an older version (2.1.4), and the authorization works fine there.

Server OS: Debian 12
Server Arch: x86
Nginx UI Version: v2.1.14
Your Browser: Chrome 130

Originally created by @firengate on GitHub (Jul 28, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1271 Hello! After upgrading to the new version and waiting for nginx-ui to automatically deauthorize the session after it times out, attempting to log in again results in a "Request timeout" error. curl 'http://192.168.110.124:9000/api/crypto/public_key' \ -H 'Accept: */*' \ -H 'Accept-Language: en-US;q=0.8,en;q=0.7' \ -H 'Connection: keep-alive' \ -H 'Content-Type: application/json' \ -H 'Cookie: token=' \ -H 'DNT: 1' \ -H 'Origin: http://192.168.110.124:9000' \ -H 'Referer: http://192.168.110.124:9000/' \ -H 'Sec-GPC: 1' \ -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36' \ --data-raw '{"timestamp":1753705061,"fingerprint":"3fce14bbcb918b815f9b7d8c4172c536"}' \ --insecure Nginx UI Response {"scope":"crypto","code":40401,"message":"request timeout"} <img width="1113" height="919" alt="Image" src="https://github.com/user-attachments/assets/ccc8de7e-be07-4575-aa72-7139e1bf8461" /> I tried installing an older version (2.1.4), and the authorization works fine there. - Server OS: Debian 12 - Server Arch: x86 - Nginx UI Version: v2.1.14 - Your Browser: Chrome 130

kerem

2026-03-12 22:55:48 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-12 22:56:05 +03:00

Author

Owner

@0xJacky commented on GitHub (Jul 28, 2025):

Please calibrate the time of the server and the browser.

@0xJacky commented on GitHub (Jul 28, 2025): Please calibrate the time of the server and the browser.

kerem commented

2026-03-12 22:56:10 +03:00

Author

Owner

@kaijia323 commented on GitHub (Jul 28, 2025):

Please calibrate the time of the server and the browser.请校准服务器和浏览器的时间。

{“timestamp”：1753705061，“fingerprint”：“3fce14bbcb918b815f9b7d8c4172c536”}

这个时间戳是错误的，应该获取的是毫秒，我通过替换js的内容，换成毫秒就可以成功

This timestamp is incorrect. It should be in milliseconds. I can make it work by replacing the content of the JavaScript to get the milliseconds.

@kaijia323 commented on GitHub (Jul 28, 2025): > Please calibrate the time of the server and the browser.请校准服务器和浏览器的时间。 {“timestamp”：1753705061，“fingerprint”：“3fce14bbcb918b815f9b7d8c4172c536”} 这个时间戳是错误的，应该获取的是毫秒，我通过替换js的内容，换成毫秒就可以成功 This timestamp is incorrect. It should be in milliseconds. I can make it work by replacing the content of the JavaScript to get the milliseconds.