oxideSeven

That did it. Looks like VPN changed their addresses without notice! Thank you.

docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ=[REDACTED] -e HOST_OS="Unraid" -e HOST_HOSTNAME=[REDACTED] -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'=[REDACTED] -e 'VPN_PASS'=[REDACTED] -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'WEBUI_PORT'='8080' -e 'LAN_NETWORK'='10.0.0.0/24' -e 'NAME_SERVERS'='209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' -e 'ADDITIONAL_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -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 '6881:6881/tcp' -p '6881:6881/udp' -p '8080:8080/tcp' -p '8118:8118/tcp' -v '/mnt/user/downloads':'/data':'rw' -v '/mnt/user/games/':'/games':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' 'binhex/arch-qbittorrentvpn' [REDACTED] supervisord.log

I have this same problem. My qbt is no longer reachable. I can't get to the web interface either. something broke?

I can' get mine to launch. I guess it can't set itself up because permissions are denied? Not sure what's going on here, since I can even set full permissions to the folders themselves but it never has permission to do anything... All my other docker containers have had no issues like this. mkdir: cannot create directory '/home/headless/.vnc': Permission denied /dockerstartup/vnc_startup.rc: line 57: /home/headless/.vnc/passwd: No such file or directory chmod: cannot access '/home/headless/.vnc/passwd': No such file or directory /dockerstartup/vnc_startup.rc: line 65: /home/headless/.vnc/config: No such file or directory /dockerstartup/vnc_startup.rc: line 99: /dockerstartup/vnc.log: Permission denied /dockerstartup/vnc_startup.rc: line 127: /dockerstartup/novnc.log: Permission denied /dockerstartup/startup.sh: line 25: kill: (25) - No such process

Fair enough haha! I'll setup a VM for it, since I guess Funcom doesn't even support linux servers anyway. Thanks ich777!

I'm trying to run a Conan Exiles server. When it was fresh with nothing on it, it loaded up fine. So I gave it a reboot, logged in again, then shut down. I then added a few mods. Nothing big like AoC or EEWA. Now I get this after it has loaded tons of stuff. I have a ton of free ram. LogMemory:Warning: Freeing 33554432 bytes from backup pool to handle out of memory. LogMemory:Warning: MemoryStats: AvailablePhysical 19807563776 AvailableVirtual 140737488158719 UsedPhysical 7747080192 PeakUsedPhysical 7750664192 UsedVirtual 7725981696 PeakUsedVirtual 7725981696 00f8:err:sync:RtlpWaitForCriticalSection section 00000000029D2480 "?" wait timed out in thread 00f8, blocked by 0104, retrying (60 sec) 010c:err:sync:RtlpWaitForCriticalSection section 00000000029D2480 "?" wait timed out in thread 010c, blocked by 0104, retrying (60 sec)

I can't change any settings in scrutiny via the webapp. All the options like trying to get manufacturer info is grayed out. It's also not really registering errors in a real way. One of my drives should be failing but scrutiny says it passes.

Satisfactory server can now be run on the early access branch instead of experimental. How would I go about changing that on my end? Just change the appID?

Either way gives the same result, and ranges work fine, no need for separate lines.

I've used mobile, another computer at another house, and I've checked with port detector sites (some people recommended a site that would declare refused if set up correctly instead of timed out. I only ever get timed out)

I'm more concerned about configuration of the docker. I agree that the docker image can't be the issue considering no one else is having a problem. There's clearly an issue somewhere that isn't my network though. That works. It works for an image added before and one added after also needing port forwarding. There is a lot of talk about weird port forwarding issues with bedrock all over the internet though, but nothing I've found was a solution for me unfortunately. If I install the docker image fully default with no other changes to any configs or anything included with it, it should work externally?

I can post something when I get home, but considering the port forwarding for the other server, and like 7 other things all work, I don't think that's the issue. I'll get a screenshot in a few hours.

I tried all 3 methods. UDP, TCP, and both. No difference that I noticed. Never connected.

I've got no external access. I've got this server as x.x.x.61 and port forwarding is set correctly to this address. I can access it on the network, but not outside. I've also got mineOS on x.x.x.60 and port forwarding for that one is also set the same way. These are different ports than the above docker. This one is accessible inside and outside of my network without any problems. Because of that, I'm assuming everything is correctly setup except maybe something with this docker... I did nothing after using apps to install it at default settings.