SM411

I ran into the same issue. Found a fix for it here: https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence This command fixed my issue (might need to be modified for your setup) sudo chown -R 1000:1000 /mnt/user/appdata/nodered

Yep, there is an error with the template. I lost everything from my first setup upon docker update due this error.

I have lately been having issues with most of my torrents failing to update the tracker. It seems to not be tracker specific, but a general problem with my setup. I use binhex-delugevpn with PIA on unraid. The time until next announce keeps increasing and the client is not registered on the tracker. The only method I have found to manually force a update to the tracker is to "Edit Trackers" which seems to manually refresh and trigger a new announce and then the client is also registered on the tracker. Have anybody else experienced this issue? Is there any variables i can tweak to improve the success-rate? EDIT: I can not say for certain, but it seems that the issue is related to active_tracker_limit. Increasing this seems to have solved the issue.

I started running spants/mqtt as a broker for homeassistant/home-assistant and openzwave/ozwdaemon to communication between my home automation system and z-wave devices. I run all dockers on same network custom br0 where each has their own IP. From the start I have struggled with clients disconnecting from mqtt quite frequently. I'm not sure how to troubleshoot this as I am not familiar with how the protocol works. I'm looking for suggestions on how to troubleshoot these disconnects. What I have tried with no success is setting up a user for each client. I thought that there might be some conflict with multiple anonymous clients but I have not noticed any improvements. I have attached a log from the docker where I filter on disconnects. I have also converted time from epoc to human readable. # docker logs MQTT --tail 200000 2>&1 | grep disconnect 2020-05-22 14:52:35: Client 5927cacb-f79d-4041-8f19-4f7bd0264b08 has exceeded timeout, disconnecting. 2020-05-22 14:52:35: Socket error on client 5927cacb-f79d-4041-8f19-4f7bd0264b08, disconnecting. 2020-05-22 14:52:50: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting. 2020-05-22 14:52:50: Socket error on client mqtt_9c73a1f4.c7455, disconnecting. 2020-05-22 15:17:38: Client qt-openzwave-1 disconnected. 2020-05-22 15:17:38: Socket error on client qt-openzwave-1, disconnecting. 2020-05-22 15:18:16: Client fb0ab425-2281-40f1-820b-80d55d414fb1 has exceeded timeout, disconnecting. 2020-05-22 15:18:16: Socket error on client fb0ab425-2281-40f1-820b-80d55d414fb1, disconnecting. 2020-05-22 15:18:29: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting. 2020-05-22 15:18:29: Socket error on client mqtt_9c73a1f4.c7455, disconnecting. 2020-05-22 19:21:12: Client qt-openzwave-1 disconnected. 2020-05-22 19:21:12: Socket error on client qt-openzwave-1, disconnecting. 2020-05-22 19:21:51: Client ff1f7321-c154-438a-aeab-f58a3d9a582d has exceeded timeout, disconnecting. 2020-05-22 19:21:51: Socket error on client ff1f7321-c154-438a-aeab-f58a3d9a582d, disconnecting. 2020-05-22 19:22:12: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting. 2020-05-22 19:22:12: Socket error on client mqtt_9c73a1f4.c7455, disconnecting. 2020-05-23 04:55:21: Client 54b9a167-0813-4422-a97e-8768f5deeda1 has exceeded timeout, disconnecting. 2020-05-23 04:55:21: Socket error on client 54b9a167-0813-4422-a97e-8768f5deeda1, disconnecting. 2020-05-23 04:55:23: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting. 2020-05-23 04:55:23: Socket error on client mqtt_9c73a1f4.c7455, disconnecting. 2020-05-23 04:55:49: Client qt-openzwave-1 has exceeded timeout, disconnecting. 2020-05-23 04:55:49: Socket error on client qt-openzwave-1, disconnecting. 2020-05-23 06:30:29: Client qt-openzwave-1 disconnected. 2020-05-23 06:30:29: Socket error on client qt-openzwave-1, disconnecting. 2020-05-23 06:31:29: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting. 2020-05-23 06:31:29: Socket error on client mqtt_9c73a1f4.c7455, disconnecting. 2020-05-23 06:31:48: Client 465dcd1c-ccec-4b60-a9c5-a4aeb3a3baab has exceeded timeout, disconnecting. 2020-05-23 06:31:48: Socket error on client 465dcd1c-ccec-4b60-a9c5-a4aeb3a3baab, disconnecting. 2020-05-23 09:39:31: Client qt-openzwave-1 disconnected. 2020-05-23 09:39:31: Socket error on client qt-openzwave-1, disconnecting. 2020-05-23 09:40:24: Socket error on client 7bd74f74-0933-459c-9e95-26aa488f32f3, disconnecting. 2020-05-23 09:40:32: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting. 2020-05-23 09:40:32: Socket error on client mqtt_9c73a1f4.c7455, disconnecting. I have also attached log from ozwdaemon at one instance where it gets disconnected. This corresponds to the latest disconnect at 09.39 in mqtt log: [20200523 11:39:30.491 CEST] [qt.mqtt.connection] [debug]: bool QMqttConnection::sendControlPingRequest() [20200523 11:39:30.491 CEST] [qt.mqtt.connection.verbose] [debug]: bool QMqttConnection::writePacketToTransport(const QMqttControlPacket&) DataSize: 2 [20200523 11:39:30.511 CEST] [qt.mqtt.connection] [debug]: void QMqttConnection::transportError(QAbstractSocket::SocketError) QAbstractSocket::RemoteHostClosedError [20200523 11:39:30.511 CEST] [ozw.mqtt.publisher] [debug]: MQTT State Change 0 [20200523 11:39:30.511 CEST] [ozw.mqtt.publisher] [warning]: Exiting on Failure [20200523 11:39:30.511 CEST] [ozw.mqtt.publisher] [debug]: Disconnnected [20200523 11:39:30.511 CEST] [ozw.mqtt.publisher] [warning]: Broker Error 256

