cardo

I should add this is the primary GPU in my server. I used @SpaceInvaderOne's script to dump the vbios. Is there anything else I can provide that will help find a solution? Any other resources I can check? I've been trying to fix this on my own for the past several days and I'm no closer than I was.

Still trying to find some guidance here. I tried making the 3060 a secondary GPU and installing the NVidia drivers over VNC but that made no difference. I even dumped the vbios and I'm still seeing the issue above? As I mentioned, Windows 10 is a breeze. I don't even need the vbios rom.

Hi All, I'm attempting to pass through my RTX 3060 GPU to an Ubuntu Desktop 22.04 LTS VM without success. My workflow is as follows: 1. Install Ubuntu 2. Install openssh-server 3. Verify connection to ssh 4. Shutdown VM via NoVNC 5. Edit VM template to passthrough the 3060's video and audio 6. Start VM The VM's IP will appear on my router after it starts, but I cannot connect via SSH or even ping the VM. Here is my VM XML: https://pastebin.com/ffJvfxny I see the following in my diagnostics log: Dec 9 07:39:47 MojoRyzen avahi-daemon[6043]: Registering new address record for on vnet8.*. Dec 9 07:43:28 MojoRyzen kernel: vfio-pci 0000:0f:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 Dec 9 07:43:28 MojoRyzen kernel: vfio-pci 0000:0f:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Dec 9 07:43:28 MojoRyzen kernel: vfio-pci 0000:0f:00.0: vfio_ecap_init: hiding ecap 0x26@0xc1c Dec 9 07:43:28 MojoRyzen kernel: vfio-pci 0000:0f:00.0: vfio_ecap_init: hiding ecap 0x27@0xd00 Dec 9 07:43:28 MojoRyzen kernel: vfio-pci 0000:0f:00.0: vfio_ecap_init: hiding ecap 0x25@0xe00 Dec 9 07:43:28 MojoRyzen kernel: vfio-pci 0000:0f:00.0: No more image in the PCI ROM Any idea what I'm missing? With my Windows 10 VM's it works perfectly. TIA!

Hi All, I am setting up an Ubuntu VM for the express purpose of using Stable Diffusion in a smaller footprint than Windows. As you know, once you pass through a GPU, the option to connect via the built in VNC disappears. I would prefer to use Ubuntu Server since it doesn't have the overhead of a GUI, but when I pass through my GPU, the VM will start, but I can no longer SSH into the VM. So, with that said I'm looking to get the desktop version of Ubuntu to allow a remote connection over a GUI interface. Are there any recommendations or tutorials out there on how to set this up? I've been searching without much success. Thanks in advance!

It could be circumstantial, but going to Mullvad's site, deleting the port forward I had and downloading the Wireguard config files again resolved the issue for both containers.

Do you think the recent port forwarding change by Mullvad could cause this issue? I had port forwarding before I recreated the containers (switched from unassigned devices to multiple cache pools) and when I downloaded the wireguard config files again, it still is including the port forward which now they've taken away. I may be way off, but that's the only change on their end that I'm aware of.

Yeah, restarting. broke the qbittorrent container as well. As a test I dropped all of the DNS servers except for cloudflare's 1.1.1.1 and 1.0.0.1 and it still fails, but I can ping each from an unRAID shell.

Did you ever find a solution to this issue? I am experiencing the same issue here using Mullvad and Wireguard. The strange thing is that the binhex-qbittorrentvpn docker works perfectly even using the same server. Any insight on what could cause this @binhex? The supervisord.log just shows the dns errors, the container starts without a hitch.

Change to develop branch and it will keep your settings.

Excellent, thanks! That worked for me as well.

Did you get this figured out? If I switch to linuxserver/sonarr:latest or linuxserver/sonarr, It loses all of my settings. I am running the preview like you as well.

That makes sense now. I was able to use Steam to directly connect to my server's public IP even when connected from my gaming VM via VPN. My server is just not showing up in the community browser in Valheim which I suppose at this point could just be early access growing pains. Thanks for your help!

I am also having the same problem trying to port forward through my Unifi Dream Machine Pro. Plex forwards fine, but testing the Valheim UDP ports fails on that site fails as well.

I was having the same issue and enabling Privoxy worked for me too. Never had to have this enabled until the docker pull from today.

This is working perfectly thanks. The only odd thing for me is I can’t get faster than 30MB/sec using the next gen servers, even one that’s not too far from my location and the port is reporting open by ruTorrent as well. Same torrent without port forwarding working gets at least 82MB/sec on my gigabit connection using Mullvad. I wonder if others with fast connections are seeing similar results.

Same here after following binhex’s recommendations. I’m using Mullvad.

Thanks for that. I was able to get your Deluge docker up to 62-64MB/sec by unchecking incoming and outgoing UDP, but it’s still roughly 20 fewer than rTorrent using Mullvad as the provider with. port forwarding not working. I’m curious to see if PIA is faster once you get done testing next gen and update the rTorrent container.

I’m seeing slow performance as well, but I suspect it’s on the PIA side. Strangely, binhex’s rTorrent VPN docker using Mullvad without forwarding working I can get 82-85MB/sec on my gigabit connection, but the same torrent with next gen in DelugeVPN won’t get above 22-24MB/sec and that’s using the high performance options with the ItConfig plugin.

And when you check the port status in rTorrent’s GUI, it shows the forwarded port as open? I’m set up exactly the same as you other than I’m using a different VPN location and I get the exclamation mark in the status bar with the message xxxxx: Port is closed. Where xxxxx is the forwarded port.

So, the port status shows open in the status bar?

Can you provide more information about how you configured the container/router, because I set this up 4-5 days ago and it is still failing for me. Here were my steps: 1. Set up the port forward on Mullvad. 2. set up a port forwarding rule on my router from anywhere to my private IP and port I’ve set up on Mullvad. It is set for both TCP/UDP. 3. Created two port entries in the container, one for UDP and one for TCP and specified the port on Mullvad and my router’s port forward rule. 4. Edited the .torrent.rc file and specified the port like this: network.port_range.set = xxxx-xxxx where xxxx is the port number. 5. When starting the container and going to Settings > Connection > Port used for income connection shows my port. Yet the status still shows the exclamation mark with the port being closed.

I’ve also manually forwarded the port in my firewall and added two port entries in the container one for TCP and another for UDP and it still fails both from rTorrent’s port status as well as the external tester.

Has anyone who switched to Mullvad get port forwarding to work? I know the strict port forward is ignored if don’t have PIA, but I’ve added a port forward for my account over at Mullvad and have gone into ruTorrent front end and choose settings > connection > port used for incoming connections and set it to the port and even tried 1234-1234 where 1234 is the real port number. It doesn’t do anything for me. The status icon at the bottom is still a red exclamation mark. I have a gigabit connection and without port forwarding I get about 60MB/sec on a well seeded torrent, I used to get as high as 85MB/sec with PIA and port forwarding enabled. EDIT: I should add I copied the rtorrent.rc file to .rtorrent.rc with the ports specified from Mullvad and the port status still is red.

I’m in the U.S. and Mullvad was significantly slower for me than PIA. That’s why I switched back. I ended up getting 3 years of service too. It really pisses me off too because without the port forwarding my speed is cut significantly.

Thank you very much!