Celsian

Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by Celsian

  1. 1 hour ago, Mcklaren said:

     

    Hi,


    We didn't test the new python with pip, sorry, we'll revert to version 3.9.16 to fix the problem.

    Let's try to create the python package again with ssl active.

     

    Best regards.

    Thanks for your help!

  2. Looks like the dreaded SSL issue is back for pip, see attached.

    I didn't see any answers previously in this thread other than needing to wait for an update. Is that still the case?

    KFTUSyS[1].png

     

    Edit:

    Turns out the Repo was updated 11 hours ago with a new version of Python3 (3.9.17) that does not have SSL by default. The old package version 3.9.16 does. Hopefully this will get fixed soon.
    This support thread in Trash guides discord helped me figure out what was going on and install an older version of Python 3 that worked.

    Here's the two commands to run in the Unraid console to install the older version. If you already installed Python3 through the NerdTools pack, remove it. Do install python-pip & python-setuptools via NerdTools.

    wget -O /boot/extra/python3-3.9.16-x86_64-1_nerdtools.txz https://github.com/UnRAIDES/unRAID-NerdTools/raw/d01098b77b82c1d12a8491d988da2db7f66d9f40/packages/6.11/python3-3.9.16-x86_64-1.txz
    
    installpkg /boot/extra/python3-3.9.16-x86_64-1_nerdtools.txz --reinstall

     

     

  3. Turns out the problem was actually with my network settings, when I restarted my unRAID server, the network connections stopped working again for both VM's. To resolve it I discovered that under network settings I had to enable bonding for eth0.

    I enabled bonding for the NIC, set the mode to backup and only included eth0 in the bond.

    After starting the VM's again, their network connections started working and the connections continued working after an unRAID restart.

    • Thanks 2
  4. 1 hour ago, ich777 said:

    Are these friends hosted servers also dedicated servers or do they host that directly in the game?

     

    I don't play the game anymore because I simply have no time playing games currently but I didn't noticed micro stutters.

    You don't have to do anything special and I can't really think why you would experience micro stutters because only of the game server and TBH you are the first one who reported that and I've even never heard of that that a dedicated server is causing this.

     

    Maybe report it on the V-Rising Discord or support forums, maybe it has to do with the latest update but I really don't think that it is caused by that. Oh and it is a simple dedicated server running in a Docker container, I do nothing special in the container and it is almost the same as if you run the dedicated server on bare metal.

    Thank you for the response, it seems to be better today after I restarted the container. Maybe something funky was going on. I'll keep an eye on it and ask there if it comes back.

  5. I only recently got back into V Rising and decided to spin up my own server via a docker container.

    When playing, I get occasional micro stutters. The stutters are noticeably worse after about 24 hours of up time.

    I'm the only one on this server at the moment. This doesn't happen when I'm playing on a friends hosted server. Is there some sort of special resources setup I should be doing for this docker?

     

    I'm using a Ryzen 3900x with 64gb of 3200mhz memory. My CPU usage doesn't appear to go over 15% when I'm logged into the server.

    It has a Raid 1 cache drive setup with two 970 Evo Plus drives, which house my docker appdata folder. These are 85% empty.

    I do have several other docker containers running on the same machine, but none of them are game servers and appear to use very few resources.

     

  6. 18 hours ago, robertpaolella said:

    Is there a way to use this via reverse proxy? It's as if it creates two separate sessions when I access via reverse proxy vs accessing the IP directly.

     

    If you're using Apache2, add this to your reverse proxy virtual host:

     

    RewriteEngine On
    RewriteCond %{HTTP:Connection} Upgrade [NC]
    RewriteCond %{HTTP:Upgrade} websocket [NC]
    RewriteRule /(.*) ws://<docker ip address>:<port>/$1 [P,L]

     

    Replace <docker ip address> and <port> with your OpenBooks ip address and webui port.

     

    Edit: You need the rewrite mod for this to work:

    sudo a2enmod rewrite

     

  7. dg180, I found some information in another thread about this being an unRaid implementation issue. It's supposed to be fixed in the next version. In the mean time you can use the community application linked in this thread to fix things, it's called 'docker patch'

    Apparently the community app is set to not install on unRaid after version 6.11.5, so you shouldn't need to remove it later, it will remove itself.

     

     

     

  8. Small update. After fixing my Passthrough issue (earlier in this thread) the VM has been working flawlessly since.

    Upgrading to 6.11 worked fine. Passthrough continues to work.

     

    Edit: 11/28/22

    Passthrough still working as of 6.11.5

     

    Another note, I recently helped my brother with his GTX 770. The steps I took above did not work for that card, we were still getting Error code 43 in device manger, however a change to the VM's XML from this post fixed it:

    • Thanks 1
  9. I likely could have sysprepped it and moved it over that way, but I didn't think to do that until after I had already started setting up the new one. I've installed windows hundreds of times and this VM is just an HTPC anyway, so there's not a lot of setup necessary.

     

    Obviously that's not the case for everyone else, sysprep is a great alternative.

  10. Resolved my issue by creating a new Win10 VM using the following parameters:

     

    Machine: Q35-6.2

    BIOS: OVMF

    Hyper-V: Yes

    USB Controller: 3.0 (nec XHCI)

     

    For Graphics card passthrough I did the following:

    Settings -> VM Manager -> Advance View:

    PCIe ACS override: Both

    VFIO allow unsafe interrupts: Yes

    For the XML view I moved the Audio to the same Bus as the GPU (bus 0x04) and set the function of the audio to (0x1), then added multifunction='on' to the gpu address. See SpaceInvaderOne's video for more information on this.

        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>
          </source>
          <rom file='/mnt/user/isos/vbios/gtx_1060_strix_gaming.rom'/>
          <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/>
        </hostdev>

     

    For Syslinux configuration: Unraid OS:

    Main -> Flash -> Syslinux Configuration -> Unraid OS:

    Added:

    video=efifb:off

    to the end of the line.

     

    Note: I am unable to use my existing VDisk image. I had to fresh install windows and migrate settings and files. It sucks, but it works and I'm on 6.10.2 with an AMD Ryzen cpu and an NVidia GPU.

     

    Edit: No matter what I tried, I couldn't get the VM to pass through the gpu with Seabios selected. OVFM is the only thing that worked for me in 6.10.2.

  11. 4 minutes ago, trurl said:

    What happens if you don't create a root share?

     

    I think he means the root folder that contains the share list. For example if you connect to \\192.168.1.XXX\ in windows he sees the couple of shares he's created.

    He did not create a share for the root user or anything like that.

    When he goes to \\192.168.1.XXX\share_name it does the same thing

  12. I have been using zwave2mqtt for a couple months now. So far there have been 3 updates for the container. Each time I've applied the update it erases all of my zwave settings. This seems to be abnormal as none of the other 5 containers I'm running do that. Any tips as to why that might be the case?

    Or you know, I could actually edit the container and set the app data path... In my defense, they typically set themselves ;)

  13. On 4/13/2021 at 9:43 AM, alancostello said:

    So this thread originally fixed my issue, putting the following in my go file made passthrough work:

    echo 0 > /sys/class/vtconsole/vtcon0/bind
    echo 0 > /sys/class/vtconsole/vtcon1/bind
    echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind

     

    But now after upgrading to 6.9.2 I can't use it anymore, something about that third command sends my tower in to complete lockdown and I have to manually shut it down, I had to take out my USB and remove the lines from the Go file to get it to even boot properly. I'm still getting the MMAP errors because the GPU is being used by Unraid and I can't unbind it.

     

    I was worried about this, I didn't upgrade yet.

     

    Couple questions:

    1. Does it work again if you roll back to 6.9.1 and put the 3 lines back?
    2. I see that you are using the lines in your go file. What happens if you remove them from the go file, install the "User Scripts" plugin, Add a new script with those three lines (#!/bin/bash as the first line), and run that script at 'At Startup of Array'?

     

    Edit:

    I went ahead and updated to 6.9.2, everything is working fine for me with the setup I mentioned in my previous post. See #2 from my "Couple Questions" above. I did not attempt to add the lines to the go file to see if that made my boot fail as well. It's working with the "User Scripts" plugin, I was content to let it be. If anything I said in my previous post or this one was unclear, let me know and I'll clarify.

  14. I'd like to add a new store. I found the instructions to do so here: https://jef.codes/streetmerchant/help/general/#adding-a-store but I do not see the src/store/model folder in the appdata directory for streetmerchant. Am I looking in the wrong place? Should I create these directories myself or map it to the appdata directory somehow?

     

    mnt/user/appdata/streetmerchant

    Only contains an empty logs folder.

  15. 15 hours ago, Econaut said:

    Thanks for that guide - I actually found it referenced somewhere else and followed it pretty much to the letter with the most recent Win10 VM attempt (stopping short of the virt-manager section). After reading countless forum posts, articles, and watching videos I've seen everything all over the map recommended for any possible scenario (SeaBIOS vs OVMF, Q35 vs i440fx, use vbios or don't) - the community doesn't seem to have any reliable consensus aside from 'use whatever works' & 'try everything' which is infuriating haha.

     

    I may not be having the exact same issue, in fact I don't think anyone in the world is having my exact issue since my hardware configuration (and most folks) are rather unique, but I am on 6.9.1 and I cannot get GPU passthrough working for the life of me despite following every guide I could get my hands on.

     

    Behold:

     

     

    Sounds like you've tried it all, I don't see any glaringly obvious issues with the current setup you have. I never could get OVMF to work with Windows 10, I'm stuck on SeaBios. From what you said, you've already given that a try though, not sure what else to suggest.

  16. 21 minutes ago, Econaut said:

     

    Not currently. I did install teamviewer with VNC when initially installing Ubuntu and while I can actually see the teamviewer ID populate in the systems list when I start it up in passthrough mode, I cannot actually connect to it. I would probably be able to SSH in if that is what you mean but I don't have that enabled currently.

     

    Well, it's good that it's showing up. Can you post a screen shot of your VM settings?

     

    This checklist might help as well: https://mediaserver8.blogspot.com/2020/07/problems-passing-through-gpu-to-unraid.html

     

    You don't seem to be having the same issues as the guys who started this thread. The three of us couldn't get our VM to boot at all, the video driver was causing the VM to terminate prematurely. Have a look at that link above, it might help.