bastl

Looks like the "Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller" is the only one on your board. Most boards these days have at least 2 controllers. Kinda bad, if you don't have enough space for a simple pcie usb card. Even a cheap x1 card should work. Another question, what PSU are you using? Maybe it's at the limit and small spikes causing to drop connected USB devices. Depending how old your board is, you might check the pins/contacts for the used USB port. Clean them in case there are some corrosion. For some USB devices a small voltage drop

Make sure you passthrough all parts for the GPU. The GPU itself i guess group20, the Nvidia Audio Controller group21 and the Nvidia USB Controller group22 Edit: I forgot group23 is also part from your GPU

I routinely updated the docker today and saw the same error. Not sure if it's because of the update or happened before. Current version for me is 6.1.71

@PeZet Usually as long as you don't change settings in your BIOS or add/remove USB devices, the IDs are kinda static. If you have a VM for example with a passed through USB controller which you often restart with changing USB devices connected, sooner or later you will see some IDs changing. As long as unraid itself always sees the same devices without adding or removing devices you shoud be ok. What you can do is passthrough a USB controller where the Conbee is connected to. Keep in mind, all connected devices will be disconnected from Unraid and handed over to the VM. Maybe get a

@Tomlox Maybe post a screenshot of the error you got, log from the vm and it's config. "It didn't work" doesn't really help identify your issues.

As I said before, performance might be an issue, depending on the programs running inside the VM. Also to be noted you can edit the xml of a VM and change the CPU flag to emulate a specific CPU type. For example the following I have in one of my VMs to emulate a Skylake CPU <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Skylake-Client</model> <topology sockets='1' dies='1' cores='6' threads='1'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='hypervisor'/> <feature

@Ford Prefect Vielen Dank nochmal für den Hinweis. Detailierte Netzwerkgrundlagen sind schon eine Weile her. Man kann ja auch nicht alles in seiner Birne behalten. Ich geb zwar mein Bestes, wie wahrscheinlich jeder technikversierte User, halbwegs auf dem Stand der Dinge zu bleiben, da fällt aber leider immer mal was hinten runter. Gerade wenn man es nicht tagtäglich vor sich hat 😘 @SpaceInvaderOne I'am kinda confused, seeing you in the german section of the forum. Thanks for the link.

@Ford Prefect Ah ok, also wird quasi der Traffik des gleichen Vlans routerunabhängig direkt im Switch weiter geleitet und bei Sprung zwischen 2 Vlans, die Datenpakete dann entweder, wenn es sich um einen L2 Switch handelt, über den Router gesendet, oder direkt im Switch sofern es ein L3 Switch mit Routingfunktionalität handelt gesendet. Bleibt mir jetzt halt noch die Frage, wie verbreitet L3s sind.

Kurze Frage. Mein Verständnis von nem managed Switch war immer, dass wenn Traffic an ein spezielles Vlan gerichtet wird, läuft das über den switch direkt und nicht erst über den Router. Der Switch erkennt wo Traffic hin soll, auf welchem Port welches Vlan hängt und "routet" den Traffic dann ohne den Umweg über den Router. Lieg ich da etwa falsch? Ohne so nen Switch, is klar, muß die Arbeit natürlich der Router übernehmen. Kenn paar Setups, wo hausintern 20-30 clients in diversen Vlans hängen und der Router an sich nen popelliges kleines Gerät is, was 0 Performance hat und die ganze

I'am curious which software development team forces their software to ONLY run inside a VM. Usually it's the other way, if a hypervisor is detected a license server gives an error and the software is unusable. Not sure which CPU feature are used by that software. By using a “CPU Host Passthrough” flag CPU features are directly used and not emulated by software like if you use a emulated "virtual CPU" like "Qemu64". With emulation you will always see a decrease in performance compared to a software directly running on hardware. If a software doesn't really need specific hardware fea

Quote from Wikipedia: https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security

@carnivorebrah @BVD Thanks! same time I found it myself be testing, I got a message for your answers 😅 By digging around and testing I also found the post with the changelog @BoxOfSnoo is refering to https://docs.linuxserver.io/images/docker-nextcloud Removing that file and recreate it was new for me. Never had any issues with my old config before. Last couple updates went fine until today. Renaming the "default" file in "/config/nginx/site-confs" and restarting the docker at first wasn't the solution. Looks like Nextcloud is reading every file in

@andreidelait I got the same errors like you after the update. The missing indices and the default phone region is easy to fix, but I'am kinda struggling finding the correct file to edit for adjusting the cardav, caldav, webfinger issue. Can you guys please hint me to the correct path where i can find/edit/adjust these entries. I'am kinda confused right now. I know I've edited this before, over a year ago and can't find it anymore. Thanks

Same here for me, started yesterday. Yesterday i clicked on "check for updates" and mariadb and collabora came up with an update. Only collabora showed not available. After updating mariadb I thought, ok, your internet has stability issues anyways, check again tomorrow. And today it shows the following. Not all are unavailable and Collabora shows a update now. Weird! I've checked pihole if anything came up in the query log, but nothing is blocked. I updated all packages on pihole (on a pi4), updated unbounds local root config, restarted the pi and rechecked for updates

Die Idee hatte ich auch schon. Leider gibt es keine öffentlich verfügbaren Listen aller Letsencrypt Server. Wurde nie publiziert und die IPs ändern sich leider auch. Ich hab im Pfsense nen Geoblocking drin. Beim Sperren von Nordamerikanischen IPs funktioniert die Erneuerung der Certs leider nicht mehr. Desweiteren scheinen die Letsencrypt Server auch teils in anderen Ländern zu stehen. Die kontaktierte IP heraus zu bekommen war nicht das Problem. Bei der nächsten Erneuerung wird dann aber meist ne andere IP angesprochen. Ist nicht wirklich praktikabel da IP Freigaben zu konfigurieren, die wie