Windows to mac migration emby connect

[SCTVMB 0]

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

[Luke 43537]

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[SCTVMB 0]

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

[Luke 43537]

@sa2000

[sa2000 880]

@SCTVMBI will try and see if I can replicate this.

My understanding is that you wish to have two different emby servers with a local user account on each that is linked to the same emby connect email address.

if you are able to use browser dev console on the windows machine to capture an emby connect login sequence using this emby connect account, that will show me what data emby connect has for server. Saving the Dev Console Network packets into a har file (Save All as ,har)  and sending me the har file by Private Message - so enabling Dev Console (F12) in browser and starting capture and then going to http://app.emby.media and signing in to the emby connect account and then when you get to select server screen, saving all the network requests and responses into a har file and sending me zip of the har file by private message. 

And from the windows emby server, within the server app data area (paths show in View Server info on the dashboard), locating these files:

programdata\data\connect.txt

programdata\data\device.txt

and include these 2 files in the zip please

Separately on the MacBook, please locate these 2 files - they would be in paths

.config/emby-server/data/connect.txt

.config/emby-server/data/device.txt

copy these 2 files out and save into a separate zip and include in your private message

 

[sa2000 880]

On 09/10/2026 at 20:28, SCTVMB said:

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.

I have gone through a test and it was successful

- Emby Server 1:  Backup produced

- Emby Server 1 shutdown

- Created a new emby server (emby server 2) 

- Restored from the server 1 backup with the "Restore Server Id" unticked

- After relaunch and logging into the new restored server, i edited the user account to link to the same emby connect email account as was on server 1. This was successful

So will need to go through a detailed investigation of the setup on your 2 servers (with the information requested so far initially)

 

 

 

[SCTVMB 0]

Hi and many thanks. I was not trying to keep 2 servers no. I was just trying to migrate my original 2 year old server to new hardware (windows to mac OS). I think it had/has something to do with all backups keeping way to much “windows” information. On the mac it wiuld not accept a restore form the backups taken on windows. So i ended uo doing it manually bit by bit. 

[sa2000 880]

 

2 hours ago, SCTVMB said:

(windows to mac OS)

I should have flagged that earlier !

We do say in the backup and restore documentation that when migrating to a new system - the filesystems directory separator would need to match  - so windows to windows maintaining the "\" path directories separator and linux/mac to linux/mac maintaining the "/" path directories separator

Using Restore to Migrate to a New System

2 hours ago, SCTVMB said:

So i ended uo doing it manually bit by bit. 

I understand now. The outcome would be indeterminate because you would need to know exactly which files / folders / contents are relevant for Emby Connect and the users

So lets not investigate what happened but try and resolve your issue going forward

What state are you in now ? Are you happy with what you have on the Mac and just need to fix the emby connect issue ? 

Is the windows server still in use ?

You could copy out these folders and subfolders within them and zip and make available to me and I will have a look

Windows PC

programdata\data
programdata\config
programdata\logs

MacBook

.config/emby-server/config
.config/emby-server/data
.config/emby-server/logs

I can send you an upload link for the zips if you are happy sharing the files

 

Edited October 15 by sa2000

[Neminem 1981]

@sa2000People don't read documentation