Jump to content

Emby refused connection


CasaWongo
 Share

Recommended Posts

CasaWongo

Hi,

I have an Asustor AS1004T v2 and I was able to installed the Emby Server from App Central and it was working fine for awhile. I then had to reconfigure my drives and recreate my volumes. But after I reinstalled the Emby server I got the error 192.168.0.XX refused to connect. I removed and reinstalled the app and I also tried the beta version for this NAS and it still giving me the same error. Please let me know what I can do to troubleshoot this? Thanks

Link to comment
Share on other sites

CJTripper

*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:

  1. 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.
  2. 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
  3. type "rm -rf /home/emby" without the quotes to delete the emby folder
  4. type "ls /home/" without the quotes to verify the emby user folder has now been deleted
  5. type "cat /etc/passwd" without the quotes to view user accounts on your NAS, emby is the default name for the installed emby user
  6. 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.
  7. type "cat /etc/passwd" without the quotes to verify the emby user has now been deleted
  8. type "cat /etc/group" without the quotes to view user groups on your NAS, emby is the default name for the installed emby group
  9. 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.
  10. type "cat /etc/group" without the quotes to verify the emby group has now been deleted
  11. 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 by CJTripper
Updated process for ADM 4.xxx Asustor update
  • Like 1
Link to comment
Share on other sites

  • 1 month later...
bdub44

Hi,

I'm having the same issue. When i follow these steps more specifically userdel emby  i get the message "cannot lock etc/passwd try again later"

Edited by bdub44
Link to comment
Share on other sites

tisron13

Hi,

I've been having the same problem, after deleting a folder too many in Emby. I can say the solution by CJTripper worked. 

I did a search in asustor's knowledge base, with "How to ssh into my ASUSTOR NAS" being the search terms. The result is the 8th one in the list of finds. Click on that and you will find the means to follow CJTripper's solution, and perhaps may help others, who have the this problem, and like me, not too tech savvy. I've attached a screen shot which should help.

I now have Emby working again

Kindest regards,

Ronnie

 

Screen Shot 2021-05-19 at 15.10.17.png

Edited by tisron13
Link to comment
Share on other sites

CJTripper

1. ensure Emby has been uninstalled in AppCentral

2. ensure you are logging into your SSH console with an administrative account (such as "root" mentioned above).

3. try sudo in front of your command line commands to escalate permissions

4. if still getting lock errors, maybe retry a reboot of your NAS

5. if still getting errors, look for any other apps/services you may have installed that may be interacting with the NAS user accounts/groups, and turn them off also while deleting the emby user.

Link to comment
Share on other sites

bdub44

Thanks to you both CJTripper & tisron13

Got it working putting sudo in front of the command in ssh did the trick.

Thanks Again,

Bdub44

Link to comment
Share on other sites

  • 4 months later...
On 19/05/2021 at 18:15, bdub44 said:

Thanks to you both CJTripper & tisron13

Got it working putting sudo in front of the command in ssh did the trick.

Thanks Again,

Bdub44

Finally, this worked for me! Nice one mate.

Link to comment
Share on other sites

  • 3 months later...
On 1/18/2022 at 8:59 PM, Alfa19 said:

Buenas noches amigo el ip no me coje e intentado muchas veses

Hi there, can you please describe your issue in more detail? Thanks !

Link to comment
Share on other sites

  • 1 month later...
KbtheReturn

Hi there.

I'm really hoping someone can help me...After changing my system http and https port numbers from the default I'm no longer able to open my Emby. 

I tried CJTripper's steps to the letter, multiple times without success because everytime when I type "sudo userdel emby" the output reads "sudo: userdel: command not found, and the same supplies when I type sudo groupdel emby.

I also tried typing both commands without adding sudo in front but the output reads "groupdel: cannot remove the primary group of user 'emby' "

Prior to deleting Emby my "Manual Connect" port forwarding rules is still on the default 8096 & 8920 ports set, but still nothing allows me to get onto Emby. Even adding my wan address I still can't get the server running.

Besides performing a factory reset I really don't know what else I can do to fix this. My Asustor is running the latest 4.0.4.RR23 update.

Link to comment
Share on other sites

CJTripper

I am still on 4.0.4.RQO2, I haven't installed the RR23 update yet...you have me nervous about it now! Maybe I'll be brave and run the update tonight...

Can you confirm that the account you are using when logging into your SSH session is a member of the administrators group on your Asustor?

Also please confirm that you changed the http & https port numbers in the Emby server manager (specific to Emby connections)? Did you also change the http & https ports for your NAS web access (default 8000 and 8001) and can you still connect to your NAS web interface? And please confirm that they are not the same ports for both your NAS web access and Emby access, they need to be different.

Link to comment
Share on other sites

KbtheReturn

Hi CJTripper

