Connection refused after restore from backup on new install

[Aldursil 15]

13 minutes ago, Luke said:

Ok please let us know how things go. Thanks.

I could not get the official docker image to work. I had removed the crashing container with docker compose down and then re-created it and it still kept crashging so I switched to this  image from here: https://docs.linuxserver.io/images/docker-emby/. I tried using the old ports of 8124:8196 so when I did the restore there would be no coflict. I could not connect with this. I then switched back to the default ports of 8096 and now I am getting the "Forbidden" message.

Do you know how to get past this error? This was what was originally the issue with my other docker container on Portainer.

[Luke 42077]

I don't know. I would try a fresh start with a fresh data folder and not restore anything from the backup.

[Aldursil 15]

4 minutes ago, Luke said:

I don't know. I would try a fresh start with a fresh data folder and not restore anything from the backup.

I'm not sure what you mean about a fresh data folder. At this point I am  not pointing to any data at all. I just want to get back to Emby working in the UI and then I can go from there. Do you know how to fix the "Forbidden" error?

What I don't understand is why this started happening in the first place. Emby has been working for many months if not more than a  year with no problems. I think this all started occuring after I applied some updates to the Pi.

[Luke 42077]

2 minutes ago, Aldursil said:

Do you know how to fix the "Forbidden" error?

 

Not yet because I don't know why it's happening. It is obviously not normal for a brand new install - assuming this is a brand new install as you're saying it is.

[Aldursil 15]

Is there anybody else who can help me look into this?

[Luke 42077]

There's obviously something environmental happening on your server machine. I don't know what that is so that is why I don't have a solution at this point. 

But one thing i can suggest is that each time you attempt something and retry, please attach the latest server log. Maybe at some point we'll spot something.

It should also go without saying, the ports in your docker compose should match emby server. In situations like this, it is best to stick to defaults. And make sure there is no other software present that is attempting to use the same port numbers.

[Aldursil 15]

I don't know what casued the initial problem but the reason I was getting the "Forbidden" error was because in the new install I did not enable "Allow remote connections to this Emby Server.". Once I enabled that I was able to connect with all the devices I had connected previously.

 

[Luke 42077]

Ah yes that’s a typical reason for causing this however I did not bring it up because normally you’ll see the request rejections in the server log.