xthursdayx

Yeah this is exactly the issue. I set up a Windows VM and installed Roon on it, but then found out that my CPU can't do VT-d and so can't pass through the sound. I've looked into replacing the motherboard and CPU with one that can handle VT-d, but in order to do that it looks like I'll need to spend around $700 (CAD) that I don't have at the moment. This is partially because my server case can only accommodate mini-ITX boards - (I was thinking of this combo http://ark.intel.com/products/75052/Intel-Xeon-Processor-E3-1220-v3-8M-Cache-3_10-GHz + http://www.asrockrack.com/general/productdetail.asp?Model=E3C226D2I#Specifications). Do you guys have any advice for integrating the audio drivers into the unraid kernel..? Again, this isn't something that I really know anything about.

Hi all, I'm having an issue that I'm hoping someone might be able to help me with. Here is the situation. I am using an ASRock C2750D4II motherboard with an Intel Avoton (Atom) C2750 CPU (http://www.asrockrack.com/general/productdetail.asp?Model=C2750D4II), and recently installed an ASUS Xonar DX PCIe soundcard. I am also running Roon (https://roonlabs.com/) in a modified Ubuntu docker to manage and play my music, but my goal is to be able to play music directly from my server through the Xonar soundcard. However as it stands now Roon doesn't recognize the soundcard as an available audio device. Does anyone know how I can install the drivers for this soundcard in Unraid, and then make my Roon docker recognize the soundcard and pass the audio through? Or alternatively how I can install the drivers inside of the docker container itself (if this is even a possibility). I'm a total noob to this kind of thing, so any advice or suggestions would be very much appreciated. thanks!

Crap, I was afraid that might be the case. Do you have any idea how I could install the driver in the docker? I don't really even know how to begin doing that...

Hi all, I wasn't sure if I should post this here or in the KVM section. Sorry for the long and convoluted post, but I've spent the last couple of hours trying to figure this out with no luck. Any suggestions or advice would really be appreciated! Thanks. Here is the situation. I am using an ASRock C2750D4II motherboard with an Intel Avoton (Atom) C2750 CPU (http://www.asrockrack.com/general/productdetail.asp?Model=C2750D4II). I am also running Roon (https://roonlabs.com/) in a modified Ubuntu docker to manage and play my music. I would like to be able to play music directly (via Roon) from my server by sending it out digitally (via TOSLINK optical or coaxial) to my DAC where it will be decoded and transferred as an analog signal to my amplifier. I thought I could accomplish this by installing an ASUS Xonar DX PCIe sound card which has a coax digital output. However my Roon docker doesn't recognize the sound card as a local audio device. When I check my PCI devices in Tools > 'system devices' I see this: 00:00.0 Host bridge: Intel Corporation Atom processor C2000 SoC Transaction Router (rev 02) 00:01.0 PCI bridge: Intel Corporation Atom processor C2000 PCIe Root Port 1 (rev 02) 00:03.0 PCI bridge: Intel Corporation Atom processor C2000 PCIe Root Port 3 (rev 02) 00:04.0 PCI bridge: Intel Corporation Atom processor C2000 PCIe Root Port 4 (rev 02) 00:0e.0 Host bridge: Intel Corporation Atom processor C2000 RAS (rev 02) 00:0f.0 IOMMU: Intel Corporation Atom processor C2000 RCEC (rev 02) 00:13.0 System peripheral: Intel Corporation Atom processor C2000 SMBus 2.0 (rev 02) 00:16.0 USB controller: Intel Corporation Atom processor C2000 USB Enhanced Host Controller (rev 02) 00:17.0 SATA controller: Intel Corporation Atom processor C2000 AHCI SATA2 Controller (rev 02) 00:18.0 SATA controller: Intel Corporation Atom processor C2000 AHCI SATA3 Controller (rev 02) 00:1f.0 ISA bridge: Intel Corporation Atom processor C2000 PCU (rev 02) 00:1f.3 SMBus: Intel Corporation Atom processor C2000 PCU SMBus (rev 02) 01:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa) 02:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] 03:00.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) 04:01.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) 04:05.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) 04:07.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) 04:09.0 PCI bridge: PLX Technology, Inc. PEX 8608 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch (rev ba) 05:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11) 06:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 02) 07:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 21) 08:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) 09:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) 0a:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11) The Asus soundcard is not listed, but when I downloaded my config files from Tools > Diagnostics, the lspci.txt file in the system folder lists this entry: 02:04.0 Multimedia audio controller [0401]: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] [13f6:8788] Subsystem: ASUSTeK Computer Inc. Virtuoso 100 (Xonar DX) [1043:8275] Because the sound card isn't recognized in the Roon docker directly I decided to install a Windows VM and enabled PCIe ACS Override, and then installed Roon Server inside this VM. However when I look at the Windows Device manager I can't see the sound card. Here is my VM XML: <domain type='kvm' id='1'> <name>Windows 10 x86 VM</name> <uuid>91be1eb1-3ce5-58bb-657f-8ab5ca490376</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Domains/Windows 10 x86 VM/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/WIN10.X86.8x1.ENU.May2016.ISO'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.102.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:fb:83:45'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 10 x86 VM.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> So, I'm not sure what the issue is. When I check Tools > System Devices the IOMMU Groups entry says: Warning: Your system has booted with the PCIe ACS Override setting enabled. The below list doesn't not reflect the way IOMMU would naturally group devices. To see natural IOMMU groups for your hardware, go to the VM Settings page and set the PCIe ACS Override setting to No. No IOMMU Groups When I check my server info HVM is Enabled, but IOMMU is disabled. I checked the Intel page, and it says that my CPU is VT-x enabled (http://ark.intel.com/products/77987/Intel-Atom-Processor-C2750-4M-Cache-2_40-GHz), but from what I can tell the ASRock BIOS doesn't have an option to enable IOMMU. I checked this sticky post in the KVM forum: https://lime-technology.com/forum/index.php?topic=38259.0 , and this post in the KVM forum: https://lime-technology.com/forum/index.php?topic=44591.0 which both seem to indicate that I should add this code to my VM XML but I'm not sure if that will solve the problem as I don't have any IOMMU groups listed: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x02' function='0x1'/> </source> </hostdev> Again, at the end of the day what I want to accomplish is being able to play audio directly from the server through my PCIe sound card, either from a docker like Roon or Plex or from a Windows VM. Any ideas how I can accomplish this with my setup?

Did you ever figure out how to do this? I'm running Roon in a docker and would love to pass my audio out through my PCIe sound card. Thanks!

Hi all, I've had this docker set up and working well for a couple of months now, but due to a change in my network infrastructure I had to reinstall OpenVPN-AS. Now that I've done this I am able to connect to the VPN and it seems to be working - for example if I join the VPN on my iPad I am able to see my Plex Server in the Plex app and play media. However for some reason I am unable to connect to my server management webUI... When I go to my normal internal IP address it will never load. Any idea why this would happen? As I said, i am able to connect to the VPN and do other tasks, but not manage the server, which is one of the key reasons I wanted to install OpenVPN-AS to begin with.

The strange thing is that the only log I see changing sizes when I use this command is the log from Mylar. Yet the only way I am able to reduce my docker image usage is by resetting crash plan...

I've already tried this, but Crashplan's logs aren't particularly large. And as I said in my post there don't seem to be any logs internal to crashplan that I can clear or limit the size of.

So, I'm having the same problem (docker image filling up), and unfortunately CAdvisor hasn't been any help as my container sizes don't seem to be changing. I have however been able to isolate the source of the problem by going through all my containers that seem to have high memory usage and larger container sizes and updating them (edit > save) and waiting until my docker utilization goes back to normal. It seems that my problem is coming from gfjardim's Crashplan docker. I am using crashplan to backup my entire server (unlimited account), so it is moving a lot of data, but it doesn't seem to keep logs, so I'm unsure what could be causing the docker image to fill up. Any ideas?

Hey sorry, I've been away from my server. It seems to have updated... It says I'm at build 872edd43293aaf65ec98f50071cbbb6835956612 now, and hasn't told me I'm behind on commits. I'll report back if this changes.

That's awesome, I really appreciate it!

I actually was using theirs previously. The reason I switched to yours is because the linuxserver.io build doesn't support the development branch, which has the commit I need to fix my error....

This isn't working for me. I hit the update button when it tells me I'm 34 commits behind, but then nothing happens after the restart and I'm still 34 commits behind (unfortunately I am having a problem with the program that these commits fix - which is the reason I switched to this docker running the development branch to begin with). Is there any way to update manually?

Still have the same problem... Any ideas what I should do?

Yep, this is via https. This is the entire log string I get when I try to load the GUI [2016-04-20 10:01:57.007744] _LISTENER == ConnectionFrom(192.168.1.160, 54585) [Allowed] [2016-04-20 10:01:57.007801] There are [0] clients from [192.168.1.160] [2016-04-20 10:01:57.040803] _LISTENER == ConnectionFrom(192.168.1.160, 54586) [Allowed] [2016-04-20 10:01:57.040845] There are [0] clients from [192.168.1.160] [2016-04-20 10:01:57.067630] WebMod::Client == ReachedMaxBuffer() [2016-04-20 10:01:57.067705] Remote IP: 192.168.1.160; discarding session [f46ef5a56ccdbf8553396fc995dcf993f06ca36984d94155847c7b298e6dde1b] [2016-04-20 10:01:57.067765] Auto generated session: [3051ce7f050953494593a56f2302414b33d39aae1175e8814b2301b496788cbb]

bump?

I've installed the docker but everytime I try to access the web GUI I get an ERR_EMPTY_RESPONSE and the ZNC log shows this: [2016-04-16 13:33:31.363483] _LISTENER == ConnectionFrom(192.168.1.160, 56903) [Allowed] [2016-04-16 13:33:31.363524] There are [0] clients from [192.168.1.160] [2016-04-16 13:33:31.384572] WebMod::Client == ReachedMaxBuffer() [2016-04-16 13:33:31.384683] Auto generated session: [0306a53c39224dda8136e4f802c5b5756ea1d2634f367c27bad2d423bd289e8b] Any ideas?

Also I'm assuming this information from my cache drive SMART info might be related: 196 Reallocated event count 0x0032 100 100 000 Old age Always Never 85 197 Current pending sector 0x0022 100 100 000 Old age Always Never 4 And this is coming up in my cache's SMART error log: ATA Error Count: 119 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 119 occurred at disk power-on lifetime: 1459 hours (60 days + 19 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 36 9a 02 4a ef Error: UNC 54 sectors at LBA = 0x0f4a029a = 256508570 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 d0 01 4a e0 08 22d+20:04:30.300 READ DMA EXT ea 00 00 00 00 00 a0 08 22d+20:04:30.300 FLUSH CACHE EXT c8 00 80 50 01 4a ef 08 22d+20:04:30.200 READ DMA ca 00 08 c0 00 00 e0 08 22d+20:04:30.200 WRITE DMA c8 00 20 30 01 4a ef 08 22d+20:04:30.200 READ DMA Error 118 occurred at disk power-on lifetime: 1458 hours (60 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 2e 9a 02 4a ef Error: UNC 46 sectors at LBA = 0x0f4a029a = 256508570 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 c8 00 4a e0 08 22d+18:54:13.200 READ DMA EXT c8 00 80 48 00 4a ef 08 22d+18:54:13.200 READ DMA c8 00 20 28 00 4a ef 08 22d+18:54:13.200 READ DMA 35 00 30 d0 a9 3c e0 08 22d+18:54:13.200 WRITE DMA EXT c8 00 08 20 00 4a ef 08 22d+18:54:13.200 READ DMA Error 117 occurred at disk power-on lifetime: 1445 hours (60 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 05 9b 99 a7 e1 Error: UNC 5 sectors at LBA = 0x01a7999b = 27761051 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 98 99 a7 e0 08 22d+05:34:20.100 READ DMA EXT ef 10 02 00 00 00 a0 08 22d+05:34:20.100 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 08 22d+05:34:20.100 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 08 22d+05:34:20.100 IDENTIFY DEVICE ef 03 42 00 00 00 a0 08 22d+05:34:20.100 SET FEATURES [set transfer mode] Error 116 occurred at disk power-on lifetime: 1445 hours (60 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 05 9b 99 a7 e1 Error: UNC 5 sectors at LBA = 0x01a7999b = 27761051 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 98 99 a7 e0 08 22d+05:34:16.300 READ DMA EXT ef 10 02 00 00 00 a0 08 22d+05:34:16.300 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 08 22d+05:34:16.300 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 08 22d+05:34:16.300 IDENTIFY DEVICE ef 03 42 00 00 00 a0 08 22d+05:34:16.300 SET FEATURES [set transfer mode] Error 115 occurred at disk power-on lifetime: 1445 hours (60 days + 5 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 05 9b 99 a7 e1 Error: UNC 5 sectors at LBA = 0x01a7999b = 27761051 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 98 99 a7 e0 08 22d+05:34:12.500 READ DMA EXT ef 10 02 00 00 00 a0 08 22d+05:34:12.500 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 08 22d+05:34:12.500 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 08 22d+05:34:12.500 IDENTIFY DEVICE ef 03 42 00 00 00 a0 08 22d+05:34:12.500 SET FEATURES [set transfer mode]

I've found that I'm getting this series of repeating errors in my server's log. Any idea what is causing it? I have 4 pending sectors and 85 reallocated events (though 0 reallocated sectors) on my cache drive it seems (see my next post for the errors from my cache drive). Is this the cause of the errors in my SysLog? Do I need to swap out my cache? The number of currently pending sectors doesn't seem to be increasing. Apr 12 02:01:20 Tower kernel: ata9.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6 frozen Apr 12 02:01:20 Tower kernel: ata9.00: failed command: WRITE FPDMA QUEUED Apr 12 02:01:20 Tower kernel: ata9.00: cmd 61/08:10:00:a9:8c/00:00:0d:00:00/40 tag 2 ncq 4096 out Apr 12 02:01:20 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 12 02:01:20 Tower kernel: ata9.00: status: { DRDY } Apr 12 02:01:20 Tower kernel: ata9: hard resetting link Apr 12 02:01:20 Tower kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 12 02:01:20 Tower kernel: ata9.00: configured for UDMA/133 Apr 12 02:01:20 Tower kernel: ata9.00: device reported invalid CHS sector 0 Apr 12 02:01:20 Tower kernel: ata9: EH complete

Hi Aptalca, I was wondering if you know how I might run multiple Calibre Content Server instances from you RDP-Calibre docker? The reason that I want to do this is that I have multiple libraries and I would like to serve all of them (since it doesn't seem that there is a way for server clients to switch between libraries). I've read a bit about it and seems like it's possible, but I'm not sure how to implement this via the docker. See the forum post here for more information -> http://www.mobileread.com/forums/showthread.php?t=150814 Thanks!

Thanks for this, really amazing explanation! Neither the router nor the modem are mine (I share them with my landlord), so while I have admin access, I don't have the ability to change the set up too much. This is super illuminating though. Cheers!

Yeah, sorry, just updated my last post. I've been able to work around this by forwarding the same port through both my router and the new modem. Thanks!

Yeah, the redirect is working now. And I figured out where the timing out problem was coming from (as you suspected it wasn't the No-IP container). The strange thing was that when I tried to connect to my No-IP host name after the redirect started working it began directing me to the login screen for the new modem that I got from my ISP, rather that to my router's login screen (or the OpenVPN login screen). If I attempted to connect to the port I forwarded for OpenVPN I would still get a refused connection. As this is a new modem I'm not very familiar with it, but I set my router to have a static IP, and forwarded the same port on the modem to the port on my router that I had previously forwarded to my OpenVPN. I am now able to connect to the VPN from my phone.

Just added the ddclient docker to see if it will make any difference from the No-IP docker. Fingers crossed.

Ok... sorry to be a bit slow, I realized this just after my last post and found the No-IP docker. I've installed that docker and linked it to my No-IP host redirect. However I'm still getting a connection time-out when I try to connect over 3G with my phone. Here is the log: 2016-03-06 19:47:16 ----- OpenVPN Start ----- OpenVPN core 3.0 ios arm64 64-bit 2016-03-06 19:47:16 UNUSED OPTIONS 0 [setenv] [FORWARD_COMPATIBLE] [1] 3 [nobind] 10 [sndbuf] [100000] 11 [rcvbuf] [100000] 14 [verb] [3] 15 [setenv] [PUSH_PEER_INFO] 23 [CLI_PREF_ALLOW_WEB_IMPORT] [True] 24 [CLI_PREF_ENABLE_CONNECT] [True] 25 [CLI_PREF_ENABLE__PROXY] [True] 26 [WSHOST] [vulf.ddns.net:943] 27 [WEB_CA_BUNDLE] [-----BEGIN CERTIFICATE----- MIIDBDCCAeygAwIBAgIEVtfU8zANBgkqhkiG...] 28 [iS_OPENVPN_WEB_CA] [1] 29 [ORGANIZATION] [OpenVPN Technologies, Inc.] 2016-03-06 19:47:16 LZO-ASYM init swap=0 asym=1 2016-03-06 19:47:16 Comp-stub init swap=0 2016-03-06 19:47:16 EVENT: RESOLVE 2016-03-06 19:47:17 Contacting 99.233.114.93:1194 via UDP 2016-03-06 19:47:17 EVENT: WAIT 2016-03-06 19:47:17 SetTunnelSocket returned 1 2016-03-06 19:47:17 Connecting to vulf.ddns.net:1194 (99.233.114.93) via UDPv4 2016-03-06 19:47:26 Server poll timeout, trying next remote entry... 2016-03-06 19:47:26 EVENT: RECONNECTING 2016-03-06 19:47:26 LZO-ASYM init swap=0 asym=1 2016-03-06 19:47:26 Comp-stub init swap=0 2016-03-06 19:47:26 EVENT: RESOLVE 2016-03-06 19:47:26 Contacting 99.233.114.93:1194 via UDP 2016-03-06 19:47:26 EVENT: WAIT 2016-03-06 19:47:26 SetTunnelSocket returned 1 2016-03-06 19:47:26 Connecting to vulf.ddns.net:1194 (99.233.114.93) via UDPv4 2016-03-06 19:47:36 Server poll timeout, trying next remote entry... 2016-03-06 19:47:36 EVENT: RECONNECTING 2016-03-06 19:47:36 LZO-ASYM init swap=0 asym=1 2016-03-06 19:47:36 Comp-stub init swap=0 2016-03-06 19:47:36 EVENT: RESOLVE 2016-03-06 19:47:36 Contacting 99.233.114.93:1194 via UDP 2016-03-06 19:47:36 EVENT: WAIT 2016-03-06 19:47:36 SetTunnelSocket returned 1 2016-03-06 19:47:36 Connecting to vulf.ddns.net:1194 (99.233.114.93) via UDPv4 2016-03-06 19:47:46 Server poll timeout, trying next remote entry... 2016-03-06 19:47:46 EVENT: RECONNECTING 2016-03-06 19:47:46 LZO-ASYM init swap=0 asym=1 2016-03-06 19:47:46 Comp-stub init swap=0 2016-03-06 19:47:46 EVENT: RESOLVE 2016-03-06 19:47:46 Contacting 99.233.114.93:1194 via UDP 2016-03-06 19:47:46 EVENT: WAIT 2016-03-06 19:47:46 SetTunnelSocket returned 1 2016-03-06 19:47:46 Connecting to vulf.ddns.net:1194 (99.233.114.93) via UDPv4 2016-03-06 19:47:56 Server poll timeout, trying next remote entry... 2016-03-06 19:47:56 EVENT: RECONNECTING 2016-03-06 19:47:56 LZO-ASYM init swap=0 asym=1 2016-03-06 19:47:56 Comp-stub init swap=0 2016-03-06 19:47:56 EVENT: RESOLVE 2016-03-06 19:47:56 Contacting 99.233.114.93:1194 via UDP 2016-03-06 19:47:56 EVENT: WAIT 2016-03-06 19:47:56 SetTunnelSocket returned 1 2016-03-06 19:47:56 Connecting to vulf.ddns.net:1194 (99.233.114.93) via UDPv4 2016-03-06 19:48:06 Server poll timeout, trying next remote entry... 2016-03-06 19:48:06 EVENT: RECONNECTING 2016-03-06 19:48:06 LZO-ASYM init swap=0 asym=1 2016-03-06 19:48:06 Comp-stub init swap=0 2016-03-06 19:48:06 EVENT: RESOLVE 2016-03-06 19:48:07 Contacting 99.233.114.93:1194 via UDP 2016-03-06 19:48:07 EVENT: WAIT 2016-03-06 19:48:07 SetTunnelSocket returned 1 2016-03-06 19:48:07 Connecting to vulf.ddns.net:1194 (99.233.114.93) via UDPv4 2016-03-06 19:48:16 EVENT: CONNECTION_TIMEOUT [ERR] 2016-03-06 19:48:16 EVENT: DISCONNECTED 2016-03-06 19:48:16 Raw stats on disconnect: BYTES_OUT : 1260 PACKETS_OUT : 30 CONNECTION_TIMEOUT : 1 N_RECONNECT : 5 2016-03-06 19:48:16 Performance stats on disconnect: CPU usage (microseconds): 47162 Network bytes per CPU second: 26716 Tunnel bytes per CPU second: 0 2016-03-06 19:48:16 EVENT: DISCONNECT_PENDING 2016-03-06 19:48:16 ----- OpenVPN Stop -----