Emby admin cannot access Jellyseerr

[cremonies 11]

This happened after the issue with spoofing the local IP was fixed. 
Emby is setup to be connect to host network. Jellyseer is setup to be on docker bridge network.
Emby Admin is not able to access Jellyseerr on local network anymore unless I Allow remote connections to this Emby Server for admin account.
172.20.0.2 is the jellyseerr bridge network IP. 
I would still like to be able to access jellyseerr without giving full external access to emby admin.

023-06-18 20:28:48.142 Warn Server: AUTH-ERROR: 172.20.0.2 - Forbidden.
2023-06-18 20:28:48.142 Error Server: Forbidden.
2023-06-18 20:28:48.142 Info Server: http/1.1 Response 401 to host1. Time: 1ms. http://192.168.1.2:8096/Users/AuthenticateByName
2023-06-18 20:28:48.918 Info Server: http/1.1 POST http://192.168.1.2:8096/Users/AuthenticateByName. Accept=application/json, Connection=close, Host=192.168.1.2:8096, User-Agent=axios/1.2.2, Accept-Encoding=gzip, compress, deflate, br, Content-Type=application/json, Content-Length=46, X-Emby-Authorization=MediaBrowser Client="Overseerr", Device="Axios", DeviceId="Qk9UX292ZXJzZWVycl9EYW5pZWxhZG1pbg==", Version="10.8.0"

[Luke 42077]

Hi. Have you customized any Emby server network settings?

 It looks like the server is setting those 192 addresses as being remote.

[cremonies 11]

3 hours ago, Luke said:

Hi. Have you customized any Emby server network settings?

 It looks like the server is setting those 192 addresses as being remote.

I do have the setting for external bandwidth setup. settings>network>lan Network = 192.168.1.1/24

Would this be making my 172.20.0.0 subnet appear as external and prevent jellyseerr from accessing using emby admin credentials?

[Luke 42077]

1 hour ago, cremonies said:

I do have the setting for external bandwidth setup. settings>network>lan Network = 192.168.1.1/24

Would this be making my 172.20.0.0 subnet appear as external and prevent jellyseerr from accessing using emby admin credentials?

It could be, yes. Try adding the 172 range to it as well.

[cremonies 11]

That's fixed it. I now have access locally and externally through jellyseerr while emby is still only directly accessible locally.

[YvonLandry 2]

I have the same problem.

I would like to know how to add the 172 ip range,  can you help?

[Luke 42077]

10 minutes ago, YvonLandry said:

I have the same problem.

I would like to know how to add the 172 ip range,  can you help?

HI there, can you please describe your issue in more detail? Thanks.

[YvonLandry 2]

Hi Luke,

I have the same problem that Cremonies had back in June "Emby admin cannot access Jellyseerr"

He said that he fix the problem by adding the 172 ip range to the lan network

[cremonies 11]

2 hours ago, YvonLandry said:

Hi Luke,

I have the same problem that Cremonies had back in June "Emby admin cannot access Jellyseerr"

He said that he fix the problem by adding the 172 ip range to the lan network

You perform the action on the emby server settings page. The previous post describe where to go to add the info.

Emby server admin access to settings>network>lan Network =

Add your subnet you used for jellyseerr.

Subnet has to be a custom bridge network on Synology else it cannot communicate with other networks. 

You also need to open firewall on Synology for docker containers.

[YvonLandry 2]

the container subnet is 172.18.0.0

 

I added the subnet to emby

then added the subnet to the firewall

and still no go

the log says that the Authentication request for admin has succeeded 

but Jellyseerr remain on the sign in page

 

 

Edited August 23, 2023 by YvonLandry
removed picture

[cremonies 11]

Instead of asking a bunch of questions, I'm going to tell you how mine is setup.

The big question though is are you trying to do all this through a reverse proxy while on your local network? Try doing it using jellyseer IP.

Try doing it with emby admin access turned on for outside your home network.

1. Emby is a docker container and on the host network. 

2. Jellyseer is on bridge network.

3. Jellyseer setup points to lan IP and port of emby.

A. Synology firewall allows jellyseer access.

B. Synology reverse proxy passes IP address.

C. Synology trusted proxy is set to its Lan IP.

