Log error Blinko-website

[trijumeau]

Hello,
I installed Blinko on a Proxmox virtual machine with a Debian 12 image.
The containers are installed correctly. I can connect to the dashboard, but when I look at the blinko-website container logs, I get a loop of errors:

tRPC error: WZ [TRPCError]: Unauthorized
at /app/server/index.js:499:15498
at vBn (/app/server/index.js:496:64529)
at e (/app/server/index.js:496:64994)
at /app/server/index.js:3840:3343
at Array.map ()
at AWr (/app/server/index.js:3840:2864)
at async /app/server/index.js:3840:10611 {
cause: undefined,
code: 'UNAUTHORIZED'
}

I can't save my blinko backup: blinko_export.bko by clicking on it.

I find this program very interesting, but it's a shame I can't install it properly.

Do you have a solution?

Thanks in advance.

[dosubot[bot]]

Hi @trijumeau! I'm Dosu and I’m helping the blinko team.

The "tRPC Unauthorized" error in your blinko-website container usually means the server isn't recognizing your session or credentials. This often happens if authentication is misconfigured, cookies or tokens are missing, or environment variables like NEXTAUTH_URL, NEXT_PUBLIC, or HOSTNAME aren't set correctly in your Docker setup. If you're using OAuth (like Authentik or Microsoft Entra ID), this error is common after updates—built-in database logins work, but OAuth users may get stuck in a login loop or see repeated "Unauthorized" errors in the logs. Clearing your browser cache/cookies and quickly signing in sometimes helps, but it's not a permanent fix source.

For backup export, Blinko now restricts downloads to superadmins for security. If you're logged in but can't save the backup, check that your account has the right permissions. Also, make sure your Docker mounted data directory isn't owned by root—otherwise, Blinko can't write the backup file during export. Fix this by adjusting directory permissions so the container user has read/write access source.

Here's a quick troubleshooting checklist:

• Confirm you're logged in as a superadmin before exporting backups.
• If using OAuth, try clearing cookies/cache and signing in quickly.
• Check and set environment variables: NEXTAUTH_URL, NEXT_PUBLIC, and HOSTNAME=0.0.0.0 in your container.
• Make sure your Docker data directory is writable by the Blinko container user.
• If you updated Blinko, ensure all required utility functions are imported (for example, downloadFromLink in the backup export component) source.

If you still see the error, let me know your authentication method (local vs OAuth) and any proxy setup—those details help narrow down the cause.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[trijumeau]

Thank you for your quick response.
I'm a little confused because I don't understand everything.

I created a /docker/blinko folder and two subfolders, db and data.
I'm sending you my docker-compose.yml file.

I used "" for my username and password.

`networks:
blinko-network:
driver: bridge

services:
blinko-website:
image: blinkospace/blinko:latest
container_name: blinko-website
environment:
NODE_ENV: production
# NEXTAUTH_URL: http://localhost:1111
# NEXT_PUBLIC_BASE_URL: http://localhost:1111
NEXTAUTH_SECRET: "a long sentence"
DATABASE_URL: postgresql://postgres:"mypassword"@postgres:5432/postgres
depends_on:
postgres:
condition: service_healthy
volumes:
- /volume1/docker/blinko/data:/app/.blinko
restart: always
logging:
options:
max-size: "10m"
max-file: "3"
ports:
- 1111:1111
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:1111/"]
interval: 30s
timeout: 10s
retries: 5
start_period: 30s
networks:
- blinko-network

postgres:
image: postgres:14
container_name: blinko-postgres
restart: always
ports:
- 5435:5432
volumes:
- /volume1/docker/blinko/db:/var/lib/postgresql/data
environment:
POSTGRES_DB: postgres
POSTGRES_USER: postgres
POSTGRES_PASSWORD: "mypassword"
TZ: Europe/Paris
healthcheck:
test:
["CMD", "pg_isready", "-U", "postgres", "-d", "postgres"]
interval: 5s
timeout: 10s
retries: 5
networks:
- blinko-network

`

When I connect to my Debian server, I see the blinko_export.bko file in my /docker/blinko/data/files/ folder, so it's created correctly.
I don't understand what the token is for.

[trijumeau]

The installation is running correctly, the 2 containers are launched and the trpc error occurs as soon as I create the admin account