Login timeout too short for runtime v4 on original raspberrypi

[QB4-dev]

Prerequisites

• Using NodeJS 20+
• Using Npm 10+

Expected Behavior

OpenPLC login pass and connection with runtime on raspberrypi is established

Current Behavior

Running OpenPLC runtime v4 on original raspberrypi - first generation.
Runtime is active but it is impossible to connect with device using OpenPLC editor. The response from raspberrypi on /login request is too slow and Login operation is considered as timedout in editor

Steps to Reproduce

1. I've been trying to run OpenPLC runtime v4 on first raspberrypi. Installed without issues when added raspbian here:
   https://github.com/Autonomy-Logic/openplc-runtime/blob/91cfacd10af5738b771109de644842047e16cf92/install.sh#L157

2. When OpenPLC editor is trying to login it sends two requests to runtime REST API:

The first one - to check if user exists:
192.168.100.20 - - [11/Jan/2026 18:06:54] "GET /api/get-users-info HTTP/1.1" 200 -
{"id": 20, "timestamp": "2026-01-11T18:06:59.196580+00:00", "level": "DEBUG", "message": "User found: <User 1>"}

And the second one with login request:
192.168.100.20 - - [11/Jan/2026 18:07:06] "POST /api/login HTTP/1.1" 200 -

The successful response(200) is received after 7-10seconds but editor timeout for login is 5seconds:

openplc-editor/src/main/modules/ipc/main.ts

Line 75 in 9d7ea78

private readonly RUNTIME_CONNECTION_TIMEOUT_MS = 5000 // 5 seconds (important-comment)

3. Editor prints error: Login Failed: Connection timeout

Possible Solution (Not obligatory)

The easiest solution may be to increase OpenPLC editor Login timeout to 10-15seconds

Context

I've been tracking what and why login procedure on first raspberry pi is so slow.
This function call: create_access_token(identity=user) is the reason:

https://github.com/Autonomy-Logic/openplc-runtime/blob/91cfacd10af5738b771109de644842047e16cf92/webserver/restapi.py#L250

Original raspberrypi is a weak hardware and has small entropy pool:

pi@raspberrypi:~/openplc-runtime $ cat /proc/sys/kernel/random/entropy_avail 
256

This probably makes flask_jwt_extended.create_access_token very slow
Installing haveged doesn't helps

Your Environment

• App version : 4.1.1
• Branch : main
• Operating System and version : Ubuntu 25.10(PC with OpenPLC editor) Raspbian GNU/Linux 13 (trixie) (raspberrypi)

[QB4-dev]

For your information I have compiled OpenPLC editor with 10sec timeout for login and it successfully connects with runtime on first raspberrypi

[alkoval72]

I have a similar problem.
OpenPLC Runtime v4 is installed in Docker on a WirenBoard 7 controller.
I run OpenPLC Editor on Ubuntu 24.04.

When I try to connect to the device for the first time in the IDE, the new user creation form appears. After creating the user, I get the error: "failed to create user".

I checked it from the terminal using curl:
curl -k https://192.168.1.163:8443/api/get-users-info
Response:
{"msg":"Users found"}

Then, when I try to connect from the IDE, I get "login failed".
I also checked the login endpoint from the terminal:

curl -k -X POST https://192.168.1.163:8443/api/login   -H "Content-Type: application/json"   -d '{"username":"MY_LOGIN","password":"MY_PASSWORD"}'
{"access_token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJmcmVzaCI6ZmFsc2UsImlhdCI6MTc3OTIwMzc1MiwianRpIjoiNmMzZGYyNjAtYTY5Zi00NWUzLTlkYWQtMjVkNTNiYjBlYWRhIiwidHlwZSI6ImFjY2VzcyIsInN1YiI6IjEiLCJuYmYiOjE3NzkyMDM3NTIsImNzcmYiOiI2YTEyMTQ1ZC04NWFlLTQ0Y2EtOTE2ZC0xYjRiNjlmOTQzZjciLCJleHAiOjE3NzkyMDQ2NTJ9.7QKoaNhhF0JWKFKHTy37zMfq6pa4j1sgvxZp0c31ze4"}

check time:

time curl -k -s -o /dev/null -w "http_code=%{http_code} time_total=%{time_total}s\n" \
  https://192.168.1.163:8443/api/login \
  -H "Content-Type: application/json" \
  -d '{"username":"MY_LOGIN","password":"MY_PASSWORD"}'
http_code=200 time_total=5.635446s

real	0m5,651s
user	0m0,014s
sys	0m0,008s

So it looks like the Runtime API works correctly, but OpenPLC Editor fails because the login request takes longer than the IDE timeout.