dcaputo-harmoni / open-balena-admin

Open Balena Admin
MIT License
90 stars 18 forks source link

Cannot launch admin page #36

Closed MiroYld closed 4 months ago

MiroYld commented 4 months ago

Good morning, When I try to access the Open Balena admin page I get a completely blank page and errors in the console. However, I do have the react logo and Open Balena Admin in my bar I access it from my domain name, http://admin.my-domain.com:8080

CONTAINER ID IMAGE COMMAND STATUS CREATED PORT NAMES
17df85235d44 harmonidcaputo/open-balena-ui:latest "bash start.sh" 9 minutes ago More than 7 minutes 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp openbalena-admin_ui_1
601b132710c3 harmonidcaputo/open-balena-remote:latest "bash start.sh" 9 minutes ago More than 7 minutes 0.0.0.0:10000-10009->10000-10009/tcp, :::10000-10009->10000- 10009/tcp openbalena-admin_remote_1
89a4ce28d3a4 harmonidcaputo/open-balena-postgrest:latest "bash start.sh" 9 minutes ago More than 7 minutes 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp openbalena-admin_postgrest_1

Ports are exposed on 8080. Here is also what I have visually image image

Also, here are some logs, everything looks correct

ubuntu@ubuntu2004-firat:/home/balena/admin$ docker logs 601b132710c3
[2024/03/01 08:51:42:0014] N: ttyd 1.7.3-a2312cb (libwebsockets 4.0.20)
[2024/03/01 08:51:42:0250] N: tty configuration:
[2024/03/01 08:51:42:0251] N:   start command: /usr/src/app/scripts/connect-ssh.sh
[2024/03/01 08:51:42:0253] N:   close signal: SIGHUP (1)
[2024/03/01 08:51:42:0254] N:   terminal type: xterm-256color
[2024/03/01 08:51:42:0255] N: endpoints:
[2024/03/01 08:51:42:0256] N:   base-path: /ttyd
[2024/03/01 08:51:42:0256] N:   index    : /ttyd/
[2024/03/01 08:51:42:0257] N:   token    : /ttyd/token
[2024/03/01 08:51:42:0258] N:   websocket: /ttyd/ws
[2024/03/01 08:51:42:0259] N:   allow url arg: true
[2024/03/01 08:51:42:1326] N:  Using foreign event loop...
[2024/03/01 08:51:42:1347] N:  Listening on port: 7681
[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10000.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10001.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10002.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10003.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10004.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10005.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10006.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10007.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10008.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10009.
Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

Connected!
[2024/03/01 08:53:04:3998] N: ttyd 1.7.3-a2312cb (libwebsockets 4.0.20)
[2024/03/01 08:53:04:4117] N: tty configuration:
[2024/03/01 08:53:04:4117] N:   start command: /usr/src/app/scripts/connect-ssh.sh
[2024/03/01 08:53:04:4117] N:   close signal: SIGHUP (1)
[2024/03/01 08:53:04:4118] N:   terminal type: xterm-256color
[2024/03/01 08:53:04:4118] N: endpoints:
[2024/03/01 08:53:04:4118] N:   base-path: /ttyd
[2024/03/01 08:53:04:4118] N:   index    : /ttyd/
[2024/03/01 08:53:04:4118] N:   token    : /ttyd/token
[2024/03/01 08:53:04:4118] N:   websocket: /ttyd/ws
[2024/03/01 08:53:04:4118] N:   allow url arg: true
[2024/03/01 08:53:04:5593] N:  Using foreign event loop...
[2024/03/01 08:53:04:5733] N:  Listening on port: 7681
[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10000.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10001.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10002.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10003.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10004.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10005.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10006.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10007.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10008.[HPM] Proxy created: /  -> 
Waiting for 127.0.0.1:10009.
Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

Connected!

I also checked my config in the activate file, everything is correct in terms of secrets etc.

MiroYld commented 4 months ago

I'm sorry for this outcome, it ended up not being one. The error was because the secrets in activate contained extra characters