emteedubs

Edit: Narrowed down the issue. For some reason, the error below only happens when running the container on the docker swarm overlay network. When I run it on a docker bridge network, things are fine now. I only wish more containers supported swarm properly. =( I hate to keep asking the same question. But this "write UDP: Operation not permitted (code=1)" error keeps coming back again. I was able to resolve it last time (maybe by luck) by flushing my IPtables on my Ubuntu 18.04 server. It worked for about a week and without me doing much other than maybe turning the containers off and on, it suddenly stopped working again with that error. This time I tried to flush the IPtables, reboot my router, but still no go. I installed a pia-openvpn docker container on the same server as delugevpn to test if it may be a server config issue. But with this other pia-openvpn container, it was able to connect to PIA without this UDP write error using the same credentials. Unfortunately there's nothing more in the log to help me test other ways to figure out the problem. Any thoughts from the experts here? What does that error code really mean?

I don't know what's going on. All of a sudden errors galore. Now there's another error. It reads like a permissions issue, but I checked the permissions and they're fine and match the UID and GID. The /config is binded to a NFS share on my Synology NAS. But again, it worked at one point and suddenly it stopped working. I tried mounting both NFS3 and 4, but the error still persists. Any help or thoughts would be much appreciated. Edit: Problem solved. dos2unix: problems converting file /config/openvpn/CA Toronto.ovpn, 2019-04-12 00:52:39.257950 [info] VPN_ENABLED defined as 'yes', 2019-04-12 00:52:39.062116 [info] PUID defined as '1033', 2019-04-12 00:52:39.034095 [info] System information Linux 6ff0039b60b6 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 GNU/Linux, 2019-04-12 00:52:39.091976 [info] PGID defined as '65541', 2019-04-12 00:52:39.140547 [info] UMASK defined as '000', 2019-04-12 00:52:39.168794 [info] Permissions already set for volume mappings, 2019-04-12 00:52:39.199245 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info', 2019-04-12 00:52:39.226604 [info] DELUGE_WEB_LOG_LEVEL defined as 'info', 2019-04-12 00:52:39.299952 [warn] Unable to chown/chmod /config/openvpn/, assuming SMB mountpoint, 2019-04-12 00:52:39.330785 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Toronto.ovpn, dos2unix: Failed to open temporary output file: Permission denied dos2unix: problems converting file /config/openvpn/CA Toronto.ovpn

hmm, I don't have anything blocking outbound access that I'm aware of. My Ubuntu server (18.04) doesn't have ufw enabled. I don't have any VLANs set up. My router settings haven't been changed (and they shouldn't be blocking any outbound access either). It's odd how this happened all of a sudden. Could this be anything on the PIA front that may have changed? Any other potential culprits?

