Password Resets

Password Reset Methods #

There are 4 main methods for facilitating password resets. They are ordered from (in my opinion, at least) worst to best, although your choice will depend on your situation.. They are described below:

Through Jellyfin (PIN Reset): The user clicks “Forgot Password” on the Jellyfin login screen, and enters their username. Jellyfin generates a file with a PIN code. Jfa-go reads this file, and sends the PIN to any contact methods associated with the user (Email, Discord, Matrix or Telegram). The user then types this PIN when Jellyfin asks for it.
Partially through Jellyfin (Link Reset): Similarly to above, the user clicks “Forgot Password” and enters their username. Jfa-go reads the file with the PIN, but instead sends the user a link that will automatically set their password to the PIN, as Jellyfin would if they typed it in.
Partially through Jellyfin (Internal Reset): Same as above, but the link sent to the user takes them to a special jfa-go password reset page.
Through Jfa-go (User Page/“My Account” Reset): The user visits the “My Account” page (your-jfa-go.site/my/account), and presses the “Forgot Password” button. They enter their Jellyfin username, or address/ID of a contact method (email address or discord/telegram/matrix username). A message with a link is sent, which links to the same password reset page described in method 2.

Pros/Cons #

Methods	Pros	Cons
PIN Reset	Initiated through Jellyfin	Can confuse user Jellyfin doesn't tell you to check email/discord/telegram/matrix for a message with a PIN. No way to enforce password requirements User's password is set to the PIN, user must set their new password through Jellyfin. Ombi Password will not change (if enabled)
Link Reset	User doesn't have to keep Jellyfin's Password Reset page open User doesn't have to type anything Reminds user to change their password after it resets to the PIN code Automatically changes password to PIN on Ombi	Same as above User will also have to manually change their Ombi password from the PIN
Internal Reset	Enforces password requirements Users are shown a page similar to the "Create Account" form New password is also applied to Ombi	Can confuse user in the same way as the above
"My Account" Reset	Performed in the same place as other account management tasks Explains itself better than other methods The page tells the user to check their inbox for a link	"My Account" page may not be familiar to user For this feature to be used, users must know the "My Account" page exists The page is already referenced on the signup form, but mentioning it on your Jellyfin instance or app portal might be a good idea.

Setting them up #

Prerequisite for Methods 1-3 #

jfa-go will need access to your Jellyfin config directory, as this is where it places the files containing PINs.

General Advice: When initiating a password reset in Jellyfin, a message will pop up telling you the location the PIN file was created in. This is the easisest way to find the directory. However, this feature was broken in older versions and still is for some.

PWR Directory Screenshot

Docker: The directory you mounted to /config in the container, e.g. for docker create ... -v /opt/jellyfin:/config, the config directory would be /opt/jellyfin.
- If you’re also running jfa-go in docker, make sure to mount it to /jf within the container; jfa-go should default to that path.
Windows: The directory should be C:\ProgramData\Jellyfin\Server or similar.
Ubuntu/Debian: Should be /var/lib/jellyfin, or one of it’s sub-directories. initiate a Password Reset and look for a file beginning with passwordreset to confirm.

Method 1 (PIN Reset) #

Enable Password Resets in settings, that’s all.

Method 2 (Link Reset) #

Enable Password Resets, and in the same section, enable “Use reset link instead of PIN”.

Method 3 (Internal Reset) #

Enable both the settings for the above 2 methods, and also enable “Set password through link”.

Method 4 (“My Account” Reset) #

Enable all of the settings listed above.
Enable the User Page feature.
Ensure Use Jellyfin for Authentication in General is enabled.
Note: Despite enabling the above features, jfa-go does not need access to the Jellyfin config directory if you only want this method to be used. You can point the directory to wherever, it doesn’t matter.