Boo-urns

OK so i'm pulling my hair out here. I'm trying to expose a Wordpress docker to the internet via Nginx Reverse Proxy (NPM). I currently own a domain, use cloudflare, and have a NPM docker handling the proxying. For example, currently have mydomain.com going to overseerr (serverip:5055), and nextcloud.mydomain.com going to nextcloud (serverip:444). Router fwds port 443 to npm. I have 'force SSL' on cloudflare enabled, so haven't even opened port 80. Working fine, no problem. Have used the ibracorp tutorial for this process here. Decided to try and host a site using Wordpress (complete noob with wordpress btw), set it up the same as I had with nextcloud using these steps: Cloudflare: add CNAME 'wp' NPM: add wp.mydomain.com to docker container webui (i'm using cloudflare SSL certs) Not working! I'm just getting a timeout when attempting to access wp.mydomain.com. Via LAN accessing 192.168.1.4:8282 shows the WP test page perfectly, but no idea why this isn't working via proxy. I've tried recreating my SSL certificates, forwarding to a different docker (heimdall for example), with same result. I'm not sure what i'm doing wrong, particularly because I already have 2 working proxies, but if anyone could point me in the right direction i'd be forever grateful. TIA

Hey mate, did you end up getting anywhere with this? I'm trying to get my non-Unifi cams working with my UDM-Pro and this seems perfect. Can't quite figure out the docker template though, although the docker is here if someone can help.

It resolves to the correct IP. I just have it set to my DDNS address, which resolves to my public IP. I have the static route set, host access enabled and Use NAT=No, however cannot access custom networks. These being other VLANs, DelugeVPN docker (which is set to bridge network), my CCTV VLAN. All of these I can access when connected to my LAN normally.

Attached. Seems right, but isn't working. So I need to set up firewall rules also?

Greeting again. Can anyone confirm this is the correct Static Route I need to set in a Unifi router? I still cannot access custom networks from my WG client. Normal LAN is fine.

Yeah I've reinstalled the LibreELEC drivers and it's recognised again. My system is a Ryzen system (R7 1700) and I did upgrade the motherboard about 2 months ago. I do remember an IOMMU setting in the BIOS. So that should be turned OFF?

dmesg attached. modprobe returned: modprobe: FATAL: Module cx23887 not found in directory /lib/modules/5.10.28-Unraid TBS drivers dmesg output.txt

I've deleted the plugin, reinstalled, rebooted, selected the TBS-OS drivers and rebooted, and my card is not recognised at all. Do I need to do something specific to get the TBS drivers to work? Card is still listed however in 'lspci -v' output: 0d:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04) Subsystem: Hauppauge computer works Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb Flags: bus master, fast devsel, latency 0, IRQ 11, IOMMU group 14 Memory at fc400000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] Power Management version 3 Capabilities: [90] Vital Product Data Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Advanced Error Reporting Capabilities: [200] Virtual Channel 0e:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04) Subsystem: Hauppauge computer works Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb Flags: bus master, fast devsel, latency 0, IRQ 10, IOMMU group 14 Memory at fc200000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] Power Management version 3 Capabilities: [90] Vital Product Data Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Advanced Error Reporting Capabilities: [200] Virtual Channel

Yep that's my card. I've tried and only the libreelec driver actually recognise my card. I've added the line as above and rebooted but it doesn't seem to have any effect. Some channels play, others don't, but there is a repeating error in the tvheadend docker log: 2021-04-30 16:13:06.752 [WARNING] linuxdvb: Silicon Labs Si2168 #2 : DVB-T #0 - poll TIMEOUT The same channel plays fine when connected to a TV directly. Any other suggestions or logs I can pull?

Yes I'm running the LibreELEC drivers. I tried to eliminate the cable as the fault, by using another cable, however problem persists. Plus plugging the cable directly to a TV plays OTA channels perfectly. Would downgrading Unraid make any difference? What effect would that have? Also, would the DigitalDevices or TBS devices work with my Hauppage card? Is it possible my card itself is being flaky? Sorry for the million questions, I'd really like to resolve this issue. Is there any other troubleshooting I could do?

I've been having issues recently with my TV Tuner. I use a Hauppage QuadHD PCIe card, backend tvheadend, via 'antennas' to Plex (all in dockers). Some channels will not tune while others do, later on they'll be fine and others will fail. Using different tuners (1,2,3 or 4) for the playback sometimes works, sometimes doresn't. I haven't had this specific issue before, and just seems to have started recently (since around the 6.9.1/6.9.2 unraid version releases). dmesg output seems to include the below errors several times, but no idea what they mean. [166371.596864] AMD-Vi: Event logged [IO_PAGE_FAULT device=0e:00.0 domain=0x000f address=0xbd7ed1c8 flags=0x0000] [166371.632766] cx23885: cx23885[1]: mpeg risc op code error Like I said, I haven't had these errors before that i'm aware of, but could be it due to updated drivers? Can I roll back? tvheadend throws lots of errors in the log too, including "invalid checksum", "continuity counter error" and "transport errors" when it doesn't play. This is really driving me nuts, and the WAF of my network TV system is dropping significantly each day this keeps failing. Any help would be greatly appreciated. dmesg output.txt lspci-v output.txt

