hrfee/jfa-go
1
0
Fork 0
mirror of https://github.com/hrfee/jfa-go.git synced 2024-06-16 22:47:46 +02:00
Code Issues Projects Releases Wiki Activity

Updated Password Resets outside local network (markdown)

Harvey Tindall 2021-06-01 01:03:55 +01:00
parent ddbd310f6a
commit ca28031f94
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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://<jellyfin address>/Users/ForgotPassword` and `http://<jellyfin address>/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://<jellyfin address>/Users/ForgotPassword` and `http://<jellyfin address>/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***
```