Antyrael

I've had this same issue, because the setup script exited earlier and I had to fix something else. Running `docker system prune -a -f` fixed it for me.

> Same issue, can connect to the device via web services, but no connection in home assistant. Wifi is ok, seems to have stopped working after the last ha os...

Same here. Just upgraded from 1.5.3 to 1.6.0, hoping it would resolve the issue. It didn't. Clicking multiple times on the Login button only results in my IP being blocked...

Hi, I changed the AD authentication settings to not use SSL and use the default port 389 so I could possibly see more information with tcpdump. Logging in actually worked...

TLS on port 389 did not work, I'm getting this error: `Warning: ldap_start_tls(): Unable to start TLS: Connect error in /var/www/phpipam/functions/adLDAP/src/adLDAP.php on line 655`

Yes, all related CA certificates are installed, as I mentioned earlier.

I can't tell if there are any flags in here that indicate what TLS version is used. Although I do see some incorrect checksums, but they don't mean anything to...

If you're using the Home Assistant HACS add-on, try using localhost as the hostname, or 127.0.0.1 as IP address.

I am running Wazuh Manager v4.8.2 and my agents are also v4.8.2, but I'm still seeing the timestamp discrepancy.   The timestamps shown on the dashboard are 2 hours...

I'm having the same issue, also for Peugeot, using country code NL. Relevant part of my logs: > 024-09-03 17:48:21,320 :: INFO :: App version 3.5.3 > 2024-09-03 17:48:22,515 ::...