Setup - jfa-go

Welcome!

You'll need to do a few things to set up jfa-go. Press start to continue.

Language

Default admin language

Default account creation language

Default email language

General

Listen Address Port

Use HTTPS

Only recommended if you aren't using a reverse proxy.

Path to certificate Path to key file Updates

Enabled

Update Channel

HTTPS Port URL Base (Optional)

Only needed if using a reverse proxy on a subfolder (e.g 'jellyf.in/accounts').

External jfa-go URL (Required)

The URL you'll be accessing jfa-go from. Used to generate links for things like password resets. Make sure to include the above URL base if you set one.

Theme

Proxy

Have jfa-go make all connections through a HTTP/SOCKS5 proxy. Connection to Jellyfin will be tested through this.

Enabled

Protocol

Address (Including Port) Username Password

Login

To access the admin page, you need to login with a method below:

Authorize with Jellyfin/Emby: Login details are shared with Jellyfin, which allows for multiple users.

Admin users only (recommended)

Allow all Jellyfin users to login

Not recommended, you should allow individual users to login once setup.

Username and Password: Manually set the username and password.

Using this will disable the "User Page" feature.

Username Password Email Address (Optional) Your email address can be used to receive notifications.

Jellyfin/Emby

An admin account is needed because the API does not allow user creation using an API key. You should create a separate account and check 'Allow this user to manage the server'. You can disable everything else. Once done, enter the login details here.

Server Type

Emby support is limited and does not support password resets.

Server name (Optional)

If given, this will replace any occurrence of 'Jellyfin' in the app.

Username Password

Server Address (Internal) Server Address (External)

Leave blank to use the same address.

Ombi

By connecting to Ombi, both a Jellyfin and Ombi account will be created when a user joins through jfa-go. After setup is finished, go to Settings to set a default profile for new ombi users.

Enabled

Server Address API Key

Find this in the first tab of Ombi settings.

Jellyseerr

Jellyseerr is an alternative to Ombi, and integrates with jfa-go slightly better. Again, after setup is finished, go to Settings to create a profile and add a template for new Jellyseerr accounts.

Enabled

Server Address API Key

Import existing users

If enabled, your existing users will have contact details and preferences from jfa-go synchronized.

User Page

The user page (shown as "My Account") allows users to access information about their account, such as their contact methods and account expiry. They can also change their password, start a password reset, and link/change contact methods, without having to ask you. Additionally, customized Markdown messages can be shown to the users before and after logging in.

Click the edit button next to "User Page" in settings to set them later.

Enabled

Log-in to jfa-go via Jellyfin must be set. Ensure "reset password via link" is selected later for self-service password resets.

Messages

Enabled

Date Format

24h Time

12h Time

Email

Sending method

Use email addresses as username

If enabled, new users will login to Jellyfin/Emby with their email address instead of a username.

From Address Sender Name

SMTP

Encryption

Server Address Port Username Password

Mailgun

API URL API Key

Admin Notifications

If enabled, you can choose (per invite) to receive a message when an invite expires, or a user is created. If you didn't choose the Jellyfin login method, make sure you provided your email address, or add another contact method later.

Enabled

Welcome messages

If enabled, a message will be sent to new users with the Jellyfin/Emby URL and their username.

Enabled

Email Subject

Invite Messages

If enabled, you can send invites directly to a user's email address, Discord or Matrix user. Because you might be using a reverse proxy, you need to provide the URL invites are accessed from. Write your URL Base, and append '/invite'.

Enabled

Email Subject

Password Resets

When a user tries to reset their password, Jellyfin creates a file named 'passwordreset-*.json' which contains a PIN. jfa-go reads the file and sends the PIN to the user. If you enabled the "User Page" feature, a reset can also be performed there, given a username, email, or contact method.

More information about the different ways of resetting passwords can be found on {n}.

Enabled

Path to Jellyfin configuration directory

If you don't know where this is, try resetting your password in Jellyfin. A popup with '<path to jellyfin>/passwordreset-*.json' will appear. This is not necessary if you only want to use self-service password resets through the "User Page".

Send a link instead of a PIN

If Ombi integration is enabled, use this to sync Jellyfin password resets with Ombi. Required for self-service password reset on the User Page.

Set password through link

Enabling this means the user doesn't have to change their password from the PIN after the reset. Password validation will also be enforced.

Default reset link language

Email Subject

Password Validation

If enabled, a set of password requirements will show on the account creation page, such as minimum length, uppercase/lowercase characters, etc.

Enabled

Length Uppercase characters Lowercase characters Numbers Special characters (%, *, etc.)

Help Messages

These messages will display in the account creation page and in some emails.

Contents of some emails, pages and messages can be customized further with markdown in Settings.

Contact Message

Displays at the bottom of all pages except admin.

Help Message

Displays on the account creation page.

Success Message

Displays when a user creates their account.

Finished!

Tons more features like Discord/Telegram/Matrix bots and custom Markdown messages can be found in Settings, so make sure to give it a browse. Click below to restart, then access jfa-go at one of the given internal/external URLs. If it doesn't load, check the application's logs for any clues as to why.