kimocal

My wife and I are the only users for our nextcloud instance. We recently started having an issue where the connection will die and I will have to restart the container. Attached is my syslog I am getting from the syslog server. Any ideas based upon the syslog? Apr 11 15:11:14 tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="23380" x-info="https://www.rsyslog.com"] start Apr 11 15:14:33 tower ool www[30194]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Apr 11 15:14:35 tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="30614" x-info="https://www.rsyslog.com"] start Apr 11 16:35:02 tower kernel: docker0: port 2(veth048550e) entered disabled state Apr 11 16:35:02 tower kernel: veth4f0e390: renamed from eth0 Apr 11 16:35:02 tower kernel: docker0: port 2(veth048550e) entered disabled state Apr 11 16:35:02 tower kernel: device veth048550e left promiscuous mode Apr 11 16:35:02 tower kernel: docker0: port 2(veth048550e) entered disabled state Apr 11 16:35:02 tower kernel: docker0: port 2(veth4583332) entered blocking state Apr 11 16:35:02 tower kernel: docker0: port 2(veth4583332) entered disabled state Apr 11 16:35:02 tower kernel: device veth4583332 entered promiscuous mode Apr 11 16:35:02 tower kernel: docker0: port 2(veth4583332) entered blocking state Apr 11 16:35:02 tower kernel: docker0: port 2(veth4583332) entered forwarding state Apr 11 16:35:02 tower kernel: eth0: renamed from veth4daad3b Apr 11 16:35:02 tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4583332: link becomes ready Apr 11 16:35:02 tower kernel: docker0: port 9(vethdcf57da) entered disabled state Apr 11 16:35:02 tower kernel: veth0389db9: renamed from eth0 Apr 11 16:35:03 tower kernel: docker0: port 9(vethdcf57da) entered disabled state Apr 11 16:35:03 tower kernel: device vethdcf57da left promiscuous mode Apr 11 16:35:03 tower kernel: docker0: port 9(vethdcf57da) entered disabled state Apr 11 16:35:03 tower kernel: docker0: port 9(vethd8cddd5) entered blocking state Apr 11 16:35:03 tower kernel: docker0: port 9(vethd8cddd5) entered disabled state Apr 11 16:35:03 tower kernel: device vethd8cddd5 entered promiscuous mode Apr 11 16:35:03 tower kernel: docker0: port 9(vethd8cddd5) entered blocking state Apr 11 16:35:03 tower kernel: docker0: port 9(vethd8cddd5) entered forwarding state Apr 11 16:35:03 tower kernel: eth0: renamed from veth976f3a7 Apr 11 16:35:03 tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd8cddd5: link becomes ready Apr 11 17:15:04 tower kernel: veth2e3f8cd: renamed from eth0 Apr 11 17:15:04 tower kernel: eth0: renamed from veth79ca70e

**UPDATE** I forgot to add the IP of the sever in the remote part. It's working now. ____________________________________________________________________________ I am running unraid 6.12.3 on this server at the moment. Currently trying to troubleshoot a Nextcloud container of it needing a restart every once in a while. I set-up the local syslog server per the directions in this post with the following settings initially: I didn't see anything in the syslog_local share after 24 hours. I then changed the syslog server settings to this: I've been letting it run and I am still not seeing anything in the syslog_local share: Thoughts?

Changed Status to Solved Solution: Force Update on the containers

Here's an update that fixed the Container WebUI issues. I updated 2 of my docker containers that had new updates and they are now showing the WebUI link: I then forced Update some others and they are now showing the WebUI link: Before After After force updating all my containers they are now all showing the WebUI link.

Another user going from 6.9.2 to 6.12.1 is reporting the same issue. I have asked them to post their diagnostics here to help.

It's a bit odd it's happening on 2 different unraid servers. The common part is they were both updated from 6.9.2.

No. I clicked through every container on both boxes and none have a WebUI link: Both boxes were running for about 18 hours. I rebooted both of them about an hour ago and the issue is still present.

Is anyone else's container not downloading? It was working fine a day ago for me. Edit #1 Appears that it can't connect to eweka: TLS handshake failed for news.eweka.nl I'm using PIA and OpenVPN. Edit #2 I swapped over to Wireguard to see if there is a difference. Getting the same error. I then tried changing the port to 119 and setting Encryption to No and it is able to connect. Setting CertCheck to No doesn't make a difference either with SSL enabled. Edit #3 So if using port 119 and wireguard is up it should be safe to run it that way? I am no longer encrypted, correct or does it still use PIA to mask the traffic if using 119? Another weird thing is that I restart NZBgetvpn after setting port 119, I can successfully connect to eweka, but then nothing downloads still. Edit #4 I tried using GrabIt on my Win box and was able to connect to eweka without any issue. Really at a loss now with NZBget 😕 Edit #5 I ran this command from the unraid terminal & container console: openssl s_client -showcerts -connect news.website:563 The terminal returns a cert but the container gets stuck on CONNECTED(00000003) Edit #6 It must eweka as I am able to use newsdemon without any issue on their ssl ports =P Edit#7 Last update for the time being. I disabled the VPN part of the container and eweka connects fine now over both SSL ports. Maybe PIA updated something recently that broke the ability to connect. I tried routing the nzbget container traffic through a binhex-privoxy container with PIA and same issues happens.

I have a general best practices question. Are there any issues to consider when running multiple DBs in one MariaDB container? I originally setup MariaDB to be used with Nextcloud. I then created another DB to use with my HomeAssistant VM. Both have been working great. I'm about to add another DB for SuiteCRM to the same MariaDB docker instance. Is it best/better practice to have multiple MariaDB dockers for this scenario or should there not be any real issues doing this? There will only be 2 users with SuiteCRM. There are currently only 2 Nextcloud users too.

I don't know why it won't work when placed in the AppData location but I downloaded the cert.pem file linked above and placed it in my "Downloads" folder. I then modified the settings in NZBGETVPN and it started downloading just now.

I don't know if it will work for this docker but for the jshridha/docker-nzbgetvpn version, I copied the cert.pem file from here and placed it in my "Downloads" folder. I then modified the settings in NZBGETVPN and it started downloading just now.

This fixed the recently connection issues I've been having too with the PIA VPN in nzbgetvpn.

How can I trigger a docker script to run by accessing a specific website/IP? I was watching this video about a PiHole docker and want to do something similar minus the Alexa part. I know I can run a docker script thru the command line via the docker exec command. I only know how to run a script via a cron job or the command line. The end goal is to make it so myself or wife only needs to click a bookmark in a browser to either run the blockdomains or unblockdomains scripts shown in the above video. These bookmarks would just be to local LAN addresses of the PiHole container like 192.168.10.5:XXXX/block or similar as shown in the YouTube video. Any tips or links to learn some more on how to do this?

Thanks @uberchuckie It's up and running. I pointed to my Maria DB docker so not sure if that's what fixed it. I was able to add my Ubiquiti ER-X device for it to monitor, as all I'm really interested in is tracking my monthly data usage thru my ISP. Beyond that I haven't had much time to tinker with it though.