Thanks for making this docker. I was in need of a VOIP server, and managed to set it up in less than two minutes with the help of you. I have only one more suggestion, and it is already mentioned here before. Could we get mumble-server.ini in the data folder?

Thanks for the insight. I did check the log, and it seems that this time there was an automatic docker update for Home-Assistant running at the same time as parity check started. This would, just like the CA Backup, restart my Home Assistant docker. I changed the schedule of the docker update to avoid overlapping, and hopefully this will avoid orphaned images in the future. Orphaned images is not the main issue though, but the fact that the system which controls my home stops working until I get it set back up again.

This happened again this month. Anybody who could look into this?

I found something relevant in syslog file. There might be some more info here. I have attached the log for the relevant time period. syslog.txt

I have been running Unraid with multiple dockers for about two years. Tonight something wired happened. My Home-Assistant docker disappeared and left behind no warning. This is my most crucial docker as it controls much of my house. This is the first time this have happened, and it was quite easy to fix, but I would not like this to happen in the future. I have some suspicions on what could have caused it. First, it is the first day of october, and that means parity check on my unraid setup at midnight. This slows down my server which could possible lead to other errors. Secondly, I have recently set up CA Backup / Restore Appdata to backup appdata from my cache driver to the array. The settings is pretty much default and it runs weekly on mondays at 3 am, which also was tonight. I'm not sure which log or where to find them to explore this further. I checked my Home-assistant sensor logs, and the last entry was just before midnight when the parity check starts. So I guess a reasonable explanation could be that I should make sure that CA Backup and parity check should not run at the same time, but I'm also looking for tips on other potential errors which could cause orphan images and confirmation that my theory is either correct or wrong.

I'm still struggling to get access to WebUI when DelugeVPN run at Network Interface Custom: br0. Bridge works fine, and everything else than WebUI seems to work fine also for br0. I can connect with desktop client and VPN/torrents seems to work fine. The reason I want to do this is to run on same network interface as required by letsencrypt docker and make an reverse proxy. I did read the complete FAQ, but did not manage to solve the issue. I have attached my supervisord.log file to this post.

Yes Sent from my iPhone using Tapatalk

I'm having a similar issue. I changed the network of deluge to Custom: br0 from Bridge according to the manual of letsencrypt docker. I struggeled to get Deluge working, but somehow after an unRAID reboot I was able to connect and nginx reverse proxy worked perfect. This worked for about a week, but today I had to reboot the docker due to a change in VPN config and now I'm not able to access the web-ui anymore. I have tried anything that I can think of to get it up and running again without changing back to Bridge: Restarting Deluge docker (20 times +/-) Stopping and starting Docker service Starting Deluge with no other dockers running Rebooting the router Rebooting unRAID Started deluge docker in bridge, which works perfectly.

I have still not solved this issue. The suggestion above did not work. I have some additional information which could be useful. I have another Ubuntu Server 16.04 VM which is usualy shut down. I span this up and it has network. I think the issue might not be caused by upgrading Unraid but updating Ubuntu with apt, and then going into effect with rebooting the VM for upgrading unraid.

Did you ever figure this out? I have the exact same issue after updating unraid from 6.5.0 to 6.5.2. Can provide more info if required.

Yesterday I recived the Fall (Fail) update. It caused issues similar to those in this post. I could not fix it though be deleting the credentials. I googled some and found this Windows Support article: https://support.microsoft.com/en-us/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016 Windows 10 Enterprise and Windows 10 Education does not longer allow anonymous connection to SMB by default. I run Education version and managed to fix it by changing this registry entry to 1. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] "AllowInsecureGuestAuth"=dword:1