I had these settings sorted already, including the static route. I've added the simplified AllowedIPs subnet on the client with no effect. Below is the static route set. Does anything glaring obvious stand out that i've done incorrectly? Unraid IP is 192.168.1.4. Unraid settings as follows: Thanks again for your help.

OK so i've done exactly this. I have a LAN connection via WG and can access everything normally, except for VLANS and custom dockers. eg I have a Shinobi docker running on VLAN5 (192.168.5.2) with all CCTV cams as well which timeout on WG. Additionally, DelugeVPN and Jackett (routed through DelugeVPN) are not accessible either. All of the above are accessible normally via this PC (192.168.1.5). Would there be any other specific routing required?

Thanks for the reply. I did notice that they weren't included in the client config after I looked. So I went to start from scratch in Unraid, reconfigured everything IAW the guide and now i'm not even getting a handshake. Edit: NVM, I forgot WG needs to 'do something' to get a handshake. But, even with added 192.168.5.0/24 and the other ranges to the client config, back to square one. Still no access.

G'day Legends, So i've been using OpenVPN built into the router for years and finally looked into Wireguard via Unraid and wow, plugin and usability is awesome. Fantastic write-up also @ljm42. One problem i'm encountering though... I guess I fall into the 'complex networks' category as I have VLANs and some dockers running via custom networks. I've followed the quickstart guide , enabled host access to custom networks, set 'Local network uses NAT' to No and added a static route on the router (FreshTomato). I can connect via my phone fine, but cannot access the dockers on the custom network, or devices on other VLANs like I could if on my LAN Wifi. Do you have any other pearls of wisdom or troubleshooting steps? Edit: for clarity, I can access everything else on my LAN fine

+1 on this error. Plex sees the TVHproxy tuner, but "There was a problem getting the channels for your device" when you try to scan. Exact same error log in tvhproxy too. @Stealth1081 Did you end up finding a fix for this?

I have the same problem. I recently changed to an ISP that uses CGNAT, so I can no longer port forward or reverse proxy. Zerotier's interface looks like it could work for me, however after starting the docker, I can not access my unraid webui locally (on 192.168.1.4). I can remotely via Zerotier but nothing locally. Anyone have a solution?

With Unraid assigned IP of 192.168.4.2 on VLAN4 (in unraid network settings), I cannot ping it from the router, or any other devices on VLAN4. Although a docker on VLAN4 does come up in the device list. I believe I do have the switch set up correctly, the router's port 3 goes to the port 1 of the switch, and port 2 of the switch goes to unraid.

So by assigning an IP to the VLAN interface, i'm assuming you're talking about within settings > network settings. I was under the impression this needed to be defined as per @bonienl's instruction in the tutorial so the docker see's the VLAN as a network choicer. Regardless, I followed your advice and removed the IP from VLAN4(br0.4). Within the docker settings, i've entered the following for br0.4. I get correct IP assignment upon starting the dockers (and the network shows up as a choice within the docker), however I get the same problem, no internet connection from the dockers/no connection to host. Also I cannot ping the dockers from the router, but i can ping between dockers on the VLAN

I've had the same results on 2 other dockers, running on both the VLAN and bridge. Although DelugeVPN gave a ping result, so I transferred that to the VLAN and got the below results. Can ping other dockers on the VLAN but not the host or gateway. Additionally, the ipp addr are below.

I'm not familiar with Linux syntax in unraid, how do you ping 192.168.4.1?

Thanks @bonienl and @ken-ji for the detailed responses. I believe I have my system set up now...mostly. My test docker is running off br0.4 and the router reports its IP on LAN2/br2/VLAN4. Success! I've set up rules in the router for access between LANs for the time being. Now for the final piece of the puzzle though, the router IP on VLAN4 is now 192.168.4.1 (192.168.1.1 on br0), I put that in the gateway IP in unraid for br0.4. The docker has no internet connection. Using Sonarr as an example, i get "no route to host" errors in the log. Is there something I need to do specifically to allow internet access to the br0.4 VLAN? I've tried setting the gateway to both 192.168.4.1 and 1.1.

@bonienl one last question: I'm trying to configure my router, however i'm having trouble trying to find the appropriate options in the webui. As mentioned previously, i'm using a Netgear R7000 running AdvancedTomato firmware. There's network and VLAN menus but i'm not sure about assigning certain networks to a VLAN ID. I've set up port 3 (which is connected to the switch with unraid), as a tagged VLAN4 port. Is this correct? Although further advanced options as per your tutorial aren't available under VLAN. I'm sure the option is available somewhere, the verbiage is probably just different, and nestled in another section somewhere. Would you have any idea how to set this up, or similar setup instructions elsewhere?

Yeah my router is at one end of the house, and the AP is at the other, so that wouldn't work ha. I went out and bought a TL-SG108E and now have it connected directly to the router, with unraid, AP and others connected to the switch. I'll have a crack tomorrow at setting up the VLANs in the switch and router. I've been dabbling deeper and deeper into the networking rabbithole lately, and advice like yours is priceless. Cheers.