Jump to content

Connection refused after restore from backup on new install

Aldursil

By Aldursil
in Linux

 Share
Go to solution Solved by Aldursil,

Recommended Posts

Aldursil

Aldursil 15

Posted
Posted

Hello,

I recently had an issue with Emby which was running with Portainer so this gave me a good excuse to move away from Portainer and to docker-compose. I installed a new install using docker-compose with the image emby/embyserver_arm64v8 from https://hub.docker.com/r/emby/embyserver_arm64v8. The install went fine and I used the default port of 8096.

After the install I logged in and added my premium key to do a restore with the restore and backup plugin. Once I selected the backup and clicked Restore Backup I saw the circle indicator showing the restore was being processed.

After the restore was finished I refreshed the Emby web page and I am now getting a connection refused error.

Any idea what I can change so the connection will be accepted? I have attached several server logs files.

This install is on a Rasberry Pi 5.

embyserver.txt embyserver-63883814400.txt embyserver-63883796754.txt embyserver-63883796542.txt

Luke Emby Team

Luke 42077

Posted
Posted

HI, what address is in the  browser address bar?

Aldursil

Aldursil 15

Posted
  • Author
Posted
2 minutes ago, Luke said:

HI, what address is in the  browser address bar?

http://192.168.68.52:8096

I have several other services which are working with the same ip address but differnt port number so I know connectivity to the Pi is ok. Just seems like Emby does not like something now after the restore.

 

Luke Emby Team

Luke 42077

Posted
Posted

Are you sure the server is running?

Aldursil

Aldursil 15

Posted
  • Author
Posted
4 minutes ago, Luke said:

Are you sure the server is running?

Yes

~/docker/emby $ docker ps
CONTAINER ID   IMAGE                                  COMMAND                  CREATED        STATUS                PORTS                                                                                                NAMES
afce42b1e6cd   emby/embyserver_arm64v8                "/init"                  20 hours ago   Up 20 hours           1900/udp, 7359/udp, 0.0.0.0:8096->8096/tcp, [::]:8096->8096/tcp, 8920/tcp                            Emby
 

Luke Emby Team

Luke 42077

Posted
Posted

Are you able to access via localhost?

Aldursil

Aldursil 15

Posted
  • Author
Posted
2 minutes ago, Luke said:

Are you able to access via localhost?

No, but then nothing else I tried just now with localhost works either.

Luke Emby Team

Luke 42077

Posted
Posted
2 minutes ago, Aldursil said:

No, but then nothing else I tried just now with localhost works either.

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

Thanks!

 

Aldursil

Aldursil 15

Posted
  • Author
Posted
5 minutes ago, Luke said:

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

Thanks!

 

Sorry, I added the latest logs thinking that would help. Here is the log where the restore was done.

embyserver-63883794348.txt

Lessaj

Lessaj 467

Posted
Posted (edited)

From your earlier log it said the port was 8124.

As root user 

netstat -lnp | grep -i emby

 

Edited by Lessaj
Aldursil

Aldursil 15

Posted
  • Author
Posted (edited)
6 minutes ago, Lessaj said:

From your earlier log it said the port was 8124.

My Portainer  install was on 8124 and when that had an issue I tried to replicate using that port as well using docker compose. That did not work so I eventually tried to use the default port and then it worked. I have no idea why 8124 did not work.

I did try 8124 again and it does not work either.

Edited by Aldursil
Luke Emby Team

Luke 42077

Posted
Posted

When you restore it's going to restore everything, so if the config that you're restoring was set to different port numbers, then those are going to be applied.

Aldursil

Aldursil 15

Posted
  • Author
Posted
7 minutes ago, Luke said:

When you restore it's going to restore everything, so if the config that you're restoring was set to different port numbers, then those are going to be applied.

Ok, I changed my docker-compose to what I had in the backup and I still cannot connect.

Aldursil

Aldursil 15

Posted
  • Author
Posted

I verified what I had in the system.xml file in the backup to replicate that in the docker-compose file.

system.xml ports entry:

