Bad Gateway in Home Assistant

[SeriousPat]

Describe the issue you are experiencing

I have still the Bug in HA.
I can Access the GUI inside HA. After some Time/Days i want access again the GUI, the Bad Gateway Error occurs.
Like in : #2720
If i restart the Addon, i cann access the Gui again for some time.
I allready tried reinstalled the whole AddOn.

Describe the behavior you expected

I can allways acces the Raspberrymatic GUI inside HA.

Steps to reproduce the issue

...

What is the version this bug report is based on?

3.79.6.20241031

Which base platform are you running?

ha-addon (HomeAssistant Add-on)

Which HomeMatic/homematicIP radio module are you using?

HmIP-RFUSB

Anything in the logs that might be useful for us?

Identifying host system: QEMU Standard PC (Q35 + ICH9, 2009) (oci), OK
Initializing RTC Clock: onboard, OK
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Running seedrng: OK
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.1, OK
Identifying Homematic RF-Hardware: ....HmRF: HMIP-RFUSB/eQ-3 HmIP-RFUSB@usb-0000:00:07.0-1, HmIP: HMIP-RFUSB/eQ-3 HmIP-RFUSB@usb-0000:00:07.0-1, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: 4.4.18, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: .......OK
Starting rfd: .OK
Starting HMIPServer: .........OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.79.6.20241031 (raspmatic_oci_amd64)

Additional information

No response

[jens-maus]

Sorry, but this must be a different issue than #2720. So please enable ssh and next time the issue happens report back to analyze the issue or if someone else come up with the same or a similar issue. But for now this isn't reproducible by me, I am afraid.

[github-actions]

@SeriousPat, the maintainer of this project has requested more detailed information or a specific feedback. Please provide this feedback and report back ASAP or this ticket will be automatically marked as stale after a certain short grace period.

[github-actions]

@SeriousPat, the issue you reported does not seem to be reproducible by the maintainer of this project. Please provide additional information and more detail and please try to reproduce your problem with a fresh test installation and try to find other users having the same problems so that they can support your observations.

[SeriousPat]

Sorry, but this must be a different issue than #2720. So please enable ssh and next time the issue happens report back to analyze the issue or if someone else come up with the same or a similar issue. But for now this isn't reproducible by me, I am afraid.

Alles klar, ich kann mich auch melden wenn der Fehler wieder da ist und wir können im Jitsi oder sonst wo gemeinsam drauf schauen wenn du mal Zeit hast.