dodgypast

Anyone put a seperate pfsense firewall infront of this. Everything else is working but I can't get traffic forwarded into swag.

24.0.12 is a valid version. There haven't been any security warnings. If it's not broke don't fix it is a valid strategy.

You could not upgrade from 24.0.12 via the command line. We're not idiots.

I just went through this and found a relatively painless way to do it: 1. downgrade the docker to linuxserver/nextcloud:24.0.12 2. Choose the update to 25.0.7 from the webgui 3. For me it kept timing out, I would use the back pause for a minute then forward button on the browser and choose continue. 4. Keep doing this until it goes into maintenance mode. 5. At this point the command line works so use docker exec -it nextcloud updater.phar from the UNRAID terminal, it will successfully continue the upgrade to 25.0.7. 6. Repeat the command docker exec -it nextcloud updater.phar and it will upgrade to 26.02 7. Upgrade the docker to linuxserver/nextcloud:latest

Guess what type of environment I'm building right now. But since I do not have infinite spare time and I'm also running a service for my family, my priority wasn't immediate perfection. It was how to migrate my services from unraid to proxmox with the minimum of downtime. I wanted to put the information out there for others who may find themselves in a similar situation.

I got it working pretty well. It doesn't seem like passing hardware through to an UNRAID VM, and passing those through to a VM in UNRAID is feasible however I did get my Intel iGPU passed through to UNRAID and have my plex docker in UNRAID use that for transcoding which was a huge win. That was the only real issue, every other UNRAID docker and the VMs that didn't rely on hardware pass through worked fine. Drives just worked by passing through my SATA controllers for my storage and the nvme drive my cache is on. ( Proxmox is installed on an nvme drive ) It took a fair bit of trial and errror but here is the config file for my unraid VM in proxmox: bios: ovmf boot: order=usb0 cores: 20 cpu: host efidisk0: local-lvm:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M hostpci0: 0000:02:00,pcie=1 hostpci3: 0000:00:02,pcie=1,x-vga=1 hostpci4: 0000:00:17.0,pcie=1hostpci5: 0000:03:00.0,pcie=1 machine: q35 memory: 64000 meta: creation-qemu=7.1.0,ctime=1677658184 name: UNRAID net0: e1000=BE:10:40:4C:9C:2E,bridge=vmbr0,firewall=1 numa: 0 onboot: 1 ostype: l26 scsihw: virtio-scsi-single smbios1: uuid=d6b4046f-fef5-43bd-b70b-10aa383dd291 sockets: 1 usb0: host=0781:5567 vmgenid: c10f6ea6-ade4-4a61-9bb8-10045a7c2329

Thank you very much. Also thank you for the back ground readiung so I can understand what has been happening.

I don't want the URL to be hijacked, I just want it to stay with hostIP/Main as the URL. I can use wireguard to get to it remotely fine. My internet isn't always that reliable and getting locked out until I physically accessed my server was inconvenient. As rquested I have included my diagnostics. tower-diagnostics-20230123-1237.zip

I want to know that if I put my IP address in I will always end up at the GUI no matter what. It's great functionality for many, but it spikes my anxiety.

When I type in the ipaddress it reditects to HASH.unraid.net:PORT/Main and the browser says it cannot connect to the server. I've tried rebooting and there's no change. I've fixed it by going through the gui on the machine and updating the cert through the webui. So what I would like to know is if there is a way of turning this off so I can go back to relying on my own ipaddress rather than risk having to deal with issues like this in the future.

I'm having a problem installing modules on a new install. I've tried a few and I get the following error for every module I try: The requested manifest at "https://bitbucket.org/rpgframework-cloud/shadowrun6-eden/downloads/system-staging.json" did not provide system manifest data. I have posted it as an issue on Github here: https://github.com/felddy/foundryvtt-docker/issues/565

Has anyone got Quicksync transcoding working with this? I get this error: Playback Error This client isn't compatible with the media and the server isn't sending a compatible media format. When I check the logs the issue is from ffmpeg: ffmpeg version 5.1.2-Jellyfin Copyright (c) 2000-2022 the FFmpeg developers built with gcc 12.2.0 (GCC) configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-shared --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto --enable-gpl --enable-version3 --enable-static --enable-gmp --enable-gnutls --enable-chromaprint --enable-libfontconfig --enable-libass --enable-libbluray --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libdav1d --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-opencl --enable-vaapi --enable-amf --enable-libmfx --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 [AVHWDeviceContext @ 0x561045659500] Failed to initialise VAAPI connection: -1 (unknown libva error). Device creation failed: -5. Failed to set value 'vaapi=va:,driver=iHD,kernel_driver=i915' for option 'init_hw_device': Input/output error Error parsing global options: Input/output error Transcoding works fine with Plex and I have the docker setup with the following: My settings in Jellyfin:

I'm using the linuxserver version of this and I'm having trouble getting it to accept the command line arguments. I've found the plex_meta_manager.py and tried running: python plex_meta_manager.py --delete-collections But it doesn't accept the --delete-collections and behaves the same as when I run: python plex_meta_manager.py Edit: Found a work around by installing it into a linux vm and running it from there. I had a huge amount of collections that had been erroneously created repeatedly ( eg. 40+ best of 2019, 2018 etc. ) that would have been a rfeal pain to delete manually. Further Edit as actually that just helped me figure out what was the real problem: Okay, actually PMM makes it difficult to figure out how the delete collections command works. It actually tells it to delete the collections just before it refreshes them. So as it is hard coded to run at scheduled times it won't delete them immediately. To get around this I combined -r with -dc so it would delete the collections then rebuild them immediately after sending the command.

Just found this thread through google and doing that worked for me on Firefox.

I was hoping that would, from your comment obviously not. In which case I need some from @limetech to help me diagnose it.

Fixed everything except the booting issue, which might be fixed by a parity check. I removed all my passed through devices from the VMs and from the bind devices dialogue, rebooted, disabled PCIe ACS override, rebooted, this time there were no conflicts so I rebound everything I needed, rebooted, reenabled everything in the VM edit screen and the VMs booted perfectly.

It boots with the array stopped but I can start it manually.

By disabling my USB passthrough and passing through USB devices individually I got my Linux VM working. This isn't a long term solution unfortunately as I need to be able to plug and unplug devices. Still getting the issue with it booting with the array stopped. I have included the latest diagnostics. tower-diagnostics-20211012-2126.zip

Lots of varied issues after my Linux VM froze. Now when I try to reboot it boots with the array stopped. When I boot the Linux VM it gets to the graphical login screen but the keyboard and mouse don't respond. ( if I boot to the console the keyboard works but when I reboot it gets stuck at the tiano core screen) Windows is even worse, it just shows the tiano core screen and freezes. I've included a couple of diagnostics. tower-diagnostics-20211012-1924.zip tower-diagnostics-20211012-1939.zip

This did the trick, huge weight has been lifted.

I have had my USB key accidentally get wiped. Unfortunately my last back up was before I added a drive, which has a lot of new data on it now. The web front end seems insistent that my drive will be wiped, but obviously I would like to avoid that.

That's exactly it. Kicking myself for not thinking of that.

Hi everyone, My Plex docker is shutting down every night at 3am and I'm scratching my head as there's nothing I can find in my Plex settings that would appear to be causing it. I was wondering if anyone could help me find the cause. Here's the relevant part of the Plex logs:

My container seems to be told to shut down every night at 3am. Any ideas where this might be coming from and how I can prevent this?

Updated fine.