<?xml version="1.0"?>
<ServerConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <EnableDebugLevelLogging>false</EnableDebugLevelLogging>
 <EnableAutoUpdate>true</EnableAutoUpdate>
 <LogFileRetentionDays>3</LogFileRetentionDays>
 <RunAtStartup>true</RunAtStartup>
 <IsStartupWizardCompleted>true</IsStartupWizardCompleted>
 <EnableUPnP>true</EnableUPnP>
 <PublicPort>8196</PublicPort>
 <PublicHttpsPort>8920</PublicHttpsPort>
 <HttpServerPortNumber>8124</HttpServerPortNumber>
 <HttpsPortNumber>8920</HttpsPortNumber>
 <EnableHttps>false</EnableHttps>
 <IsPortAuthorized>true</IsPortAuthorized>
 

Docker compose ports

   ports:
     - "8124:8196/tcp"

I don't recall now why I had 8196 for the emby port but this had been working fine for many months. What initially started all this was my Pi had some system updates and then I started getting the "Forbidden" message. I had gotten kicked out of Emby and when trying to reconnect that is what was being displayed.

Luke Emby Team

Luke 42077

Posted
Posted

OK I would try manually changing everything back to the default ports.

Aldursil

Aldursil 15

Posted
  • Author
Posted
Just now, Luke said:

OK I would try manually changing everything back to the default ports.

Where do I need to change it?

I presume I will do this in docker-compose but how about system.xml? 

Is there anywhere else I need to change it?

Is the default 8096:8096?

Luke Emby Team

Luke 42077

Posted
Posted

Both. 8096 is the default http port.

Aldursil

Aldursil 15

Posted
  • Author
Posted
11 minutes ago, Luke said:

Both. 8096 is the default http port.

I changed System.xml and updated the docker compose file, re-created the container and still cannot connect.

Any new ideas on how to get this working?

docker ps
CONTAINER ID   IMAGE                                  COMMAND                  CREATED          STATUS                  PORTS                                                                                     
          NAMES
2707d73c5092   emby/embyserver_arm64v8                "/init"                  23 seconds ago   Up Less than a second   1900/udp, 7359/udp, 0.0.0.0:8096->8096/tcp, [::]:8096->8096/tcp, 8920/tcp                 
          Emby

image.thumb.png.40d09f0004e6c354a8575eebfc334283.png

Luke Emby Team

Luke 42077

Posted
Posted

Are you sure it’s reachable at that address?

Aldursil

Aldursil 15

Posted
  • Author
Posted
11 minutes ago, Luke said:

Are you sure it’s reachable at that address?

Yes, that is the ip address of the Pi and other services work with the same ip address but a different port number.

Aldursil

Aldursil 15

Posted
  • Author
Posted

I was working on a different container and noticed that Emby was crashing over and over with the latest changes.

