nsutherland

I had problems after upgrading mine to 2.7.0, which was giving me the following error: [2025-12-02 00:17:16] error: z2m: Error while starting zigbee-herdsman [2025-12-02 00:17:16] error: z2m: Failed to start zigbee-herdsman [2025-12-02 00:17:16] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2025-12-02 00:17:16] error: z2m: Exiting... [2025-12-02 00:17:17] error: z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:115:27) at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:143:29) at Zigbee.start (/app/lib/zigbee.ts:70:27) at Controller.start (/app/lib/controller.ts:101:13) at start (/app/index.js:149:5)I tried a ton of things, including downgrading to releases 2.6.3, 2.6.2, and 2.6.1 - deleting the container and image and rebuilding it - none of this helped though, no luck. I eventually got it back up and running, not sure if this is what did it, but the last things I did were reorder some of the configuration.yaml entries, used a different TCP port, and lastly, re-flashed my SLZB-MR3 zigbee-coordinator radio with the same firmware version, and restarted zigbee on it. My linter indicated nothing wrong with the configuration.yaml file and I hadn't changed it... so I don't think that was it, I think it was just gremlins in my SLZB-MR3?

I just wanted to chime in as I am experiencing the same issue after upgrading to version 7.1.4, where my server would become unreachable basically daily. I don't have a keyboard/display hooked up to my server, but I could see it was online when it went unreachable, and I would reboot it and it would come up fine. I turned on syslog mirroring to my flash so I could check the syslog after these reboots, and found that I had the exact same syslog messages as seen here (r8169 error messages / link down). I converted my docker configuration from macvlan to ipvlan as was suggested elsewhere, which did not resolve the issue. The server went unreachable again, and I received the same syslog message. After the last reboot I went ahead and installed the realtek driver for r8168 from community apps, rebooted for the driver to take effect, and so far so good. I have not yet had another instance of it going unreachable.

It looks like one of the last updates to SWAG changed the behaviour so that it will only read in nginx/site-confs files if they have .conf in the filename, which broke redirection to my radarr/sonarr subdomains (I was getting the default swag homepage instead). I looked at an old backup of my SWAG appdata folder and noticed that in the update, it had replaced my previous 'default' file with 'default.conf' and a sample file. See the log entries below that led me to look into that: **** The following active confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare the following files to the samples in the same folder and update them. **** **** Use the link at the top of the file to view the changelog. **** /config/nginx/nginx.conf /config/nginx/ldap-server.conf /config/nginx/authelia-location.conf /config/nginx/authelia-server.conf /config/nginx/ssl.conf /config/nginx/proxy.conf /config/nginx/site-confs/default.conf I have a subdomain called "services" that points to my radarr/sonarr sites. The filename to redirect to those sites was named 'services' with no filetype extension. The fix for me was simple, and just required that I rename that file to 'services.conf' so that it would read the file, and a restart of the docker to pick up the change.

Thanks CHBMB and sparklyballs, appreciate the support. I updated my docker repository and I've confirmed the graphs are working now. I will await the official 6.4 release of UnRAID and update my docker back to the main repository.

I'm also having the issue in which it's not graphing any data. I've not had any issue accessing the webgui. I've tried deleting the docker and building it from scratch multiple times with no success. I'd be happy to provide any data requested. Here are the logs of it booting up: https://www.linuxserver.io/donations/-------------------------------------GID/UID-------------------------------------User uid: 99User gid: 100-------------------------------------[cont-init.d] 10-adduser: exited 0.[cont-init.d] 30-config: executing...[cont-init.d] 30-config: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message### assuming you are using an fping copy reporting in millisecondsSmokeping version 2.006011 successfully launched.Not entering multiprocess mode for just a single probe.FPing: probing 20 targets with step 300 s and offset 34 s.