OmgImAlexis

This may help you. The container name is likely a random one that docker has assigned. From the logs that looks like it has todo with cloudflare tunnels.

WOO!

The version we pushed out yesterday should resolve this.

Please open a seperate issue as this is unrelated. The outage shouldn’t be effecting backups.

The issue in the original post is solved. The issue you're all having is unrelated, it's related directly to the cloud issues we're currently having.

For those that have it installed still would you mind checking the dashboard. It may be slow at loading but I believe I may have resolved that part of the outage.

Still working on it. I'll have an update once we get things sorted.

Nope. Just me. Sorry about this. Should be back up as soon as we resolve the issue. Feel free to join the discord https://discord.gg/unraid while you wait.

Hey so sorry about this. We’re currently dealing with a few issues and should have a post up about this soon. Sorry for the inconvenience.

Just hit this myself from an unclean shutdown.

I believe this should be resolved in the next plug-in update. Sorry for the inconvenience.

The api has nothing todo with remote access. Restarting it won’t change anything. If your connecting ip address is the same as the server’s wan you’ll get the local otherwise you’ll get the remote. Has anything changed network wise?

Okay, is there any chance you could try running the api without those containers or healthchecks and see if you notice the CPU still spiking? If that resolves it then the next plg update should fix this for you.

Just to check do any of your containers have health checks?

@BoonioX sorry for not seeing this until now. Are you still having this issue? If so I'll raise the issue with someone on the team. @thunderclap I've never seen that on unraid before. Would you mind creating a new thread for this or hopping on our discord?