Emby  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
Emby  | [s6-init] ensuring user provided files have correct perms...exited 0.
Emby  | [fix-attrs.d] applying ownership & permissions fixes...
Emby  | [fix-attrs.d] done.
Emby  | [cont-init.d] executing container initialization scripts...
Emby  | [cont-init.d] done.
Emby  | [services.d] starting services
Emby  | [services.d] done.
Emby  | Info Main: Application path: /system/EmbyServer.dll
Emby  | Info NetworkManager: Adding event handler for NetworkChange.NetworkAddressChanged
Emby  | Info Main: Shutdown complete
Emby  | [cont-finish.d] executing container finish scripts...
Emby  | [cont-finish.d] done.
Emby  | [s6-finish] waiting for services.
Emby  | [s6-finish] sending all processes the TERM signal.
Emby  | [s6-finish] sending all processes the KILL signal and exiting.
Emby exited with code 0
Emby  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
Emby  | [s6-init] ensuring user provided files have correct perms...exited 0.
Emby  | [fix-attrs.d] applying ownership & permissions fixes...
Emby  | [fix-attrs.d] done.
Emby  | [cont-init.d] executing container initialization scripts...
Emby  | [cont-init.d] done.
Emby  | [services.d] starting services
Emby  | [services.d] done.
Emby  | Info Main: Application path: /system/EmbyServer.dll
Emby  | Info NetworkManager: Adding event handler for NetworkChange.NetworkAddressChanged
Emby  | Info Main: Shutdown complete
Emby  | [cont-finish.d] executing container finish scripts...
Emby  | [cont-finish.d] done.
Emby  | [s6-finish] waiting for services.
Emby  | [s6-finish] sending all processes the TERM signal.
Emby  | [s6-finish] sending all processes the KILL signal and exiting.
Emby exited with code 0
Emby  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
Emby  | [s6-init] ensuring user provided files have correct perms...exited 0.
Emby  | [fix-attrs.d] applying ownership & permissions fixes...
Emby  | [fix-attrs.d] done.
Emby  | [cont-init.d] executing container initialization scripts...
Emby  | [cont-init.d] done.
Emby  | [services.d] starting services
Emby  | [services.d] done.
Emby  | Info Main: Application path: /system/EmbyServer.dll
Emby  | Info NetworkManager: Adding event handler for NetworkChange.NetworkAddressChanged
Emby  | Info Main: Shutdown complete
Emby  | [cont-finish.d] executing container finish scripts...
Emby  | [cont-finish.d] done.
Emby  | [s6-finish] waiting for services.
Emby  | [s6-finish] sending all processes the TERM signal.
Emby  | [s6-finish] sending all processes the KILL signal and exiting.
Emby exited with code 0
Emby  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
Emby  | [s6-init] ensuring user provided files have correct perms...exited 0.
Emby  | [fix-attrs.d] applying ownership & permissions fixes...
Emby  | [fix-attrs.d] done.
Emby  | [cont-init.d] executing container initialization scripts...
Emby  | [cont-init.d] done.
Emby  | [services.d] starting services
Emby  | [services.d] done.
Emby  | Info Main: Application path: /system/EmbyServer.dll
Emby  | Info NetworkManager: Adding event handler for NetworkChange.NetworkAddressChanged
Emby  | Info Main: Shutdown complete
Emby  | [cont-finish.d] executing container finish scripts...
Emby  | [cont-finish.d] done.
Emby  | [s6-finish] waiting for services.
Emby  | [s6-finish] sending all processes the TERM signal.
Emby  | [s6-finish] sending all processes the KILL signal and exiting.
Emby exited with code 0
Emby  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
Emby  | [s6-init] ensuring user provided files have correct perms...exited 0.
Emby  | [fix-attrs.d] applying ownership & permissions fixes...
Emby  | [fix-attrs.d] done.
Emby  | [cont-init.d] executing container initialization scripts...
Emby  | [cont-init.d] done.
Emby  | [services.d] starting services
Emby  | [services.d] done.
Emby  | Info Main: Application path: /system/EmbyServer.dll
Emby  | Info NetworkManager: Adding event handler for NetworkChange.NetworkAddressChanged
Emby  | Info Main: Shutdown complete
Emby  | [cont-finish.d] executing container finish scripts...
Emby  | [cont-finish.d] done.
Emby  | [s6-finish] waiting for services.
Emby  | [s6-finish] sending all processes the TERM signal.
Emby  | [s6-finish] sending all processes the KILL signal and exiting.
Emby exited with code 0
Emby  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
Emby  | [s6-init] ensuring user provided files have correct perms...exited 0.
Emby  | [fix-attrs.d] applying ownership & permissions fixes...
Emby  | [fix-attrs.d] done.
Emby  | [cont-init.d] executing container initialization scripts...
Emby  | [cont-init.d] done.
Emby  | [services.d] starting services
Emby  | [services.d] done.
Emby  | Info Main: Application path: /system/EmbyServer.dll
Emby  | Info NetworkManager: Adding event handler for NetworkChange.NetworkAddressChanged
Emby  | Info Main: Shutdown complete
Emby  | [cont-finish.d] executing container finish scripts...
Emby  | [cont-finish.d] done.
Emby  | [s6-finish] waiting for services.
Emby  | [s6-finish] sending all processes the TERM signal.
Emby  | [s6-finish] sending all processes the KILL signal and exiting.
Emby exited with code 0

 

Aldursil

Aldursil 15

Posted
  • Author
Posted (edited)

@Luke

Any idea what I can try next to get this working?

Edited by Aldursil
Luke Emby Team

Luke 42077

Posted
Posted

I’m not sure. Maybe try deleting the system.xml file and see if that gets you in.

Aldursil

Aldursil 15

Posted
  • Author
Posted
59 minutes ago, Luke said:

I’m not sure. Maybe try deleting the system.xml file and see if that gets you in.

I cannot do that while the docker container is constantly crashing now. I will have to start over with the docker compose install.

Luke Emby Team

Luke 42077

Posted
Posted

Ok please let us know how things go. Thanks.

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
Go to topic listing
×
×
  • Create New...