Thank you so much for your quick reply. I'm also not a fan of updating when there doesn't seem top be anything to fix, but I think I know why you're also nervous ;) I think so long as your main Admin group doesn't have the "admin" username and the default ports you should be fine - nothing seems broken; but maybe that's why your commands of userdel and groupdel worked, because you're on older firmware?

Anyway, yes, I am logging in as a member of the admin group. I even re-enabled my default "admin" username and tried your steps again but still no luck.

So even before posting today, I deleted all the installable apps from app central from both my "admin" username and my substitute to the admin username which still had admin group privileges. I then reinstalled them again, checked my port forwarding and "app privilege" rules to make sure Emby and it's default ports were included but still no luck.

*Also please confirm that you changed the http & https port numbers in the Emby server manager (specific to Emby connections)? [I can't even log into Emby to do this] Did you also change the http & https ports for your NAS web access (default 8000 and 8001) and can you still connect to your NAS web interface? [Yes, and yes] And please confirm that they are not the same ports for both your NAS web access and Emby access, they need to be different. [I confirm they are different; NAS ports are unique, ie not default 8000 & 8001, and Emby ports are the defaults provided by the app central installation - I even tried a manual install but still no win]*

Link to comment
Share on other sites

CJTripper

My "admin" account was disabled when I initially set up the NAS a year ago, I use a different account that is a member of the Administrators group to administer my NAS. 

I just tested with a SSH session on my version Asustor with 4.0.4.RQO2, same error when using sudo with groupdel and userdel, so the sudo issue has existed at least since 4.0.4.xxxx, maybe even since 4.x was released in Oct 2021. It seems to be a path issue when using sudo. Try the full path instead with the sudo command: sudo /volume0/usr/builtin/sbin/userdel

That seems to resolve the "command not found" error. Let us know if that works for you also.

BTW, if you need to confirm your Emby ports without the availability of the web interface, mine are in the file located at Vol_1\home\emby\config\system.xml. I can't recall if that is a default path or if I customized it during install, but you will have a system.xml file somewhere.

Link to comment
Share on other sites

KbtheReturn

Hi CJTripper

Your solution looks promising, as soon as I'm able to ssh into my NAS I'll give it a try and give an update. Many thanks!

Link to comment
Share on other sites

CJTripper

FYI, I just updated my NAS to 4.0.4.RR23 (I always shutdown Emby in the Emby server manager dashboard and also in Asustor App Central before an Asustor ADM update). After the reboot, I changed my NAS default system web interface ports to non-default ports, ensuring they did not conflict with any other ports in use on the NAS. I also updated my Emby server version from 4.7.0.28 Beta to 4.7.0.29 Beta. After the Emby update, I launched the Emby server manager and restarted the Emby server (I read somewhere this should be done after an Emby update is installed). Everything worked successfully, but I did notice that Emby seemed to take a longer time than usual to restart on that last Emby server restart. Maybe I was just being overly observant this update and it really wasn't any longer than usual, but be sure to give it 3-5 minutes before you panic. I did not make any changes to my Emby server http and https ports, they remain as the default 8096 & 8920.

Anyways, everything seems to be working OK so not sure why you lost your Emby web access when you did your NAS upgrade to 4.0.4.RR23 and changed your NAS system web interface ports to non-default ports.

I did note when previously upgrading from Beta 4.7.0.26 to Beta 4.7.0.28, my Live TV M3U tuners didn't seem to be recognized or load a guide. I just edited and re-saved the TV source for each M3U tuner then they properly initialized and downloaded the guide. The upgrade from Beta 4.7.0.28 to 4.7.0.29 did not require me to "re-initialize" the M3U tuners, they migrated successfully without any intervention.

Link to comment
Share on other sites

KbtheReturn

@CJTripper... Bless you a million times over. You're a lifesaver and honestly a genius, and your additional information from your last post - invaluable! It seems like you didn't even break a sweat figuring out what was wrong :D 
You're the best - thank you so much!

Link to comment
Share on other sites

CJTripper

Glad that worked for you. I am certainly not a linux expert, but have been learning lots more since getting this Asustor NAS! I have learned many things about Asustor and Emby the hard way by breaking stuff then spending hours on web forums and internet searches figuring out how to fix it. Posts from others have taught me lots so I figure it is my duty to share my experiences and info also. I guess knowledge sharing is the whole idea of the forums, they have saved me a few times as well! :) 

Link to comment
Share on other sites

  • 2 months later...

@cjtripper

This solved my problem. I didn't see an Emby user on the first ls, but there was a hit on the cat /etc/passwd. I just went through the whole script and after refreshing the page it worked. The initial browser page load reproduced the error, but within a second or two the connection was open on port 8096.

I've no idea how much time I could have spent looking into this if you hadn't written this very specific little piece. So thanks a lot!

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

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
 Share

×
×
  • Create New...