Need a bit of clarification

[nylimited]

Hello,

The new user is back with another question. :) This is not a bug report since I am uncertain how this should work. I am attempting to allow my (non-admin) users to change their own email addresses via the /my/account interface and hoping to trigger a verification email. This is not happening. Note that I have changed the My account subpath to "/" and the admin to "/admin" (without the quotes.)

Question 1:

When a non-admin user logs on via the My Account interface they are allowed to change their email, as expected. However the spinner never stops. If I click on the screen the spinner will be removed and the email address has been changed. There is no verification email attempt made. The log shows:

[INFO] 12:47:04  Authenticated with Jellyfin @ "http://192.168.1.50:8096"
[INFO] 12:47:04  Started Housekeeping daemon
[INFO] 12:47:04  Started Backup daemon
[INFO] 12:47:04  Started User daemon daemon
[INFO] 12:47:04  Started PWR daemon
[INFO] 12:47:04  Initializing router
[INFO] 12:47:04  Loading Routes
[INFO] 12:47:04  Loaded @ "0.0.0.0:8057"
[GIN] GET(/admin/settings) => 200
[GIN] GET(/css/v0.6.0bundle.css) => 304
[GIN] GET(/css/remixicon.css) => 304
[GIN] GET(/js/admin.js) => 304
[GIN] GET(/banner.svg) => 304
[GIN] GET(/lang/admin) => 200
[INFO] 12:47:20  Token requested (refresh token) (ip=192.168.1.166)
[GIN] GET(/token/refresh) => 400
[GIN] GET(/) => 200
[GIN] GET(/css/v0.6.0bundle.css) => 304
[GIN] GET(/css/remixicon.css) => 304
[GIN] GET(/js/user.js) => 304
[GIN] GET(/lang/user) => 200
[INFO] 12:47:41  Token requested (userpage refresh token) (ip=66.31.204.233)
[GIN] GET(/my/token/refresh) => 400
[GIN] GET(/fonts/hanken-grotesk-v8-cyrillic-ext_latin_vietnamese-regular.woff2) => 304
[GIN] GET(/fonts/hanken-grotesk-v8-cyrillic-ext_latin_vietnamese-700.woff2) => 304
[INFO] 12:48:04  Checking for user expiry
[INFO] 12:48:15  Token requested (userpage login attempt) (ip=66.31.204.233)
[GIN] GET(/my/token/login) => 200
[GIN] GET(/my/details) => 200
[GIN] GET(/fonts/hanken-grotesk-v8-cyrillic-ext_latin_vietnamese-500.woff2) => 304
[GIN] GET(/css/remixicon.woff2?t=1734404658139) => 304
[INFO] 12:48:35  Email for user "e1087a30f0684be0a7d87105579e73e7" adjusted
[GIN] POST(/my/email) => 303
[GIN] GET(/my/) => 404
[INFO] 12:49:04  Checking for user expiry

The above looks to me like the email address is being changed in the database and, near the end, the POST and GET requests look to overlook my change from "my/account" to "/" but I remain uncertain.

So, the question is if jfa-go should/can be doing verification of an email change. I do have the verify template but should that be used at this point? Or, did I simply miss something in the setup that is making the verification be skipped?

The second part of that question is how do I get the spinner to clear properly?

Question 2:

I was attempting to use Ombi integration and, yes, I understand it is spotty. Since I use Ombi only for the newsletter function most other parts (like password) are unimportant to me. Creating a new user from an invitation works very much as expected in Jellyfin, jfa-go and also ombi.

But email change does not translate to Ombi. Perhaps due to the issues described above whereas the spinner does not end naturally. Alternately, all the old Ombi users were originally created manually. I am guessing that jfa-go does not have their user id and may be attempting to change the user data based on that, not the user name.

The simple answer, of course, is to disable Ombi integration. The question is could jfa-go make Ombi changes based soley on user name or could it also import the user tokens or Ids from Ombi? Not nearly as important a question as #1 above.

Thank you for your time! Appreciate any help you may offer.

[hrfee]

For the first one, there were some CSS issues that might've meant the confirmation required message didn't show but nothing I saw that would stop it sending the message. A redirect was also meant to happen when email confirmation is disabled which would cause the page to reload, but the URL was broken when you had an empty "My Account" path set. That should be fixed now. Could you try again, and is there anything in the logs of jfa-go, or the javascript console when you press the button?

[hrfee]

Also let me know if any of the changes have fixed the second issue, or if changing the email address on the admin page doesn't change it in ombi. If it's still broken i'll re-install ombi and have a look. Also, it correlates Jellyfin and Ombi users by their username first and email address second, so there shouldn't be any issues finding users.

[nylimited]

Thanks for the quick response!

Updated my docker version with "unstable" dated 16Dec. A definite difference but .. logging in as a non-admin user and changing the email is near instant now. No spinner at all (or so fast I missed it). Email address was changed but no email was sent via smtp.

The "/" for /my/account? now looks fine in the log I think.

Now, this may well be intentional in this version. Still, my thought was that the original email would remain on the account till the new one was verified... jfa-go might want to send a notification to the old/original email asking if changing to the new one is okay. Any other notification would compromise the process. Please let me know if this is not the intended process flow.

The log shows Ombi failure since I that user did not exist in Ombi at that time. I will manually add the test user and run a test with Ombi.

