AnhedonicNeko

Members
  • Posts

    6
  • Joined

  • Last visited

About AnhedonicNeko

  • Birthday April 9

Converted

  • Gender
    Male

AnhedonicNeko's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Hmm, not from Twitch, but if I can figure out how to share the twitch folder to UnRaid maybe I can change the docker's serverfiles parameter. I'm not really sure how to do that though since my Windows install is on a native NVMe drive being stubbed to the VM instead of using a Vdisk. Edit: Well, turns out the twitch button is just a quick way to download the files, it isn't actually server management capability. So I would still have to do it the manual way anyway. No need then really to link the server files since it will take just as long anyway.
  2. Turned out to be the router, I bought a real router instead of the ISP one and it works fine now. Now I just need to come up with a good way to update the modpack on the server side, though unless there is some miraculous curse integration option somewhere, I'm probably just going to have to manually update files the old way before Twitch supported server packs.
  3. Does which controller matter? I have several of them, and I'm not sure which one the UnRaid flash drive is on. I'll try it here in a bit. The Type-C port on the GPU is already passed through (as I needed to for the purpose of passing through the GPU as a whole) Edit: I tried each USB controller independently and also the ones grouped together to no avail. Only one of them being passed actually let me boot the VM and didn't allow for plug and play (I tried multiple USB ports to see if it was only controlling some of them). I think it was actually the internal connectors that allowed that. The other configurations just caused either the VM to seize up UnRaid or otherwise make it so I needed to reboot UnRaid, so I'm assuming they either need additional configuration or are tied to something else that isn't/can't be forwarded properly. Incidentally, my WiFi was able to be passed through separate from the Ethernet, but I can't seem to identify which device is the Bluetooth. The device I previously thought was the Bluetooth (a device listed in USB) disappears when I forward the WiFi (listed in PCI), so I'm guessing it was the Antenna that attaches to the WiFi?. Regardless, still no touch/pen input on my tablet though even on the USB controller that was able to be passed through.
  4. I'm trying to get my Wacom Cintiq Pro 16" working in my Windows VM. I have the GPU: EVGA RTX 2080 Super FTW3 Hybrid passed through fully to the VM. For 4k support, I have to use the Type-C connection on the GPU for the tablet. In Baremetal Windows, this works fine and has no issues. However, when I boot it in a VM, it only acts as a screen (no touch functions, pen detection, and the Wacom Tablet program doesn't detect the tablet hooked up). Even if the device is powered on, at boot-up of UnRaid, it doesn't show up as a IOMMU or USB device, so I don't seem to be have an option to pass it through. So my question is, does anyone know how to get this to work through a VM, preferably using the Type-C connector so I can have 4k support? As far as my UnRaid setup goes, this is what I have: Ryzen 9 3900x AsRock x570 Taichi EVGA RTX 2080 Super FTW3 Hybrid Wacom Cintiq Pro 16" NVMe drive stubbed with native Windows Install (so I can boot the same OS either Baremetal or VM on the fly). Incidentally, this device, and a couple others are not ALWAYS hooked up, is there a way to get them to automount and passthrough to an active VM (so that they function like normal plug and play devices on baremetal)? I find it really annoying to have to reboot the VM just because I plugged my headset back in or remove devices that are not hooked up just to get the VM to boot each time.
  5. So that first part worked for changing the port. Thanks for the instruction on that. As for the first problem, after some further testing, I do find it odd that indeed those ports do seem to be being blocked. Previously they worked just fine on baremetal before upgrading things to UnRaid, but even testing again on baremetal and a factory reset of the router did not change anything. So my ISP at some point either did a firmware update that broke port forwarding (tested with other non-upnp apps and same issue) or they are indeed blocking ports now. Unless, my motherboard has some sort of firewall built into it, other than UnRaid, that is the only other recent change to the network.
  6. I am new to unraid and am trying to run a modded MinecraftBasicServer docker, and I have it working locally (I can connect to it via the 192.x.x.x address). However, I have a couple problems, the first is I can't connect to it from my external IP. I do have the port forwarded to the 192.x.x.x port. I don't see any option in the template to change to allow it to connect externally. The second is that changing the port from the default 25565 makes it no longer able to connect regardless. I notice there is a port mapping on the docker tab which shows a 172.x.x.x address, and that port never changes off of 25565 when I change the port. I have changed the port in both the server.properties and on the docker template. The 192.x.x.x shows the port change on the port mapping, but the 172.x.x.x one never changes. I am guessing that this port mapping is also why I am unable to connect externally. I've tried changing from Bridge to Host, all that did was remove the port mapping on the docker tab, it otherwise functions the same as above. As a side note, it shows the server pop with an X below it on the Internal connection (but still lets me connect), and on the External connection it just says it can't connect, and "connection refused:no further information" when I try to connect externally. Edit: Changing to host instead of bridge allowed me to change the port now for the second issue. But I'm still unable to access the server externally. Ports in router were updated to reflect the changed port.