Corneloues

Just set up my first Windows VM using VirtIO-FS I only appear to be able to access one share at a time. I can access any share I like as long as it's only 1! I changed to order, deleted, re-added, but it appears whatever the last share in the VM config, is the one that the VM sees. I've checked in Device Manager, and I'm seeing a VirtIO FS system device for each share I've added. I've tried uninstalling, re-installing. Adding/removing shares, but no joy. And I have added the dependency for VirtioFsSvc to WinFSP.Launcher, as per SpaceInvaderOne's video. Am I missing something?

Ah bugger... My skills don't stretch that far yet... Maybe easier to use a different VPN client.

Run a Soulseek client over the VPN

Yes, and this is what I have configured. But one of my containers needs a port open to the outside world. So I'm trying to use a PIA port to do that. Can that be done?

So got DelugeVPN back up and running. I'm looking to route other containers through this one, but confused by the definitions of VPN_INPUT_PORTS and VPN_OUTPUT_PORTS... The container I want to pass through, requires an external port opened. If I connect to PIA on the desktop to Berlin, I get a port back consistently, so assume this would be the same port I get when connecting via delugevpn. I am adding the necessary port to VPN_OUTPUT_PORTS. I've tried testing to see if the port is open as per the PIA FAQ's: nc -l {PORT} http://{VPN IP}:{PORT} But I don't get the expected output back. I haven't routed the container yet, just looking to make sure I have a port and it's open. Am I missing something?

FYI... It's now called Appdata Backup - turns out I did have this one installed. Investigating...

Still learning - big lesson here! Installing the Appdata Backup app now. Luckily it's a CA Spotlight app for this month... My issue was trying to use this DelugeVPN to route other apps through and needed to setup additional ports and that's where its all gone Pete Tong! I've been prepared to kill and restore. As long as connect to existing folders, I can minimise the re-work.

I think I've tinkered with one too many docker settings. Is there an easy way to restore without deleting and starting over?

Port forwarding using DelugeVPN as a proxy server on Windows. The proxy is working fine, and I can see that PIA is popping me out nicely in my preferred location. What I'm struggling with is port forwarding from Windows, through this container and out to PIA. I have the following set in the container config: VPN_INPUT_PORTS: 8989,7878,9696,8191,52488,52489,2416 VPN_OUTPUT_PORTS: 52488,52489,2416 The ones in bold are the ones I am expecting to be passed through from the local machine and out to the VPN. The others are what are there by default. Here's my proxy settings: However, the app I am using is reporting remotely that the ports are still closed. Not sure what I've missed or am doing wrong. Any help would be appreciated.

@realies I'm trying to route the Soulseek container via my BinHex-DelugeVPN container using this video as a guide: Couple of things: There is no BASH in the container so I can't curl or netstat for checking ports. These would be really useful Even though I've added port 6080 as a passthrough in the DelugeVPN container, I can't access the noVNC interface I know the container is up and running as it logged my out of Soulseek locally. I just can't get to it.

Any suggestions as to how to route the docker out to a VPN? I think I might need to bypass my ISP controls. I have a VPN installed via BinHex's Deluge-VPN container. I'd like to route my Slsk container over the same VPN.

So after further investigation, there is already a folder called /media in the Soulseek docker. I renamed my folder path in the docker config and now it loads fine. However, all my downloads keep aborting immediately and I can't browse other users. @xthursdayx did you resolve this issue?

@realies so I'm almost there. The container spins up and I can VNC in. The issue is if I deviate from your XML to add a path for my Media which is separate from my downloads. Name: Media Container Path: /data/Media, or /Media Host Path: /mnt/user/Media Default Value: /mnt/user/Media Access Mode: Read Only, Read Only - Shared or Read Only - Slave Adding an additional path prevents noVNC from connecting. The container shows as "up", but I cannot connect. I even tried re-ordering things so that the noVNC port was last, but that made no difference either. As you can see below, the container spins up, but the extra Path prevents me from doing anything with it! docker run -d --name='Soulseek' --net='bridge' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="Soulseek" -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='http://www.slsknet.org/news/sites/default/files/slsk_bird.jpg' -p '49289:57620/tcp' -p '6080:6080/tcp' -v '/mnt/user/appdata/soulseek/':'/data/.SoulseekQt':'rw' -v '/mnt/user/Downloads/Soulseek/':'/data/Soulseek Downloads':'rw' -v '/mnt/user/Media/':'/data/Media':'ro' --restart unless-stopped 'realies/soulseek' 49ac84f5dc97007424e41f9975cd3df82d8f5a2ebf94fa250aee8538def1e165 The command finished successfully! Any ideas? Roy

@realies OK, I can reach the noVNC interface by going straight to :6080. I've just been accustomed to right-click->WebUI... The container works, but if I try and add an additional path for my media, then the container refuses to start. Is there a "right way" to map a media path?