From ca28031f940937bde29fa1ec5edfc3da57ca9bee Mon Sep 17 00:00:00 2001 From: Harvey Tindall Date: Tue, 1 Jun 2021 01:03:55 +0100 Subject: [PATCH] Updated Password Resets outside local network (markdown) --- Password-Resets-outside-local-network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Password-Resets-outside-local-network.md b/Password-Resets-outside-local-network.md index 5573133..74cc29d 100644 --- a/Password-Resets-outside-local-network.md +++ b/Password-Resets-outside-local-network.md @@ -1,4 +1,4 @@ -If you have Jellyfin set up to recognize connections from the LAN network, it will complain when a user tries to do a password reset remotely. If you're using a reverse proxy, Jellyfin knows the real IP of a user through the `X-Real-IP` HTTP header, which the reverse proxy should be adding automatically. If you want to allow password resets for remote users, you can selectively not add this header to the specific routes necessary, which are `http:///Users/ForgotPassword` and `http:///Users/ForgotPassword/Pin`. This way Jellyfin will see the IP of the reverse proxy, which should be on your local network. +If you have Jellyfin set up to recognize connections from the LAN network, it will complain when a user tries to do a password reset remotely. If you're using a reverse proxy, Jellyfin knows the real IP of a user through the `X-Real-IP`/`Host` HTTP headers, which common proxy configs include. If you want to allow password resets for remote users, you can selectively not add this header to the specific routes necessary, which are `http:///Users/ForgotPassword` and `http:///Users/ForgotPassword/Pin`. This way Jellyfin will see the IP of the reverse proxy, which should be on your local network. If the proxy isn't on the same network, you could maybe hardcode `X-Real-IP`/`Host` to a local address. ***Example NGINX config*** ```