Jeremy Sermersheim

I found that if the redis podman volume mount is not present, when the container is stopped/deleted, the ntopng admin password and other ntopng preferences are reset to their respective...

One additional comment I should make....you need to create the redis dir with the proper ownership: uid/gids inside container ``` root@router:/# ps -ef UID PID PPID C STIME TTY TIME...

you're prob hitting a permission issue...i added an additional comment in https://github.com/tusc/ntopng-udm/issues/9#issuecomment-871668315

if you append `--pem` to the LEGO_ARGS value in udm-le.sh it will automatically create the combined certificate that ntopng expects..then you can simply adjust your ntopng volume mount directly to...

Attached the log, but the only 'beacon' messages I see are: ``` [ +0.000005] RTW: OnBeacon: beacon keys ready [ +0.000007] RTW: OnBeacon: beacon keys ready [ +0.000006] RTW: OnBeacon:...

Hmm, my NetworkManager config is bare bones (/etc/NetworkManager/NetworkManager.conf is effectively blank), it's using the default wpa_supplicant backend (not iwd) and my wifi config file is: ``` [connection] id=myssid uuid=39a38116-0be8-48a7-9ffc-8a378c9330c5 type=wifi...

It works using the same basic config options (ssid, bssid, and psk) manually with wpa_supplicant directly but not using those same options with NetworkManager (I'm actually sending this message over...

Switching the wifi backend in NetworkManager to iwd, restarting NetworkManager, removing existing 'known wifi networks', killing the existing wpa_supplicant, and re-attempting a connection using the wifi settings in gnome control...

Still unsure why wpa_supplicant works natively, but not via NetworkManager using the default wifi.backend of wpa_supplicant. I can report however, that changing the backend to iwd seems to work pretty...

Comparing the sensor numbers with the mobile app seems to indicate (for me at least), that _0d looks like yesterday, _1d today, _2d tomorrow, etc when my local time is...