muzo178

same here

I am getting an Error Something went wrong message when i try signing in. The clicking on theconnect logo on the right hand side reveals unraid-api failed to update Connect account configuration. Response not successful: Received status code 400 I tried uninstalling and reinstalling the plugin and running unraid-api plugins install unraid-api-plugin-connect as recommended to no avail. Diagnostics attached. Looking at my browser console reveals Failed to load resource: the server responded with a status of 400 (Bad Request) every few seconds. hpg4-diagnostics-20260110-1334.zip

this issue came up while I moved my Home Assistant OS VM from Proxmox to a brand new Unraid 7-rc1 install. My matter devices were all unavailable. This command was the fix.

check this.. if you have the same in your syslog, you have the same problem due to a kernel issue..

I added another satellite device to my UNRAID box and now I am getting this message in the logs constantly.. Any ideas? Aug 12 14:00:16 UNRAID kernel: vhci_hcd: unlink->seqnum 108674182 Aug 12 14:00:16 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:22 UNRAID kernel: vhci_hcd: unlink->seqnum 108700222 Aug 12 14:00:22 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:28 UNRAID kernel: vhci_hcd: unlink->seqnum 108727607 Aug 12 14:00:28 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:34 UNRAID kernel: vhci_hcd: unlink->seqnum 108755739 Aug 12 14:00:34 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:40 UNRAID kernel: vhci_hcd: unlink->seqnum 108782401 Aug 12 14:00:40 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:46 UNRAID kernel: vhci_hcd: unlink->seqnum 108810661 Aug 12 14:00:46 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:52 UNRAID kernel: vhci_hcd: unlink->seqnum 108838662 Aug 12 14:00:52 UNRAID kernel: vhci_hcd: urb->status -104 Aug 12 14:00:58 UNRAID kernel: vhci_hcd: unlink->seqnum 108866563 Aug 12 14:00:58 UNRAID kernel: vhci_hcd: urb->status -104

yup, fixed. now my zigbee and rtl sdr dongle that is upstairs connected to a pi are happily and automatically humming along passed through to my hasssio VM in the basement server. thanks for this.

this is fantastic in initial testing. I am getting this in my syslog every minute though.. UNRAID usb_manager: Info: rc.usb_manager USBIP Host Check attached failed Array

+1 for this. It would be great if USB Manager could mount remote USBIP devices automatically if they are discovered. I have a couple of them set to attach automatically to the VM when they are available, but if I restart the remote host that has the USB devices plugged in, I have to manually attach them so that they then attach to the local VM. Amazing plugin btw. Keep up the good work..

I definitely agree with this. 5.x kernels don't like my hardware.

So we both have the touch file i915.conf. Theoretically that could be the culprit, but I doubt it. Whoever finds the energy to upgrade and try without the touch file, report back. :))

In my go file I'm only modprobing it87 drivers for getting the fan speed. Removed everything else pertaining to i915. I just checked my flash backup from 6.10-rc2, and there was a i915.conf file in modprobe.d. Maybe removing that after the upgrade might make a difference, but I really don't have the patience to go upgrade and then have to downgrade again. I'll try with rc3 if gets released or 6.10 final... Do you have flash backups from 6.9 or 6.10 that you can check if you have this file in modprobe.d @Tristankin? On another note, if it is not needed, the upgrade process should be removing that. It's not like we do fresh flash setups on every upgrade....

just as before... zero, zilch, zip, nada, nothing.

Bit the bullet and updated to 6.10.rc2 after @jkirkcaldy's feedback... Unfortunately crashed twice in three days...both during while the plex docker was transcoding... I'm either gonna try putting plex on a VM this time, or gonna roll back to 6.8.3...

there's a few of us with the same kind of issue over here. no solution apart from sticking to 6.8.3 yet:

I have tested pretty much everything and now I know for a fact that once I start transcoding on i915, it will halt within minutes.