jude

Try Changing the Peer DNS Server to something like CloudFlares 1.1.1.1 Thats the only difference I see from my setup and yours

I'm having trouble after updating from version 17 to 18.0.10 It gets to the screen: Nextcloud will be updated to version 18.0.10 and then after I click on the Start Update button it has an error InvalidArgumentException: Column name "oc_flow_operations"."entity" is NotNull, but has empty string or null as default. I set this up following @SpaceInvaderOne's YouTube tutorial and I'm not sure how to make the necessary change to the MariaDB to fix the error the following link references the error and the solution https://github.com/nextcloud/server/issues/23174 I tried a number of the suggestions and they didn't work. None of them were specific to unraid dockers though. If someone could please provide a step by step of the commands needed in the MariaDB Docker console that would be very much appreciated

I decided to delete the contents of the openvpn folder again and redownload the files from https://www.privateinternetaccess.com/openvpn/openvpn.zip . Copied the three files needed back to the openvpn folder and this time the container started up no problem. I don't know what the problem was but its working and that's all the matters. Thank you for the help!

I can't access the console. I don't think it's accessible until the container starts and it won't start. It still feels like a permissions issue ........ but maybe its something else

hmmm pretty sure thats setup right but maybe ....... Container Path: /config host path: /mnt/cache/appdata/binhex-delugevpn the docker created the openvpn folder in /mnt/cache/appdata/binhex-delugevpn so the container path /config/openvpn/ should translate to /mnt/cache/appdata/binhex-delugevpn/openvpn/ unless i'm messing something up

I ran the following command chmod -R 777 /mnt/user/appdata/binhex-delugevpn/openvpn now the file permissions look like this root@Tower:/mnt/user/appdata/binhex-delugevpn/openvpn# ls -al total 12 drwxrwxr-x 1 nobody users 6 Jul 17 12:07 ./ drwxrwxr-x 1 nobody users 239 Jul 17 09:02 ../ -rwxrwxrwx 1 nobody users 2025 Jul 15 07:59 ca.rsa.2048.crt* -rwxrwxrwx 1 nobody users 869 Jul 15 07:59 crl.rsa.2048.pem* -rwxrwxrwx 1 nobody users 3180 Jul 15 07:59 toronto.ovpn* And i'm still getting the same start error 2020-07-17 16:32:28.135552 [info] System information Linux 56018defcf38 4.19.107-Unraid #1 SMP Sun Mar 8 14:34:03 CDT 2020 x86_64 GNU/Linux 2020-07-17 16:32:28.155602 [info] OS_ARCH defined as 'x86-64' 2020-07-17 16:32:28.177680 [info] PUID defined as '99' 2020-07-17 16:32:28.199094 [info] PGID defined as '100' 2020-07-17 16:32:28.250136 [info] UMASK defined as '000' 2020-07-17 16:32:28.269896 [info] Permissions already set for volume mappings 2020-07-17 16:32:28.292303 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2020-07-17 16:32:28.312127 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2020-07-17 16:32:28.331927 [info] VPN_ENABLED defined as 'yes' 2020-07-17 16:32:28.354248 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...

Hey @Geekd4d I think you're right seems like it could be a permissions issue. Any ideas on the commands I need to run to set the permissions so that the docker can access that file properly?

OK tried removing the space from the file name. Its now Toronto.ovpn root@Tower:/mnt/user/appdata/binhex-delugevpn/openvpn# ls -al total 12 drwxrwxr-x 1 nobody users 6 Jul 17 12:03 ./ drwxrwxr-x 1 nobody users 239 Jul 17 09:02 ../ -rw-rw-rw- 1 nobody users 3180 Jul 15 07:59 Toronto.ovpn -rw-rw-rw- 1 nobody users 2025 Jul 15 07:59 ca.rsa.2048.crt -rw-rw-rw- 1 nobody users 869 Jul 15 07:59 crl.rsa.2048.pem still not starting. See log 2020-07-17 12:03:58.879125 [info] System information Linux 56018defcf38 4.19.107-Unraid #1 SMP Sun Mar 8 14:34:03 CDT 2020 x86_64 GNU/Linux 2020-07-17 12:03:58.898479 [info] OS_ARCH defined as 'x86-64' 2020-07-17 12:03:58.917293 [info] PUID defined as '99' 2020-07-17 12:03:58.937562 [info] PGID defined as '100' 2020-07-17 12:03:58.974703 [info] UMASK defined as '000' 2020-07-17 12:03:58.992439 [info] Permissions already set for volume mappings 2020-07-17 12:03:59.011408 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2020-07-17 12:03:59.029829 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2020-07-17 12:03:59.048154 [info] VPN_ENABLED defined as 'yes' 2020-07-17 12:03:59.070252 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting... Really odd that its kicking out an error that it can't find a .ovpn file and there is clearly one there

