I’m having the same Unraid Connect registration issue on both of my Unraid servers: Epic-Alpha and Epic-Bravo.

The symptoms are the same on both systems.

When I try to register either server with Unraid Connect, the Unraid Account side appears to accept the registration, but the process fails when it returns to the local server.

The GUI shows:

Something went wrong
Sign In Failed

On Epic-Alpha I investigated this in detail.

Server details:

• Unraid OS 7.3.2

• Unraid API 4.37.2+a00c99a5

• Unraid Connect plugin 2026.08.20.1609

The API itself is running normally:

status: online

Using Chrome DevTools, I found that the registration request to account.unraid.net succeeds with HTTP 200 and the returned data contains:

validated: true

The failure happens afterwards when the local server processes the Connect sign-in.

The browser console shows:

GraphQL error: Bad Request Exception

and:

unraid-api failed to update Connect account configuration

The failing operation is:

connectSignInMutation

The local API log also repeatedly shows:

ConfigFileHandler:connect.json: Migration failed. Using defaults.

We have already done quite a lot of troubleshooting.

First, we found a real DNS issue in my local network. I use Pi-hole together with Unbound, and Unbound had DNS rebinding protection enabled for RFC1918 ranges, including:

private-address: 192.168.0.0/16

This caused the unique *.myunraid.net hostname to lose its private IPv4 result.

Directly querying Cloudflare DNS returned the correct result:

myunraid.net hostname -> 192.168.100.30

but querying through Pi-hole/Unbound initially did not return the IPv4 address.

We fixed this properly by adding:

private-domain: "myunraid.net"

to Unbound.

After restarting Unbound, Pi-hole correctly returned the local Unraid IP for the myunraid.net hostname.

We also verified the complete DNS path through the router, and the server now resolves its own myunraid.net hostname correctly.

In addition, I temporarily removed Pi-hole from the MikroTik DNS path entirely to exclude Pi-hole/Unbound as the cause.

The Unraid Connect registration still failed exactly the same way.

Other things already tested:

• Confirmed the Unraid API is online.

• Restarted the Unraid API.

• Installed/reinstalled the Connect API component with:
  unraid-api plugins install unraid-api-plugin-connect

• Confirmed the Connect plugin loads correctly.

• Provisioned the Unraid Let's Encrypt myunraid.net certificate.

• Confirmed the unique myunraid.net hostname resolves to the correct LAN IP.

• Confirmed the HTTPS myunraid.net URL opens successfully in Chrome.

• Chrome reports the connection as secure.

• Tested registration from the local Unraid WebGUI.

• Tested registration through the Unraid Account page.

• Tested normal Chrome sessions and private/clean sessions.

• Tested after flushing DNS/browser state.

• Remote Access has remained disabled.

• Temporarily removed connect.json and allowed Unraid API to create a fresh one.

• The newly generated connect.json still immediately produced:
  Migration failed. Using defaults.

• The original Connect configuration was restored afterwards.

• Monitored:
  /var/log/graphql-api.log
  nginx access logs
  nginx error logs
  Chrome Network
  Chrome Console

An important observation is that while the registration to account.unraid.net succeeds, the failure happens during the local Connect account update.

So at this point the sequence appears to be:

1. Register server with Unraid Account

2. Unraid Account returns HTTP 200

3. Response contains validated: true

4. Browser returns to the local Unraid server

5. Local connectSignInMutation runs

6. Local Unraid API returns Bad Request Exception

7. GUI shows Sign In Failed

The fact that the same problem occurs on both Epic-Alpha and Epic-Bravo makes me think this may not be a single-server configuration issue.

Diagnostics for Epic-Alpha have been uploaded to this forum thread.

At this point I have stopped changing the local configuration because DNS, Pi-hole/Unbound, HTTPS, certificates, browser state, API status and the Connect plugin have all been checked or ruled out.

Any guidance on what could cause connectSignInMutation to return Bad Request Exception, or what additional logging/debugging would be useful, would be greatly appreciated.

Many thanks.

Ronald

epic-alpha-diagnostics-20260826-1529.zip

Edited 15 hours ago15 hr by TallMan206

Does it work if you bypass Pi-Hole/Unboaund, etc, and connect the server directly to the router?

11 minutes ago, JorgeB said:

Does it work if you bypass Pi-Hole/Unboaund, etc, and connect the server directly to the router?

Yes, i also tried that. Router with 1.1.1.1 and no pihole/unbound interference. Also Chrome with secure DNS off, so that also does not intervere. Brave browser has the same problem, both browsers also with Incognito.
I am really lost in what else I can try.

I cannot reproduce it, so it's not a general issue, you can try booting a new trial with a stock Unraid install, then only install Connect and see if you can register it, to rule out a config issue. If that still fails, it's likely an external issue.