Ding Dong Del

+1 from me - I know most of the time you guys hear about what isn't working. @binhex your work is a key part of my homelab / selfhosted setup, thank you.

+1 to that from me @FoxxMD

Got the same error on first run Was a permissions error for me - fixed it by: - in the docker configuration, switch to advance mode and added the following as extra parameters "--user 99:100" - I also had to change the logs (and content under it) to be owned by nobody.users (99:100) in my set up - assume these were created as root when I installed the app and it tried to run the first time as root. I've not gone any further yet other than to confirm it now starts and I can get to the startup (config) screen. @FoxxMD - thank you for putting this together, looks cool to play with. Allowing users to specify a PUID, and GUID variable to set the user/group they want this to run as seems to be a familiar pattern (at least on the LSIO containers) that will help with this I think. Edit: Quick test using SQLlite was able to run up with the test data ok - FWIW

Awesome @bonienl, worked a treat, thank you! And a general thank you for the great work you and community / limetech do - really awesome product!

Thanks for the heads up @itimpi

Hi all, please sing out if this is the wrong thread and/or more info is needed to troubleshoot. I am following along @ljm42 's writeup (thank you @ljm42). I've come across what I think is an error in page validation logic when attempting to configure a tunnel via UNRAID->Settings->VPN Manager. I have my own domain where the top level is .management When attempting to enter the domain name I get an error (looks like a javascript validation error - including it here in case someone else is searching for the same error message) The error message (chrome) is: "Please match the format requested." "IP Adress or FQDN" The error message (safari) is: "Match the requested format." From what I can tell, page is expecting that the top level domain (TLD) will be 8 characters or less. Some (not very scientific) examples / tests: fred.management - ERROR management.fred - Saves FINE fred.fredfred - Saves FINE fred.fredfredf - ERROR (note one additional character in the TLD) I've tried clearing my browser cache in case I had some js validation file/library cached. Not really sure who to address this to as I don't know who is the author of the Wireguard VPNManager page.

Works a charm, thank you @sparklyballs

I haven't been able to find any more info. Things I have tried. Changed logging to debug, and then trace - have seen the backend disconnection error messages, but nothing captured in either of these files. I have lidarr set up behind an nginx reverse proxy, and get the same error regardless of whether I am going direct via a local addressed, or via the external address. will keep digging

+1 Have tried adding TZ variable, and separately a path to /etc/localtime but still getting the same error. (https://hub.docker.com/r/linuxserver/ombi/ suggests exceptions will be thrown without one set.)

FWIW I have been running the volkion container for months now, and have just switched to the linuxserver.io container (because they rock). I am seeing the same error as reported above, while configuring the application (and wasn't on the volkion container. I assume that the version of the app within the container is not necessarily the same. Off to get some dinner but will dig a bit more and see if I can find some info that is a bit more helpful.

So I’ve tried any number of things and am clearly missing something. Details of latest specific attempt below at the bottom of my post, would appreciate any insight. I’ve tried any number of combinations of things: I have confirmed that port 80 is not blocked by temporarily forwarding external port 80 in my router to my Krusader container and have been able access successfully it via my dynamic domain name. I have tried combinations of IPV4, and IPV6, host networking, bridge networking, I am currently using eth0 networking so that my LE container has a dedicated IPV4 address on my local 192.168.1.0/24 network. In bridged mode, I confirmed there were no port conflicts by using 88, and 440 (respectively). I also used 80, and 443 on the host, after having moved the unraid UI to 81, and 444 respectively - a config I’ve used successfully on other hosts. I’ve added —cap-add=NET_ADMIN as per the linxserver page for the LE container HOST netstat output root@cerberus:~# netstat -tulpn | grep -i listen 80,443 in this instance are the unraid UI’s - don’t think this is relevant given that the container has it’s own dedicated local ip (192.168.1.1 vs. 192.1.68.1.10 for the host - cerberus) tcp 0 0 0.0.0.0:37 0.0.0.0:* LISTEN 1597/inetd tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1643/smbd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1583/rpcbind tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 8610/nginx: master tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 1597/inetd tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1605/sshd tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 1597/inetd tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 8610/nginx: master tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1643/smbd tcp 0 0 0.0.0.0:59331 0.0.0.0:* LISTEN 1587/rpc.statd tcp6 0 0 :::58185 :::* LISTEN 1587/rpc.statd tcp6 0 0 :::139 :::* LISTEN 1643/smbd tcp6 0 0 :::111 :::* LISTEN 1583/rpcbind tcp6 0 0 :::8080 :::* LISTEN 29105/docker-proxy tcp6 0 0 :::80 :::* LISTEN 8610/nginx: master tcp6 0 0 :::22 :::* LISTEN 1605/sshd tcp6 0 0 :::443 :::* LISTEN 8610/nginx: master tcp6 0 0 :::445 :::* LISTEN 1643/smbd I've also attached my letsencrypt log file from the LE container - note it still talks about the bind to :80 using IPV4 failing. letsencrypt.log

@Nem, it was probably equal parts ignorance, and equal parts stubbornness I was playing with / had set up my reverse proxy virtual directories first, before deciding to set up a vpn. Even though if I used a vpn to connect home, I didn't really need anything exposed, I was pretty pleased with myself having set up the virtual dirs, so didn't want to take them down..... Silly I know.... Same thing, I don't use the webgui of ovpn - I always use a vpn client. By the time I realised I could use the port share feature of ovpn I was too lazy to undo my work (even though it probably ended up being more work setting up the stream approach). so I set them both up to be available on 443 because I didn't want to open too many ports on my fw, and because I wanted to be able to get to either from behind e.g. a corporate firewall which I am sure will have outbound 443 open (but probably couldn't rely on much else being open)

@Nem - that's pretty much what I get when using my setup.

I only use duckdns because I only have a dynamic IP address through my ISP (both domain names point to the same IP address). You can use your own Dynamic DNS provider or hostname(s) assuming you can set up the relevant DNS entries.

My bad - I left out a key piece! I am using hostnames to get to either openvpn (via a vpn client), or my nginx reverse proxies. so using the example above, I have two duckdns domains set up (fred, and barney) and if I want to get to sonarr e.g. I use: https://fred.duckdns.org/sonarr when I want to connect to my vpn, I point my vpn client at barney.duckdns.org. I've done it this way on purpose so that both the reverse proxy, and openvpn are listening on 443 externally so that if behind a firewall I can still use my vpn. that is a slightly different use case than you described.