No access to Emby on Asustor

[Mountainmanwyo 1]

I have all of the steps on this site and Asustor to try and get my Emby back up and working. For me the problem started when I lost my router and updated to the least Linnksys model MBE7000. After weeks I contacted Linksys to help fix the problem found out that that model dose not allow port forwarding. Last month got new router Archer AX80 now I can get back on the NAS but still cannot get on emby. The settings all say I should be able but nothing works. I have been working on this off and on for the last two days. Where should I look to change to get access back?

 

Asustor model 6510t

adm 5.0.0rin1

emby 4.9.0.70

[Luke 42077]

HI, what about inside your local network? Are you able to access the server there? That doesn't depend on port forwarding.

[Mountainmanwyo 1]

No I cannot access Emby at all.

[Luke 42077]

Is any emby server log file generated?

Emby Server Data Folder

[Mountainmanwyo 1]

Yes the SSH is Enable.

[DeniskaQ 0]

попробуйте сделать это

*updated 2022-03-04 for Asustor ADM 4.xxx, and provided a more detailed process with additional confirmation steps*

When reinstalling Emby server on my Asustor 5304, I had to complete these steps (via SSH terminal session to my NAS box) after uninstalling Emby (from AppCentral) and before reinstalling Emby:

Connect a teminal session via SSH to your Ausutor, login with an account that has admin permissions to your NAS - not an emby account or the emby user (see post below in this thread for using PuTTY to make a SSH connection to your NAS). Note that SSH must be enabled in Asustor Services->Terminal. Default port is 22.
type "ls /home/" without the quotes to see the list of user home folders, emby is the default name for the installed emby user, containing all the emby files/configs
type "rm -rf /home/emby" without the quotes to delete the emby folder
type "ls /home/" without the quotes to verify the emby user folder has now been deleted
type "cat /etc/passwd" without the quotes to view user accounts on your NAS, emby is the default name for the installed emby user
type "sudo /volume0/usr/builtin/sbin/userdel emby" without the quotes to delete the emby user account. You will be prompted to re-enter your password for the administrative account you logged in via SSH with.
type "cat /etc/passwd" without the quotes to verify the emby user has now been deleted
type "cat /etc/group" without the quotes to view user groups on your NAS, emby is the default name for the installed emby group
type "sudo /volume0/usr/builtin/sbin/groupdel emby" without the quotes to delete the emby group. You will be prompted to re-enter your password for the administrative account you logged in via SSH with.
type "cat /etc/group" without the quotes to verify the emby group has now been deleted
type "exit" without the quotes to end/exit your SSH
Also confirm you are connecting to the default port of 8096 (http://<yourNASIPaddress>:8096) after the re-install as your https:// certificate and any custom port numbers would need to be set up again if previously using https:// or custom ports. You can also check your Asustor firewall to ensure it is not blocking the Emby ports or the client device you are connecting with.

It likely wouldn't hurt to clear your cache on your browser also if it possibly has cached passwords from your previous config before the reinstall.

Edited March 4, 2022 by CJTripper

[Luke 42077]

6 hours ago, Mountainmanwyo said:

Yes the SSH is Enable.

Hi @Mountainmanwyodid you find a log file in the server data folder? Can you please attach it here? Thanks !

[Luke 42077]

Hi, please follow along this topic: 

Thanks.

[Mountainmanwyo 1]

This download didn't help me still have no access to Emby. I am have a 6510T. I am not sure how to get to the sever data file. 

[Luke 42077]

16 hours ago, Mountainmanwyo said:

This download didn't help me still have no access to Emby. I am have a 6510T. I am not sure how to get to the sever data file. 

Hi, what download exactly are you referring to?

[Mountainmanwyo 1]

That would be beta version 4.9.1.3.

[Luke 42077]

1 minute ago, Mountainmanwyo said:

That would be beta version 4.9.1.3.

What file did you download?

[Mountainmanwyo 1]

https://github.com/MediaBrowser/Emby.Releases/releases/download/4.9.1.3/emby-server-asustor_4.9.1.3_x86-64.apk

 

[Luke 42077]

Did the installation complete?

[Mountainmanwyo 1]

Yes it did.

[Luke 42077]

Hi, can you try the 4.9.1.4 beta package and see if that helps? Thanks.

[Mountainmanwyo 1]

OK I did the 4.9.1.8. I still cannot open emby. I have also contacted Asustor on this problem. waiting on reply. I am open to any other suggestion or a personal conversation about this problem.

 

[Luke 42077]

Hi, we are looking into it. Thanks.

[MadMeddler 1]

Just to throw my 2p in.

I'm on an older NAS (AS6204T) and received a very similar looking update from Asustor (4.3.3.RJH1) which I installed on Monday evening.

Upon restarting my other apps all behaved normally, but EmbyServer refused to start.

So the last logs I have are from before the update, nothing has run since.

I have tried upgrading to the latest beta downloaded from emby.media (4.9.1.9) - no joy
I have also completely uninstalled EmbyServer, removed the /home/emby folder and removed the emby user account
then I re-installed the version available from the AppCenter

So far as AppCenter is concerned it's installed and running, but there are no Emby processes running nor any logs.
The emby user account was re-created and the /volmain/.@plugins/AppCenter/emby-server folder is created again.

It just won't start the server service(s).

I had Asustor connect to my NAS this morning, but apart from them uninstalling a couple of apps (for which I didn't give them permission) nothing has changed.

@LukeIf can be any use in debugging, please let me know.

Edited July 23, 2025 by MadMeddler

[Luke 42077]

2 hours ago, MadMeddler said:

Just to throw my 2p in.

I'm on an older NAS (AS6204T) and received a very similar looking update from Asustor (4.3.3.RJH1) which I installed on Monday evening.

Upon restarting my other apps all behaved normally, but EmbyServer refused to start.

So the last logs I have are from before the update, nothing has run since.

I have tried upgrading to the latest beta downloaded from emby.media (4.9.1.9) - no joy
I have also completely uninstalled EmbyServer, removed the /home/emby folder and removed the emby user account
then I re-installed the version available from the AppCenter

So far as AppCenter is concerned it's installed and running, but there are no Emby processes running nor any logs.
The emby user account was re-created and the /volmain/.@plugins/AppCenter/emby-server folder is created again.

It just won't start the server service(s).

I had Asustor connect to my NAS this morning, but apart from them uninstalling a couple of apps (for which I didn't give them permission) nothing has changed.

@LukeIf can be any use in debugging, please let me know.

HI, so you're on ADM 4?

[MadMeddler 1]

Yep. 4.3.3 - was all fine until the recent update. The last update that I know worked is ADM 4.3.3.RH61.

 

[alucryd 315]

Can't reproduce here on 4.3.3.RJH1. Could you SSH into the NAS and run: `sudo -u emby /usr/local/AppCentral/emby-server/bin/emby-server` and paste the logs here?

[MadMeddler 1]

I get Permission denied when I try that command. Could you point me in the direction of the logs you're looking for?

The only logs I can see are the embyserver.txt files and they haven't updated since the firmware update

[MadMeddler 1]

Holy crapola!

I just ran your command but:

sudo -u root

Emby is back!

How can I get it back to running normally?

But so far, this is a huge improvement already.

Thanks

M

[alucryd 315]

You should not get a permission denied with the command I provided, this means permissions on the emby package files or program data files had been tampered with. Running as root is really not a good idea as it probably messed up permissions even further. Please stop the server,  run `sudo chmod -R emby:emby /home/emby`, and then try running the earlier command as emby again. If that works, you can reboot and the server should start as normal.