Jump to content

Windows to mac migration emby connect


Recommended Posts

Posted

Emby Connect linking fails with HTTP 500 on migrated macOS server

I’m migrating from Emby Server 4.10.0.40 on Windows to Emby Server 4.10.1.0 on macOS.

I restored my configuration using the Backup & Restore plugin.

The new macOS server has a unique server ID, different from the original Windows server.

When I attempt to link an existing Emby Connect account to a local user, the Connect username field remains empty and the operation fails.

The server log shows:

POST https://connect.emby.media/service/ServerAuthorizations

Http response 500

ConnectManager.LinkUserInternal

The account lookup succeeds with HTTP 200.

The original Windows server is still running, and I need to preserve its existing Emby Connect associations during migration.

Is this a known issue with server authorisations or restored user accounts

Posted

Thank you. I've attached an extract from the Emby Server log covering the failed Emby Connect linking attempt on 9 October 2026.

The relevant error occurred at approximately 18:06.

The server successfully contacts Emby Connect, but the POST request to /service/ServerAuthorizations returns HTTP 500.

This is a new macOS installation restored from a Windows Emby backup. Both servers have different server IDs.

Please let me know if you need the complete server log.

emby-connect-error-extract.txt

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...