No logs displayed in Frontend

[gypais]

Describe the issue you are experiencing

This is exactly the same problem as the 6103 that was closed. #6103

But I'm not using Cloudflare Tunnel, so my problem isn't there.

I tried in safe mode, same result.

I also get the logs if I look via the console: ha apps log core_ssh for example.

The only logs I can see via the browser (fronted) are the Home Assistant Core logs. All the other logs get stuck on "Loading log…"
Thanks

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Steps to reproduce the issue

...

Anything in the Supervisor logs that might be useful for us?

I can't display it!!!

System information

System Information

version	core-2026.5.1
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	amd64
user	root
virtualenv	false
python_version	3.14.2
os_name	Linux
os_version	6.12.85-haos
arch	x86_64
timezone	Europe/Paris
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	3057
Downloaded Repositories	10

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 17.3
update_channel	stable
supervisor_version	supervisor-2026.05.0
agent_version	1.8.1
docker_version	29.3.1
disk_total	30.8 GB
disk_used	16.0 GB
nameservers	192.168.1.254, fd0f:ee:b0::1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization	qemu
board	ova
supervisor_api	ok
version_api	ok
installed_addons	OpenThread Border Router (2.16.8), File editor (6.0.0), Matter Server (8.4.0), ESPHome Device Builder (2026.3.2), Terminal & SSH (10.2.0), Linky (1.7.0), Get HACS (1.3.1), Matterbridge (2026.5.1), Battery Sentinel Plus (2026.05.2)

Dashboards

dashboards	2
resources	4
views	5
mode	storage

Network Configuration

adapters	lo (disabled), enp0s1 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth15f54b9 (disabled), veth0f6ad31 (disabled), vethc909faf (disabled), veth3370c33 (disabled), veth41d5a10 (disabled), vethccd117c (disabled), veth84ded83 (disabled), wpan0 (disabled)
ipv4_addresses	lo (127.0.0.1/8), enp0s1 (192.168.1.95/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth15f54b9 (), veth0f6ad31 (), vethc909faf (), veth3370c33 (), veth41d5a10 (), vethccd117c (), veth84ded83 (), wpan0 ()
ipv6_addresses	lo (::1/128), enp0s1 (fe80::58b1:7db9:3b88:64e6/64), docker0 (fe80::3867:44ff:fe7b:1b1a/64), hassio (fd0c:ac1e:2100::1/48, fe80::e855:77ff:fe9b:a0fa/64), veth15f54b9 (fe80::b4cc:d1ff:fee7:9aee/64), veth0f6ad31 (fe80::c42e:44ff:fe4f:dc41/64), vethc909faf (fe80::d472:f0ff:fe2f:235f/64), veth3370c33 (fe80::a437:53ff:fe96:188b/64), veth41d5a10 (fe80::9400:8bff:fe5e:a291/64), vethccd117c (fe80::6841:7fff:fe58:1f5d/64), veth84ded83 (fe80::ac21:a9ff:feb8:7399/64), wpan0 (fd37:5727:dff5:1:122e:7eb4:f494:3609/64, fd1c:90ad:b745:ba00:0:ff:fe00:fc38/64, fd1c:90ad:b745:ba00:0:ff:fe00:fc10/64, fd1c:90ad:b745:ba00:0:ff:fe00:8400/64, fd1c:90ad:b745:ba00:f9ee:67ea:c413:db05/64, fe80::c049:6e0a:d8a7:471f/64)
announce_addresses	192.168.1.95, fe80::58b1:7db9:3b88:64e6

Recorder

oldest_recorder_run	6 mai 2026 à 19:31
current_recorder_run	17 mai 2026 à 08:06
estimated_db_size	90.07 MiB
database_engine	sqlite
database_version	3.49.2

Sonoff

version	3.11.1 (66624ed)
cloud_online	2 / 5
local_online	0 / 0

Supervisor diagnostics

home-assistant_2026-05-17T07-25-12.988Z.log

Additional information

No response

[agners]

What browser are you using? What (type of) URL are you using to access Home Assistant?

What I find a bit interesting is that your network configuration shows an IPv6 DNS server (fd0f:ee:b0::1) while your main interface enp0s1 has no IPv6 address 🤔

[gypais]

hi, i use chrome, but it's the same thing with safari.
http://192.168.1.95:8123/config/logs?provider=supervisor
I'm using thread/matter in IPV6
http://192.168.1.95:8123/config/logs?provider=core -->ok
http://192.168.1.95:8123/config/logs?provider=supervisor-->ko

[agners]

So you are seeing just "Loading log…"?

I also get the logs if I look via the console: ha apps log core_ssh for example.

The Core is acting as proxy for Supervisor logs. Is there anything in the Core logs which hints of a problem? Can you share the Core logs?

Can you run ha supervisor logs, any error reported there?

[gypais]

So you are seeing just "Loading log…"?
yes for all log except for HA core

I also get the logs if I look via the console: ha apps log core_ssh for example.

The Core is acting as proxy for Supervisor logs. Is there anything in the Core logs which hints of a problem? Can you share the Core logs?
nothing, as you can see in the attached file

log-core-jpp.txt

Can you run ha supervisor logs, any error reported there?
nothing special

log-supervisor.txt

[agners]

Hm, I don't see anything which would caught my eye in that log. I wonder if the request hits Core even. Do you see something in Developer console maybe?

Was this always the case or did this start recently?

[gypais]

Hm, I don't see anything which would caught my eye in that log. I wonder if the request hits Core even. Do you see something in Developer console maybe?
Where exactly?

Was this always the case or did this start recently?
From begining.
It looks like a communication problem. What are the differences between the display techniques of HA-core and supervisor? A log is a log!
Is there a way to put the display in debug mode to see what's happening behind the waiting message?
thanks