[GIN] GET(/profiles/names) => 200
[GIN] GET(/invites) => 200
[INFO] 21:53:37  Checking for user expiry
[GIN] GET(/profiles/names) => 200
[GIN] GET(/invites) => 200
[GIN] GET(/profiles/names) => 200
[GIN] GET(/invites) => 200
[INFO] 21:54:37  Checking for user expiry
[GIN] POST(/my/email) => 400
[ERROR] 21:55:11 api-users.go:1204: Failed to set email address for Ombi user "8ef5da3703bb465d9612149a4cbbfd9e": not found
[INFO] 21:55:11  Email for user "8ef5da3703bb465d9612149a4cbbfd9e" adjusted
[GIN] POST(/my/email) => 303
[GIN] GET(/) => 200
[GIN] GET(/my/details) => 200
[INFO] 21:55:37  Checking for user expiry

[nylimited]

The second test with Ombi failed as you can see from the log. The test user was added manually to Ombi hence jfa-go would not have known about yet.

[ERROR] 22:08:07 api-users.go:1204: Failed to set email address for Ombi user "8ef5da3703bb465d9612149a4cbbfd9e": not found
[INFO] 22:08:07  Email for user "8ef5da3703bb465d9612149a4cbbfd9e" adjusted

[nylimited]

If it's still broken i'll re-install ombi and have a look.

Keep in mid that my Ombi installation does very little - it exists only to email newsletters - and nobody has direct access to it from the WAN side. If it would help you I'll setup an account for you on jfa-go so you can test as much as you want.

[hrfee]

The page should say "Email confirmation required" and send an email to the new address, but it looks like the code path for it is not running. To confirm:

• Settings > Integrations > Email > Email Confirmation > Enabled is checked,
• Settings > Integrations > Email > Method is not empty (i.e. set to SMTP or Mailgun),
• Settings > Messages/Notifications > Enabled is checked

for the ombi integration, i'll do some testing myself and let you know if I need anything.

[nylimited]

Oooo .. I am losing my touch! I totally missed the first enabled check mark. Seems once I got past SMTP my brain assumed the rest is something I am not using. Apologies for making you do that lookup. It is, indeed, working as intended!

Thank you and no rush. Take some time off. Wishing you a very Happy Christmas and a relaxing break after 2025. Here’s to exciting new adventures in the New Year.

Cheers!

[hrfee]

Thank you, I suppose i should allow settings to have multiple dependencies in the UI so it can only show when Messages are enabled -and- email is setup.

Finding an ombi user seems to work for me, does changing the email address not work for any user, or is it specifically one? if so, is there anything unique about the username? i.e. accents, capitalization or whitespace.

[nylimited]

My Ombi users were all created either manually in Ombi by an Ombi admin or imported by Ombi from Jellyfin. Most user names are all lower case, a few have the first letter in upper case. Nearly all have never logged into Ombi and most have Newsletter selected. I was working with a testuser (all lower case in all systems). Tried a minute ago with my admin account which has "Andy" in JFA-GO but "andy" in Ombi. The only thing in common between the two users is that they are both shown in Ombi as "Local user" not "Jellyfin user".

If it'd help I can turn on debug in setup and/or add the -debug switch to the Docker RUN command and run the test again.

The first ERROR in the log seems to show a problem on sending the email but the email was, in fact, sent and received. Ombi user names are all alpha.

[INFO] 10:38:06  Token requested (userpage refresh token) (ip=192.168.1.166)
[GIN] GET(/my/token/refresh) => 400
[INFO] 10:38:13  Token requested (userpage login attempt) (ip=192.168.1.166)
[GIN] GET(/my/token/login) => 200
[GIN] GET(/my/details) => 200
[INFO] 10:38:24  Checking for user expiry
[GIN] POST(/my/email) => 400
[ERROR] 10:39:01 api-userpage.go:273: Sent confirmation email for "bb41857b4c5e4021bb25fd2c135e7f79" to "aksubs@gmx.co.uk"
[GIN] POST(/my/email) => 401
[INFO] 10:39:24  Checking for user expiry
[ERROR] 10:39:29 api-users.go:1204: Failed to set email address for Ombi user "bb41857b4c5e4021bb25fd2c135e7f79": not found
[INFO] 10:39:29  Email for user "" adjusted
[GIN] GET(/my/confirm/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJlbWFpbCI6ImFrc3Vic0BnbXguY28udWsiLCJleHAiOjE3NjYxNjIzMzksImlkIjoiYmI0MTg1N2I0YzVlNDAyMWJiMjVmZDJjMTM1ZTdmNzkiLCJ0YXJnZXQiOjAsInR5cGUiOiJjb25maXJtYXRpb24iLCJ2YWxpZCI6dHJ1ZX0.Mm2j2ULYC0LXGATrE94z4h8jG0aDSea_zY-vjUvVxQc) => 303
[GIN] GET(/) => 200
[GIN] GET(/css/v0.6.0bundle.css) => 304
[GIN] GET(/css/remixicon.css) => 200
[GIN] GET(/js/user.js) => 200
[GIN] GET(/lang/user) => 200
[INFO] 10:39:29  Token requested (userpage refresh token) (ip=66.31.204.233)
[GIN] GET(/my/token/refresh) => 400

[hrfee]

The log line mistakenly goes to the error log rather than the info log, i'll fix that. I can put up a temporary build which logs the process of finding an Ombi user to see what's happening, i'll put it on hrfee/jfa-go:issue455debug, ill assume you're using an x86 machine but let me know if you need an arm version.

[hrfee]

actually i think i found something, the new email gets written to the DB, then the search for the ombi user happens, looking for that new address rather than the existing one. Once that build is done could you try it?