Live logs and reverse proxy

Hello everyone,

Since version 2024.11, I have problems with displaying my logs from the HMI connected to my reverse proxy.

Locally, I have no problems, but with the URL, I have the following problem:
Loading full log…

image

it’s finished with
Failed to get a0d7b954_grafana logs, Failed to fetch

here is my apache conf:

<VirtualHost *:443>
ServerName WEBSITEFQN
SSLEngine on
SSLProtocol all -SSLv2 -SSLv3
SSLProxyEngine On
RequestHeader set Front-End-Https “On”
ProxyPreserveHost On
RewriteEngine on
SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
SSLHonorCipherOrder on

ErrorLog ${APACHE_LOG_DIR}/error_has.websites.log
CustomLog ${APACHE_LOG_DIR}/access_has.website.log combined

Header always append Access-Control-Allow-Origin: “WEBSITEFQN”

ProxyRequests Off
ProxyPreserveHost on

ProxyPass /api/websocket ws://192.168.1.234:8123/api/websocket
ProxyPassReverse /api/websocket ws://192.168.1.234:8123/api/websocket

ProxyPass / http:// 192.168.1.234:8123/
ProxyPassReverse / http:// 192.168.1.234:8123/

RewriteEngine on
RewriteOptions inherit
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.) ws:// 192.168.1.234:8123/$1 [P,L]
RewriteCond %{HTTP:Upgrade} !=websocket [NC]
RewriteRule /(.
) http:// 192.168.1.234:8123/$1 [P,L]

SSLCertificateFile /etc/letsencrypt/live/has.website.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/has.website.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf

it’s look like that the follow function using this URL:

WEBSITEFQN/api/hassio/addons/a0d7b954_grafana/logs/follow?lines=100
but im using
WEBSITEFQN/hassio/addon/a0d7b954_grafana/logs

Does its normal?

Someone encounter this issue?

Thanks

2 Likes

I too had been experiencing issues similar to this. HA is completely functional but I lost access to my Addon Logs when I’m going through my reverse proxy… If I access the system through the internal address I can view my addon logs… This wasn’t an issue until recent updates over the last 2-3 weeks.

Having also this issue. Has someone found a fix?