Jump to content

Can't Connect After TOS6 Update


Recommended Posts

bparrish450
Posted

My TOS Version updated to 6.0.650 and now emby won't connect. I get a 404 Not Found. I am not sure why it can not find my server or files now. Please help, I do not want to have to erase everything and start over again.

Screenshot 2025-03-24 213532.png

Screenshot 2025-03-24 213342.png

Posted

@bparrish450I see you have 8181 in the url as your port number. Are you sure that is correct?

bparrish450
Posted (edited)

The port that I have listed in my emby is 8096 but when I click on the emby app in the TOS it opens to port 8181. When I log into the emby browser I get the following (see screenshots)

Screenshot 2025-03-24 214829.png

Screenshot 2025-03-24 214720.png

Screenshot 2025-03-24 215301.png

Edited by bparrish450
Posted

Try putting this in your browser address bar instead:

http://ip:8096

Where ip is the ip address of the nas. Please see if that helps .Thanks.

bparrish450
Posted

I get the following...

Screenshot 2025-03-24 215718.png

bparrish450
Posted

Is this the log that you are talking about...

Screenshot 2025-03-24 220949.png

bparrish450
Posted

It won't enable, it keeps saying operation failed.

Screenshot 2025-03-24 221324.png

Posted (edited)
On 3/25/2025 at 4:36 AM, bparrish450 said:

My TOS Version updated to 6.0.650 and now emby won't connect.

Hello.

I had the same problem after updating to 6.0.650. The Emby Server App in TOS was permanently disabled.

My TOS 6.0.650 is accessible via port 8181. My Emby Server is accessible via port 8096.

 

This solution worked for me:

 

1. First, uninstall the Emby Server app in App Manager.

EmbyServerApp4.9.0.42Uninstall.thumb.jpg.c2cd305291c37a35583bfd3a786d82c6.jpg

2. Restart TNAS.

3. Go to File Manager => Emby directory.

4. In the Emby directory, rename these two folders:

"data" and "config" 

The extension is irrelevant.

I named these folders like this: "data.error" and "config.error."

EmbyFileManager4.9.0_42.thumb.jpg.44e1a3511446d2d17eb4f6f0ba48685e.jpg

5. Now install the Emby Server app manually.

EmbyServerApp4.9.0.42Install.jpg.a23328d2181d2a6a58c03a22c14dc508.jpg

6. Restart TNAS and try to access the Emby Server. If access via IP address doesn't work, try accessing the server via Emby Connect. 

7. If you can access the Emby Server again, you need to check all settings.

Edited by jhnbrg
  • Thanks 1
Posted
4 hours ago, jhnbrg said:

Hello.

I had the same problem after updating to 6.0.650. The Emby Server App in TOS was permanently disabled.

My TOS 6.0.650 is accessible via port 8181. My Emby Server is accessible via port 8096.

 

This solution worked for me:

 

1. First, uninstall the Emby Server app in App Manager.

EmbyServerApp4.9.0.42Uninstall.thumb.jpg.c2cd305291c37a35583bfd3a786d82c6.jpg

2. Restart TNAS.

3. Go to File Manager => Emby directory.

4. In the Emby directory, rename these two folders:

"data" and "config" 

The extension is irrelevant.

I named these folders like this: "data.error" and "config.error."

EmbyFileManager4.9.0_42.thumb.jpg.44e1a3511446d2d17eb4f6f0ba48685e.jpg

5. Now install the Emby Server app manually.

EmbyServerApp4.9.0.42Install.jpg.a23328d2181d2a6a58c03a22c14dc508.jpg

6. Restart TNAS and try to access the Emby Server. If access via IP address doesn't work, try accessing the server via Emby Connect. 

7. If you can access the Emby Server again, you need to check all settings.

Hi, thanks for the info. Did the permissions change on those folders following the TOS6 upgrade?

Posted (edited)
1 hour ago, Luke said:

Did the permissions change on those folders following the TOS6 upgrade?

Not that I know of. I haven't changed anything. The Update Notes for TOS 6.0.650 don't contain any information on this.

When I noticed the problem, I initially thought that the Fritz!Box had deleted the port forwarding after the FRITZ!OS Update (version 8.03 from March 15, 2025). Or that the IP address of TNAS had changed after TOS Update. Neither of these is the case. Then I tried installing an older Emby Server Beta App version because I thought the new version was causing problems. That wasn't the cause either.

Then the only thing that worked for me was the reinstallation method mentioned above. I have no idea what happened.

Edited by jhnbrg
Posted

Nope, did all those steps and it won't stay enabled. 

Posted

Ok, I tried the beta version also. It stays enabled now but it comes up as 404 not found but it's on :5443 if I put in the :8096 it shows " this site can't provide a secure connection sent and invalid response" 

Oh, as I'm writing this out it looks like it was on https: I put it as http:  and it logged in. But I can't click on the app from tos6 I have to manually type in the right port number and change https 

Posted

So I figured a way around this for now. under network - general I had force redirection from http to https connections turned on. Turning it off  the app from navigation bar now works. 

This worked before I updated Emby from tos app center. So not sure what happened. 

Posted
On 3/31/2025 at 11:49 PM, lil-duke said:

So I figured a way around this for now. under network - general I had force redirection from http to https connections turned on. Turning it off  the app from navigation bar now works. 

This worked before I updated Emby from tos app center. So not sure what happened. 

Do you mean an Emby option or something in tos?

Posted

It's within tos6. I had to disable that option then clicked on Emby. It pulled up the Emby page instead of "404 not found". Then went back to tos6 settings and re-enable the option again. 

  • Thanks 1

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...