elibosley

Are you sure your flash drive is good? Try writing a file on your flash drive and see if you can read it or delete it, sometimes broken drives can cause this when they fail into read only mode.

This is currently a bit broken, we removed the check in logic from servers and are relying on a legacy data point for this. There will be a new version of mothership published in the next month or two that will resolve this for good.

Actually, rebooting shouldn’t be necessary, it seems like your api may have failed to configure and resolved on a reboot but ideally this would not require a reboot! Sorry about this.

Just followed up on that GitHub thread. I’m very interested in solving this for you and others, and I think I need a bit more logging and information about what the exact request from HA is that is failing.

You may need to forward your server or be on wan, there is a system called nat reflection that can allow the wan address to be used internally but it is likely that from within your own network you will only be able to use the lan address (and that’s expected).

Awesome! Let me know if you continue to have issues (feel free to direct message me your IP address as well) as that will allow me to see if you’re being rate limited by our firewall!

We were having issues with the backing server for Connect, which have been fixed now. Please try signing out and back in on your server again!

This all seems to be related to the issue we discovered today causing problems with the database backing mothership. Please try signing out and back in and let me know if issues persist.

This was a bug in our registration system. This is now fixed, please try again!

Try today- I think we were aggressively rate limiting mothership causing too many disconnections!

If you go to each server and sign out of Connect, it will trigger a removal from the system. We’re also planning on deploying a full infrastructure rebuild in the near future which I am hoping will resolve the spotty connectivity going forwards.

We didn’t really document this but settings -> management access has api key creation as well! I’ll try to get the docs up to date to make this easier.

Right now it’s just Unraid.net BUT we are planning on having this system extensible for other OIDC controllers. This is built with oAuth2 so the token validation endpoint in the API needs updating and the button component will need to be aware of other providers. The API is open source as well if you’d like to see how it works: GitHubGitHub - unraid/api: Unraid API / Connect / UI MonorepoUnraid API / Connect / UI Monorepo. Contribute to unraid/api development by creating an account on GitHub.

Thanks so much for this. We'll add a check to our plugin installation to make sure we remove a directory for unraid-api, that should always be a symlink!

I just added UPS monitoring today! We're also working on a much better docker integration for you right now!

Can you please install the plugin, and then enter this command: unraid-api plugins install -b unraid-api-plugin-connect Then please let me know if that works or errors out and I can help out from there.

Please try again with the latest plugin, we’ve resolved this issue we believe.

Hi! Sorry to revive this just wondering if the latest updates are still giving you trouble?

This is indeed fixed, or drastically minimized. Be aware that querying for USB info may cause this error to occur but it isn’t happening on every page load anymore.

The latest update has fixed this lifecycle issue. Please update your Connect plugin.

This is fixed as of our Monday, July 28 release, we’ve set a timer job to truncate logs over 5mb rather than relying on Logrotate.

This is fixed as of our Monday, July 28th update - we now truncate logs every 20 minutes if they grow over 5 megabytes, which should prevent this going forwards.

We’ve released quite a few updates that fixed docker and lifecycle issues since March, I’d recommend trying out the latest release if you’re willing as I’d love to know if it has solved these issues.

Should be in settings -> management access and scroll down, there should be a WAN port setting if you set access to Static. If you’re not seeing it - please update your Connect plugin and let me know if it still doesn’t show.

This is very strange - I think related to the other bugs users were seeing after our Monday release. We’ve published a new version that may fix this issue, please update Unraid Connect and let me know if you’re still seeing this problem.