pujitm

hey odon, so sorry this happened -- gotta hate such surprises. hopefully issues like this will be easier to anticipate one the api/connect plugin is open sourced. for context, this update added and changed (the name of) some css variables in order to fix a bug with header gradients. i bet that's breaking your theme customization. rn, i'm not 100% sure what the solve looks like, so i'll have to get back to you on that. going to raise this to the team today for sure tho. agreed on the "roll-back" suggestion. it'd be awesome to have a way to "feature flag" changes, especially breaking changes. this will (most likely) require an update to the connect settings page first though.

dude i thought it was just me. will investigate, but i currently have no idea why this is happening or what could have caused this. this might have been happening since the 2025.02.06 release. apologies if this breaks yours or anyone else's workflow. fwiw, it also breaks mine.

hey guys--sorry this this has been going on so long. that must be super frustrating. is this still happening? if so, i could try cooking up some cursed strats. give this a read too tho:

@banthon if your issue persists, I'd recommend starting a ticket with https://unraid.net/support if you haven't already. my blind guess would be that your connect config (i.e. /boot/config/plugins/dynamix.my.servers/myservers.cfg -- you should prob not paste this file here btw) is at least partially corrupted. does everything else in the webgui work, like notifications, etc? any errors in browser dev tools? for a sanity check (if you're comfortable/technical), you could try setting apikey and localapikey in that myservers.cfg file to an empty string. for reference, this is what a completely fresh myservers.cfg looks like (see how under [remote], apikey and localapikey are set to ""): [api] version="4.0.1" extraOrigins="" [local] sandbox="no" [remote] wanaccess="" wanport="" upnpEnabled="" apikey="" localApiKey="" email="" username="" avatar="" regWizTime="" accesstoken="" idtoken="" refreshtoken="" dynamicRemoteAccessType="DISABLED" ssoSubIds="" emptying apikey and localapikey will log you out of Connect, so you'll need to log back in again. sorry this issue's been plaguing you so long.

interesting, so if i'm understanding correctly, when you use e.g. http://tower.local to access your server, it doesn't work, but when you access it using an ip address (e.g. 192.168.37.8), it does work? if so, this sounds like a networking issue rather than an unraid-api issue. could you paste the errors (if any) from the console in your browser's developer tools? (link to guide on opening dev tools, just in case)

hopefully the update today fixed this. let us know if it didn't🤞

😉 this shouldn't happen anymore after today's update. feel free to tag me if it comes up again.

fixed in the connect plugin's latest release

hey guys, the connect plugin's next release will fix this. sorry to keep yall hanging on such an annoying issue. we'll try to get it out for ya this week or early next week. Edit: just shipped the release. 🤞

i'm working on a fix, @kaiguy! in the meantime, you can run `unraid-api restart` from the terminal to reset notification counts.

Excited to have you on board, Craig 🎉

super cool to read, thanks for posting! welcome to the unraid life