[Bug]

What happened?

Good day. After updating to version 9.1.0 Auth for the application stopped working.
Simple Auth is now configured with Access directly after authentication: Users can directly access the application after authentication without approval.
The user enters login\password on the page and gets Engine Failure Please refresh the page
How to fix this?

How we reproduce?

1. ...
2. ...
3. ...

Expected behavior

No response

Error log

2025/08/05 14:17:13 [error] 128#0: *581 upstream prematurely closed connection while reading response header from upstream, client: 212.41.0.196, server: ssp2.goodsforecast.ru, request: "GET / HTTP/2.0", subrequest: "@safeline", upstream: "unix:/resources/detector/snserver.sock:", host: "ssp2.goodsforecast.ru", referrer: "https://ssp2.goodsforecast.ru/"
2025/08/05 14:17:13 [error] 128#0: *581 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 212.41.0.196, server: ssp2.goodsforecast.ru, request: "GET / HTTP/2.0", subrequest: "@safeline", upstream: "unix:/resources/detector/snserver.sock:", host: "ssp2.goodsforecast.ru", referrer: "https://ssp2.goodsforecast.ru/"
2025/08/05 14:17:13 [error] 128#0: *581 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 212.41.0.196, server: ssp2.goodsforecast.ru, request: "GET / HTTP/2.0", subrequest: "@safeline", upstream: "unix:/resources/detector/snserver.sock:", host: "ssp2.goodsforecast.ru", referrer: "https://ssp2.goodsforecast.ru/"
2025/08/05 14:22:43 [error] 131#0: *614 upstream prematurely closed connection while reading response header from upstream, client: 212.41.0.196, server: ssp2.goodsforecast.ru, request: "GET / HTTP/2.0", subrequest: "@safeline", upstream: "unix:/resources/detector/snserver.sock:", host: "ssp2.goodsforecast.ru", referrer: "https://ssp2.goodsforecast.ru/"
2025/08/05 14:22:43 [error] 131#0: *614 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 212.41.0.196, server: ssp2.goodsforecast.ru, request: "GET / HTTP/2.0", subrequest: "@safeline", upstream: "unix:/resources/detector/snserver.sock:", host: "ssp2.goodsforecast.ru", referrer: "https://ssp2.goodsforecast.ru/"
2025/08/05 14:22:43 [error] 131#0: *614 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 212.41.0.196, server: ssp2.goodsforecast.ru, request: "GET / HTTP/2.0", subrequest: "@safeline", upstream: "unix:/resources/detector/snserver.sock:", host: "ssp2.goodsforecast.ru", referrer: "https://ssp2.goodsforecast.ru/"

please exec docker logs safeline-detector to see detector's log

Host Windows Server 2019 Datacenter, Virtual Server Ubuntu 24.04.2 LTS, CPU Intel Xeon Silver 4214
SafeLine Version 8.5.1 is also in the log - [2025-08-06T08:50:52.206Z ERROR rskynet::init::check] - Intel SSE3 / SSSE3 is not supported, the engine may not work, but authorization in the application works without errors

[2025-08-06T08:50:52.201Z INFO rskynet::init::init] - init started, version info: [rskynet version data] commit_id: 187bf63dd7ad85392e793e4fafd4a695f6f5a98c; branch: v1.2.21.13-ce; tag: v1.2.21.13-ce; build_time: 2025-01-09T02:49:40.212896976+00:00; rustc_version: rustc 1.80.1 (3f5fd8dd4 2024-08-06); build_type: release; engine_type: legacy_skynet_amd64; hyperscan_version: 5.2.0 2022-02-15; matrix_version: 0.0.4; arch: x86_64; [end]
[2025-08-06T08:50:52.206Z DEBUG rskynet::config::config] - no config file specified (/tmp/.rskynet.yml does not exist), use default config
[2025-08-06T08:50:52.206Z INFO rskynet::init::init] - global log level: DEBUG
[2025-08-06T08:50:52.206Z ERROR rskynet::init::check] - Intel SSE3 / SSSE3 is not supported, the engine may not work
[2025-08-06T08:50:52.206Z WARN rskynet::init::check] - Intel AVX2 is not supported
[2025-08-06T08:50:52.207Z WARN rskynet::init::check] - Intel AES-NI / PCLMULQDQ is not supported
[2025-08-06T08:50:52.207Z ERROR rskynet::init::check] - hyperscan is not supported
[2025-08-06T08:50:52.207Z INFO rskynet::init::init] - panic hook is enabled
[2025-08-06T08:50:52.207Z INFO rskynet::init::init] - init done
2025-08-06T08:50:52.257181Z WARN snserver_engine::report: management server address is empty, skipping report
2025-08-06T08:50:52.311876Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:52.667855Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:53.089601Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:53.473584Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:54.261182Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:54.660901Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:54.918747Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:55.060833Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:55.460657Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:55.861780Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:56.263641Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:56.660882Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:57.060912Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:57.461195Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:57.860930Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:58.260697Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:58.660766Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:59.061208Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:59.461332Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:50:59.860658Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:51:00.260924Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025-08-06T08:51:00.660451Z WARN snserver_engine::web_log: failed to send web log: client error (Connect)
2025/08/06 08:51:21 ERROR wait command failed, wait to retry err="signal: killed"
[2025-08-06T08:51:22.079Z INFO rskynet::init::init] - init started, version info: [rskynet version data] commit_id: 187bf63dd7ad85392e793e4fafd4a695f6f5a98c; branch: v1.2.21.13-ce; tag: v1.2.21.13-ce; build_time: 2025-01-09T02:49:40.212896976+00:00; rustc_version: rustc 1.80.1 (3f5fd8dd4 2024-08-06); build_type: release; engine_type: legacy_skynet_amd64; hyperscan_version: 5.2.0 2022-02-15; matrix_version: 0.0.4; arch: x86_64; [end]
[2025-08-06T08:51:22.079Z DEBUG rskynet::config::config] - no config file specified (/tmp/.rskynet.yml does not exist), use default config
[2025-08-06T08:51:22.079Z INFO rskynet::init::init] - global log level: DEBUG
[2025-08-06T08:51:22.079Z ERROR rskynet::init::check] - Intel SSE3 / SSSE3 is not supported, the engine may not work
[2025-08-06T08:51:22.079Z WARN rskynet::init::check] - Intel AVX2 is not supported
[2025-08-06T08:51:22.080Z WARN rskynet::init::check] - Intel AES-NI / PCLMULQDQ is not supported
[2025-08-06T08:51:22.080Z ERROR rskynet::init::check] - hyperscan is not supported
[2025-08-06T08:51:22.080Z INFO rskynet::init::init] - panic hook is enabled
[2025-08-06T08:51:22.080Z INFO rskynet::init::init] - init done
2025-08-06T08:51:22.088665Z WARN snserver_engine::report: management server address is empty, skipping report

detector upgrade in 9.0.0 and SSE3/SSSE3 has become mandatory.

if you use vm, SSE3/SSSE3 can be enabled in the vm config

Thank you very much, I disabled the function "Allow migration to a virtual machine host with a different processor version"
Authorization works!