I used to have this working fine in the past and i'm setting it up again from scratch. I'm having an error getting it to start and I'm following @SpaceInvaderOne updated tutorial I'm getting this error in the log file 2020-07-17 09:03:59.883147 [info] System information Linux 56018defcf38 4.19.107-Unraid #1 SMP Sun Mar 8 14:34:03 CDT 2020 x86_64 GNU/Linux 2020-07-17 09:03:59.903354 [info] OS_ARCH defined as 'x86-64' 2020-07-17 09:03:59.923477 [info] PUID defined as '99' 2020-07-17 09:03:59.945295 [info] PGID defined as '100' 2020-07-17 09:03:59.982184 [info] UMASK defined as '000' 2020-07-17 09:04:00.001174 [info] Permissions already set for volume mappings 2020-07-17 09:04:00.022941 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2020-07-17 09:04:00.043588 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2020-07-17 09:04:00.062902 [info] VPN_ENABLED defined as 'yes' 2020-07-17 09:04:00.085933 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting... I have downloaded the CA Toronto.ovpn file as well as the ca.rsa.2048.crt and crl.rsa.2048.pem files and copied them to the openvpn config folder (/mnt/cache/appdata/binhex-delugevpn/openvpn) as can be seen below root@Tower:/mnt/user/appdata/binhex-delugevpn/openvpn# ls -al total 12 drwxrwxr-x 1 nobody users 6 Jul 17 09:16 ./ drwxrwxr-x 1 nobody users 239 Jul 17 09:02 ../ -rw-rw-rw- 1 nobody users 3180 Jul 15 07:59 CA\ Toronto.ovpn -rw-rw-rw- 1 nobody users 2025 Jul 15 07:59 ca.rsa.2048.crt -rw-rw-rw- 1 nobody users 869 Jul 15 07:59 crl.rsa.2048.pem If I turn off the Container Variable: VPN_ENABLED then Deluge will start and I can access the GUI - not all that useful without the VPN though. I'm sure I'm missing something simple here but I can't figure out what.

I am having big problems with the video.meet.jitsi docker using more and more RAM. I had originally poster a question in another Jitsi thread and realise now that this is a more appropriate place to look for an answer. Original post Everything seems to work the way it should in terms of making meetings and video calls but the docker is quickly consuming RAM and this is while it is idle and no meetings or calls have happened. I restarted it this morning and in the last 4 hours the RAM usage for video.meet.jitsi has increased to 1.014GB and climbing. Any ideas on what is using the RAM and how I can stop this from happening?

Thanks I'm going to post my question into the Jitsi video support thread for @SpaceInvaderOne 's video. I should have posted there in the first place.

OK when I go into Portainer to check the log location and size for docker video.meet.jitsi it gives this location LogPath /var/lib/docker/containers/59c547b2df9694533b3e20444a0152279ad19096a515a3713a04e88c8cb94d3d/59c547b2df9694533b3e20444a0152279ad19096a515a3713a04e88c8cb94d3d-json.log when I go to that location in /var and find 59c547b2df9694533b3e20444a0152279ad19096a515a3713a04e88c8cb94d3d-json.log it shows the log file as 12,106K and rising slowly. At the same time Unraid's docker container management page shows video.meet.jitsi using 365.3MiB of RAM (and rising consistently) So I'm not sure that the log entries are creating the expanding RAM usage. Jitsi has been running for 25 minutes. I can't see where or how to change the log levels for each container in Unraid dockers or in Portainer. Can you give me the location for that please and thank you

Anyone else seeing the video.meet.jitsi docker using more and more RAM while it is idle? I installed using @SpaceInvaderOne youtube tutorial. Thankyou! Everything appears to be working correctly. I have forwarded the correct ports including UDP 10000. I can access Jitsi from my letsencrypt subdomain and i'm able to host meetings. I restarted Jitsi from Portainer yesterday by this morning video.meet.jitsi was using 3GB of RAM. I restarted it four hours ago and the RAM has already risen to 1.04GB. All of this has happened with no calls or video meets. Log for video.meet.jitsi Apr 28, 2020 1:50:46 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:50:50 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Running expire() Apr 28, 2020 1:50:56 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=da5ba21b2fd0ab2a gid=null logging=false Apr 28, 2020 1:50:56 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:51:06 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=adf53a44c98d816f gid=null logging=false Apr 28, 2020 1:51:06 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:51:16 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=eb771cc1e4f11232 gid=null logging=false Apr 28, 2020 1:51:16 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:51:26 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=be447f7dff3339ad gid=null logging=false Apr 28, 2020 1:51:26 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:51:36 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=fbcca0c754e72b8f gid=null logging=false Apr 28, 2020 1:51:36 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:51:46 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=6be89e8d7d38cc22 gid=null logging=false Apr 28, 2020 1:51:46 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:51:50 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Running expire() Apr 28, 2020 1:51:56 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=92e30cc88b43f7b0 gid=null logging=false Apr 28, 2020 1:51:56 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:52:06 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=b4bdff39698e5c22 gid=null logging=false Apr 28, 2020 1:52:06 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false Apr 28, 2020 1:52:16 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=61637a55c912c8ea gid=null logging=false Apr 28, 2020 1:52:16 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 3ms. Sticky failure: false Apr 28, 2020 1:52:26 PM org.jitsi.utils.logging2.LoggerImpl log INFO: create_conf, id=93b77f7dead71923 gid=null logging=false Apr 28, 2020 1:52:26 PM org.jitsi.utils.logging2.LoggerImpl log INFO: Performed a successful health check in 2ms. Sticky failure: false I'm hoping that someone has some ideas for taming the RAM consumption.

thanks for checking

Here are the diagnostics. Thank you! tower-diagnostics-20200319-1023.zip