D. Local dns server so I can use the domain name when at home.

 

[YvonLandry 2]

Sorry about this.

this is what I'm trying to do,

I have a DS720+ Synology NAS.

I have Emby installed on the NAS as an application not in a container.

I have installed Jellyseerr in a docker container using a bridge network

emby and jellyseerr are being used locally only.

 

hope this can help understand how I this setup

[Luke 42077]

Have you configured any Emby server network settings?

[cremonies 11]

3 hours ago, YvonLandry said:

Sorry about this.

this is what I'm trying to do,

I have a DS720+ Synology NAS.

I have Emby installed on the NAS as an application not in a container.

I have installed Jellyseerr in a docker container using a bridge network

emby and jellyseerr are being used locally only.

 

hope this can help understand how I this setup

Silly question but is this a first time set up or did it work in the past?

Do you have a composed file for the jellyseer?

Did you follow a guide specifically for Synology to set up jellyseer? 

[YvonLandry 2]

this is a first time set up, never work in the past

no compose file, but I have a CLI command.

docker run -d \
--name=fallenbagel-Jellyseerr \
-e LOG_LEVEL=debug \
-e JELLYFIN_TYPE=emby \
-e TZ=America/New_York \
-p 5055:5055 \
-v /volume1/docker/jellyseer/config:/app/config \
--network=dockernet \
fallenbagel/jellyseerr
 

this is the guide I used

https://mariushosting.com/how-to-install-jellyseerr-on-your-synology-nas/

 

[cremonies 11]

Where is your docker user puid and pgid?

Did you create the docker volume and assign it's permission to the docker user account?

 

[YvonLandry 2]

added the PUID and GUID

docker run -d \
--name=fallenbagel-Jellyseerr \
-e LOG_LEVEL=debug \
-e JELLYFIN_TYPE=emby \
-e TZ=America/New_York \
-e PUID=1026 \
-e PGID=100 \
-p 5055:5055 \
-v /volume1/docker/jellyseer/config:/app/config \
--network=dockernet \
fallenbagel/jellyseerr

 

still have the same problem, Jellyseerr remain on the sign in page

 

[cremonies 11]

Did you actually create a user in synology and the volume to link the container to?

You need to create the volume and a user in synology. Lookup how to create a docker user in synology and volume mapping.

If you did create a docker volume and folders for jellyseer, shutdown the container and delete the content in the folders.

You need to give the docker user you created full access to the docker volume

[YvonLandry 2]

Ok the problem has been resolved (almost).

the main problem was caused by my browser (Safari), I used chrome and all started to work properly.

I still had to add the network address 172.18.0.0/16 in emby under "LAN networks" to get every thing to work properly.

Now I just need to figure out why safari is not working with jellyseerr.

Thanks for all the help, really appreciated.

[Headfritz 8]

Hi, 

I'm seem to be having the same trouble as those above, I can't connect to emby with Jellyseerr. I have read though the above comments a couple of times and have followed their all their advice,  but I still can't seem to get Jellyseerr to connect with emby. 

I am running emby on my server with the app. not in a docker. I have in stalled Jellyseerr in a docker and it is running fine. I made the docker though container manager with the code fromfallenbagel/jellyseerr.  I have opened the firewall port for it and have I have my "LAN network in Emby set to 192.168.0.0/24, 172.18.0.0/16. and still it will not connect. I am at a lost as where to look and what switch I have failed to throw. It seem pretty straightforward, but yet I cannot connect. 

[Headfritz 8]

Just an update. 

I finally got Jellyseer to connect to Emby.  The above was good advice, but in the end DID NOT solve the issue. I ended up have to add additional code the Docker scrip. 

So that being said...... There it is. 

[Luke 42077]

2 hours ago, Headfritz said:

Just an update. 

I finally got Jellyseer to connect to Emby.  The above was good advice, but in the end DID NOT solve the issue. I ended up have to add additional code the Docker scrip. 

So that being said...... There it is. 

Hi, what code?

[Headfritz 8]

network_mode: host

 

[Luke 42077]

7 hours ago, Headfritz said:

network_mode: host

 

OK yes, using host networking mode will make things considerably easier with Docker.