Everything was working but then randomly I got the following error. I tried using the various OpenVPN config files provided by PIA on their website (UDP, IP, TCP, etc..). When I use the UDP files I get the error below: 2019-04-09 01:37:49,207 DEBG 'start-script' stdout output:, Tue Apr 9 01:37:49 2019 write UDP: Operation not permitted (code=1), , 2019-04-09 01:37:57,318 DEBG 'start-script' stdout output:, Tue Apr 9 01:37:57 2019 write UDP: Operation not permitted (code=1), , 2019-04-09 01:38:13,402 DEBG 'start-script' stdout output:, Tue Apr 9 01:38:13 2019 write UDP: Operation not permitted (code=1), , 2019-04-09 01:38:43,844 DEBG 'start-script' stdout output:, Tue Apr 9 01:38:43 2019 [UNDEF] Inactivity timeout (--ping-restart), restarting, , 2019-04-09 01:38:43,845 DEBG 'start-script' stdout output:, Tue Apr 9 01:38:43 2019 SIGHUP[soft,ping-restart] received, process restarting, , 2019-04-09 01:38:44,109 DEBG 'start-script' stdout output:, Tue Apr 9 01:38:44 2019 WARNING: file 'credentials.conf' is group or others accessible, Tue Apr 9 01:38:44 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018, Tue Apr 9 01:38:44 2019 library versions: OpenSSL 1.1.1a 20 Nov 2018, LZO 2.10, , 2019-04-09 01:38:49,110 DEBG 'start-script' stdout output:, Tue Apr 9 01:38:49 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.25:1198, Tue Apr 9 01:38:49 2019 UDP link local: (not bound), Tue Apr 9 01:38:49 2019 UDP link remote: [AF_INET]172.98.67.25:1198, , 2019-04-09 01:38:49,110 DEBG 'start-script' stdout output:, Tue Apr 9 01:38:49 2019 write UDP: Operation not permitted (code=1), , 2019-04-09 01:38:51,134 DEBG 'start-script' stdout output:, Tue Apr 9 01:38:51 2019 write UDP: Operation not permitted (code=1), , 2019-04-09 01:38:55,181 DEBG 'start-script' stdout output:, Tue Apr 9 01:38:55 2019 write UDP: Operation not permitted (code=1), , 2019-04-09 01:39:03,805 DEBG 'start-script' stdout output:, Tue Apr 9 01:39:03 2019 write UDP: Operation not permitted (code=1), , 2019-04-09 01:39:20,046 DEBG 'start-script' stdout output:, Tue Apr 9 01:39:20 2019 write UDP: Operation not permitted (code=1), , 2019-04-09 01:39:49,276 DEBG 'start-script' stdout output:, Tue Apr 9 01:39:49 2019 [UNDEF] Inactivity timeout (--ping-restart), restarting, , 2019-04-09 01:39:49,280 DEBG 'start-script' stdout output:, Tue Apr 9 01:39:49 2019 SIGHUP[soft,ping-restart] received, process restarting, , 2019-04-09 01:39:49,337 DEBG 'start-script' stdout output:, Tue Apr 9 01:39:49 2019 WARNING: file 'credentials.conf' is group or others accessible, Tue Apr 9 01:39:49 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018, Tue Apr 9 01:39:49 2019 library versions: OpenSSL 1.1.1a 20 Nov 2018, LZO 2.10, , 2019-04-09 01:39:54,337 DEBG 'start-script' stdout output:, Tue Apr 9 01:39:54 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.46:1198, Tue Apr 9 01:39:54 2019 UDP link local: (not bound), Tue Apr 9 01:39:54 2019 UDP link remote: [AF_INET]172.98.67.46:1198, , 2019-04-09 01:39:54,338 DEBG 'start-script' stdout output:, Tue Apr 9 01:39:54 2019 write UDP: Operation not permitted (code=1), My config file worked before, so I don't think that's the cause of an issue.

@binhex Thanks for answering my previous question. I'm encountering another kink with deploying the image through docker swarm vs compose. In my docker-compose designed to be deployed as a swarm stack, I have declared the environment variables similar to what I had done as a docker-compose.yml file. However, I noticed that the resulting container created from this service/stack is not reading the environment variables such as PGID/PUID, etc declared in the swarm stack compose file. As a result, the container encounters permission errors on the volume and crashes. Is it normal that swarm stack compose file env variables are not passed to the created containers? If so, is there a workaround? Thanks in advance. Moving my docker-compose to swarm has been more of a headache than most people say...

@binhex - I am trying to run your container in docker swarm as a service instead of a docker container via docker compose. I understand that your container asks for the "NET_ADMIN" cap to be added on docker-compose files. But as far as I know docker swarm/stack files doesn't support capabilities? Can I run your container without that cap_add parameter as a docker service?

Perfect solution. Everything is good now with nzb-notify. Thank you!

Is there a way to force the container's default "python" to be python2 instead of python3? I'm trying to get the nzb-notify.py script to work for notifications. But the script only supports python2.x. Thanks!