[Bug]: Infinite check API status

[pavel-collab]

Describe the bug

When I'm trying to start the service on my raspberry pi 4 from docker (with using docker compose) I got an infinite check API status on http://localhost

To Reproduce

1. Using raspberry pi 4 with os

Linux raspberrypi 6.12.62+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.62-1+rpt1 (2025-12-18) aarch64 GNU/Linux

2. Use the instruction to build the system in docker:

docker compose --build

3. Start the service in docker

docker compose up -d

4. Go to the http://localhost

Expected behavior

All of the docker containers will start correctly, but on the http://localhost you will see the infinite check API status

Screenshots

Operating System

Linux

Browser

Chrome

Browser Version

No response

Device (if mobile)

No response

Additional context

No response

[lukashow]

Hi, can you provide your docker build and run logs for all containers, plus your browser console output? It would be helpful for me to find out the issue. Thank you.

[r-chulkevich]

Hello! I have the same issue with Docker Engine on Ubuntu.

1. All containers are running, db-init completed successfully, all logs look correct.
2. http://localhost/api/ — works.
3. http://localhost/50x.html — returns the page.
4. http://localhost/ — shows an infinite loader "Checking Api status".

Important note: all static assets are fully loaded. A client request to
http://localhost/api/encryptionPublicKey returns 304 with a successful payload, after which nothing else happens.

db logs:

Superuser configured successfully
2026/03/04 21:12:06 Server started at http://0.0.0.0:8090
├─ REST API:  http://0.0.0.0:8090/api/
└─ Dashboard: http://0.0.0.0:8090/_/

server logs:

INFO [2026-03-04 21:32:30]: (Server Core): GET /locales/listLanguages 304 0.398 ms
INFO [2026-03-04 21:32:30]: (Server Core): GET /encryptionPublicKey 304 0.491 ms

client logs:

172.18.0.1 - - [04/Mar/2026:21:31:42 +0000] "GET /index.html HTTP/1.0" 304 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "..."
172.18.0.1 - - [04/Mar/2026:21:31:43 +0000] "GET /api/locales/listLanguages HTTP/1.0" 304 0 "http://<public_ip>/index.html" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "..."
172.18.0.1 - - [04/Mar/2026:21:31:43 +0000] "GET /api/encryptionPublicKey HTTP/1.0" 304 0 "http://<public_ip>/index.html" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "..."

[r-chulkevich]

Hello! I have the same issue with Docker Engine on Ubuntu.

1. All containers are running, db-init completed successfully, all logs look correct.
2. http://localhost/api/ — works.
3. http://localhost/50x.html — returns the page.
4. http://localhost/ — shows an infinite loader "Checking Api status".

Important note: all static assets are fully loaded. A client request to http://localhost/api/encryptionPublicKey returns 304 with a successful payload, after which nothing else happens.

db logs:

Superuser configured successfully
2026/03/04 21:12:06 Server started at http://0.0.0.0:8090
├─ REST API:  http://0.0.0.0:8090/api/
└─ Dashboard: http://0.0.0.0:8090/_/

server logs:

INFO [2026-03-04 21:32:30]: (Server Core): GET /locales/listLanguages 304 0.398 ms
INFO [2026-03-04 21:32:30]: (Server Core): GET /encryptionPublicKey 304 0.491 ms

client logs:

172.18.0.1 - - [04/Mar/2026:21:31:42 +0000] "GET /index.html HTTP/1.0" 304 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "..."
172.18.0.1 - - [04/Mar/2026:21:31:43 +0000] "GET /api/locales/listLanguages HTTP/1.0" 304 0 "http://<public_ip>/index.html" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "..."
172.18.0.1 - - [04/Mar/2026:21:31:43 +0000] "GET /api/encryptionPublicKey HTTP/1.0" 304 0 "http://<public_ip>/index.html" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "..."

I managed to identify the issue. After opening the browser console, I saw the following error:

**Failed to initialize encryption: TypeError: Cannot read properties of undefined (reading 'importKey')**

It is related to this code:

return await crypto.subtle.importKey("spki", s.buffer, {
    name: "RSA-OAEP",
    hash: "SHA-256"
}, !1, ["encrypt"])

From this it became clear that the problem occurs because I was running the app on an IP address different from localhost. For the Crypto API to work in this case, HTTPS is required. Now it works!