New installation shows blank screen
Closed this issue · 4 comments
I installed this add-on v 2.0.0, but when trying to go tho the pgAdmin 4 screen, I am left with an empty screen...
My add-on configuration is default, no port forwardings.
logs:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: pgAdmin4
A PostgreSQL Management and Query tool
-----------------------------------------------------------
Add-on version: 2.0.0
You are running the latest version of this add-on.
System: Home Assistant OS 7.5 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2022.3.5
Home Assistant Supervisor: 2022.03.4
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] pgadmin4.sh: executing...
[cont-init.d] pgadmin4.sh: exited 0.
[cont-init.d] user.sh: executing...
[cont-init.d] user.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[16:14:47] INFO: Starting pgAdmin..
[16:15:07] INFO: Waiting for pgadmin to become available..
.
.
.
[2022-03-16 16:15:08 +0100] [559] [INFO] Starting gunicorn 20.1.0
[2022-03-16 16:15:08 +0100] [559] [INFO] Listening at: unix:/tmp/pgadmin4.sock (559)
[2022-03-16 16:15:08 +0100] [559] [INFO] Using worker: gthread
[16:15:08] INFO: Starting NGinx...
[2022-03-16 16:15:08 +0100] [567] [INFO] Booting worker with pid: 567
[16:15:08] NOTICE: pgAdmin4 is ready to accept connections.
nginx: [warn] lua_load_resty_core is deprecated (the lua-resty-core library is required since ngx_lua v0.10.16) in /etc/nginx/nginx.conf:43
[16:15:08] NOTICE: pgAdmin is running.
[16/Mar/2022:16:15:53 +0100] 302 <laptop ip address>, <proxy ip address>, 172.30.32.1(172.30.32.2) GET / HTTP/1.1 (Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:97.0) Gecko/20100101 Firefox/97.0)
[16/Mar/2022:16:16:02 +0100] 302 <laptop ip address>, <proxy ip address>, 172.30.32.1(172.30.32.2) GET / HTTP/1.1 (Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:97.0) Gecko/20100101 Firefox/97.0)
Can you tell me what I am missing?
It looks like it's running fine there..
Can you access it using the sidebar in home assistant instead of a local IP addreess?
Just did a test with this configuration:
Using Microsoft Edge or Chrome seems OK:
Can you try to refresh your browser witrh ctrl+F5 ?
Maby there are some old files in the cache.
I think I have narrowed it down a bit.
the ingress url is blocked because of "Mixed Content"
My setup uses a https proxy redirecting to hass on http.
I'm guessing the ingress url uses the default protocol for some reason.
I use HAProxy myself to expose Home Assistant on HTTPS. That seems to work fine., although I use it from the sidebar.
Can you give me some logs from the Chrome network debugger? Maybe I can help you sort this out.