#All user's have same local IP?

1 messages · Page 1 of 1 (latest)

scarlet leaf
#

Hey,

New to all of this , especially networking, so please bare with me.

Tracearr supervised-v1.4.22 - Docker on UnRaid

I did have a toast or warning banner appear that I closed, i cant remember exactly the content but it was along the lines of all users having the same IP.
See attached, all current users say local network, however they are not. I don't particularly see this as a problem but i guess it limits features?

Users access jellyfin via domain (hosted with cloudflare) that is grey cloud (not orange cloud) and then routed to server IP in nginx proxy manager.

I have set the Nginx internal container ip in jellyfin "Known proxies" setting.

I have restarted jellyfin several times and the server, with no change.

In Nginx proxy manager i dont seem to have the option to change/add headers?

Likely im missing something?

naive trenchBOT
# scarlet leaf Hey, New to all of this , especially networking, so please bare with me. Trace...

Thanks for opening a support thread!
Please include the following so we can help:

Required Information

• Tracearr version
• Environment (Docker, LXC, Unraid, etc.)
• Docker compose file
• Logs (pastebin.com) or screenshots

Describe The Issue

• Expected behavior
• Actual behavior
• Steps to reproduce

Read The Docs

Docs · Logs · FAQ

toxic brook
#

Please look at the docs linked above, its covered there

scarlet leaf
stray arch
#

you need to add the headers in nginx proxy manager

toxic brook
stray arch
#

NPM only adds them if you use a custom location, otherwise you need to set them manually

#

source: years of pain with npm

toxic brook
#

lol i mean i know how npm works. You should read our docs 🙂 all straight from JF/Emby docs

scarlet leaf
#

Ill look more into nginx and how to edit headers.

Thanks guys

toxic brook
#

and contains everything you need to fix it. It is not a tracearr problem, its a misconfiguration of your media server and/or proxy