JBanner

Ok this is all sorted now. Replaced the Wireguard Config, and added the tailscale net address to the allowed LAN's and updated to latest.

Thanks for the reply.... I've already tried toggling a few different things off , applying or reinstalling and still get the same... I've tried toggling the vpn off and on and tried several network types. I have reset everything back to how it was for now, but still can't get it to work.

I am also having issues after upgrading to unraid 7.2.5. After the update I could not start the container, similar to above "docker: Error response from daemon: invalid port specification: "0/tcp"" I tried to remove the container and reinstall using "Previously Apps", and tried using "Add Container", both methods end with: (Username and Password have been obscured) docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --pids-limit 2048 --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='OBSCURED' -e 'VPN_PASS'='OBSCURED' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'ENABLE_SOCKS'='no' -e 'SOCKS_USER'='admin' -e 'SOCKS_PASS'='socks' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'WEBUI_PORT'='8080' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'VPN_OPTIONS'='' -e 'ENABLE_STARTUP_SCRIPTS'='no' -e 'USERSPACE_WIREGUARD'='no' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' -l net.unraid.docker.icon=''https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png -p '8080:8080/tcp' -p '8118:8118/tcp' -p '9118:9118/tcp' -p '58946:000/tcp' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' -v '/mnt/user/data':'/data':'rw' -v '/mnt/user/binhex-shared/':'/shared':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' docker: Error response from daemon: invalid port specification: "0/tcp" Run 'docker run --help' for more information The command failed. I''m not really sure what to try next...

This was the solution. Thank you.

OK I've Ordered a usb a to usb a cable - should be here tomorrow

Hi, Historically I used an APC BackUPS 950, plugged in Via USB and it worked perfectly with the UPS Settings in Unraid.... Move on a few years and upgraded the hardware that UPS was overloading, so removed it. I have just picked up an APC SmartUPS 2200 Model SMT2200IC and cannot get it to talk. The UPS has several connectors on it, 1 RJ45 labelled as a "smartConnect" Ethernet port 1 RJ50 (maybe RJ45) Serial connector 1 USB "A" connector - Yes the one that is usually on the PC (Host) not the peripheral UPS Boots up and connects to the internet and downloaded it's latest firmware, i can ping it etc. I have a Cable that is a RJ50 to USB cable that is an APC cable (APC Ref AP9827) Plugged into a USB port on the Server. Running through the config on the UPS, it has ModBus Turned on for both serial and USB ports In the UPS Settings I've tried a LOT of different setting, UPS CAble Set As USB, Set as Ether, I've tried UPS Type as USN and ModBus, etc But I just cant get the connection to the UPS working, it constantly says Connection Lost. I have done all this based on some of the other threads on the forum but I'm tearing my hair out... - I did try NUT but I couldn't get any joy on that either.... A network card is available for this UPS but I don't want to spend more if that won't work either. - Or maybe I get a USB a to USB A cable and try that? So really not sure which way to go... The device does not show up in the system devices under USB. Diagnostics attached - Produced while the UPS was plugged in Via USB to the RJ50 cable in the Serial connector on the UPS. Looking for any suggestions. tower-diagnostics-20251205-1418.zip

Yes it is my desktop. Not sure why it would timeout though?

I'm getting random crashes, the Web UI becomes unresponsive, but docker containers continue to run. I can SSH in but nothing much works. Have rebooted and rebuilding parity, any ideas what is causing it? Diagnostics and Syslog attached. syslog-previous tower-diagnostics-20250812-2337.zip

Ok Problem Solved.... This was the solution. After looking up a few more posts, there was one that said to delete/rename network.cnf - So I added ".BAK" to the end, and did a restart. Machine got an address via DNS and bingo it worked.... only thing is I want the static address that I had assigned to it... and Lightbulb moment, I remembered I have a load baqlancing router, and had allocated a static IP to the old server, and that was the IP I wanted to use.... so the new machine was being blocked. Simple solution was to bind the new MAC address to the IP I wanted the new Server to have and BINGO it worked.

I have changed the server PC and cannot get it to see the internet. - No ping to 8.8.8.8 - it does work on my local network. Have tried several things but not sure where to look next. Ip Address is static as it was before DNS is set to 208.67.222.222 secondary 8.8.8.8 - However I can't even ping these from the console.... Diagnostics attached.

With Sorting the other Corruption issues that occurred, this has gone away.... Thank Goodness I don't believe I have lost much if anything at all. I have a backup on unraid connect, it has saved my bacon in the past! Thanks For Your Replies

XFX Check on drive 5 came back with no corruption - Array has started in the new configuration and is rebuilding Parity. Thank you for your help, I'll post again when parity is complete.

I believe it was, I will run another XFX Check on it just in case, before attempting the newconfig later today.

Thanks for your suggestion, but Yes I have done that. I have also tried using a Different PC, so there can be no cached data on that one.... I eliminated the cache possibility. However, some corruption has cropped up on my machine, so this may be related