HELP！！！ADM 3.5.9 &EMBY 4.9.0.70 CAN'T OPEN SEVER Page!

[LN13uLL 5]

man... 4.9.x has been complete junk... everything worked fine in 4.8.x. just like some other users here ever since 4.9.x was updated on my nas for emby, i'm no longer able to even load up my emby server anymore on asustor.  never ever an issue prior to 4.9.x..... i even uninstall and reinstalled and now it's a complete of a mess as I can't get anything to work.  i also give up... so sad...

Edited November 21, 2025 by GrimReaper
Topic title modified

[Luke 42077]

hi @LN13uLLcan you please describe your issue in more detail?

How to Report a Problem

Thanks !

[LN13uLL 5]

On 11/17/2025 at 3:28 PM, Luke said:

hi @LN13uLLcan you please describe your issue in more detail?

How to Report a Problem

Thanks !

I went ahead and was able to completely uninstall 4.9 (and remove any remanences of 4.9) and did a 100% clean install of 4.8.  fixed and adjusted permissions which took me a while since it's been over what 8-9 years since i set up emby server.  Im good for now.

i'm waiting for the library scan to finish overnight and make some refinements tomorrow.

Edited November 19, 2025 by LN13uLL

[Luke 42077]

What model Asustor?

[LN13uLL 5]

1 hour ago, Luke said:

What model Asustor?

Model: Asustor AS-604T

OS Version: 3.5.9.RWM1

[Luke 42077]

So you are not on ADM 5?

[LN13uLL 5]

4 minutes ago, Luke said:

So you are not on ADM 5?

No I’m not. It doesn’t give me the option to update anymore. It used to. Probably bc my model is so old now. 

[Luke 42077]

OK we had anticipated this might happen with very old devices. Our package used to bundle it's own version of glibc. We had to stop doing this for newer devices, so now it uses the one on the system, and the one on your system must be too old.

The only way for us to resolve it would be to spin off a separate legacy package for the older systems.

[LN13uLL 5]

16 minutes ago, Luke said:

OK we had anticipated this might happen with very old devices. Our package used to bundle it's own version of glibc. We had to stop doing this for newer devices, so now it uses the one on the system, and the one on your system must be too old.

The only way for us to resolve it would be to spin off a separate legacy package for the older systems.

Thanks for providing the details. I suspected that too. I spend the whole day after my initial response and read another use with the same exact model and OS version which helped explain it. 
 

for now, I’m happy to stay on 4.8 as I don’t have any issues with that version. I have it back up and running in full force on that older stable version. 
 

what are your thoughts on spinning up a separate legacy package for older systems.  These NAS are running well even though it’s old so not sure how many others may run into this issue other than me and that other user on the forum. 

[Luke 42077]

Quote

what are your thoughts on spinning up a separate legacy package for older systems.

it's doable. Just a matter of when we can get to it.

[LN13uLL 5]

1 minute ago, Luke said:

it's doable. Just a matter of when we can get to it.

That’s understandable. No rush at this point since I have 4.8.X back up and running 100%.