User profile page is not found (404) - emails not showing

I am just seeing now, that she is not the only one - Someone created a topic on my forum about it:

Are you on the latest version of Discourse? Please update to latest if you are not.

Are you running any third-party plugins?

I’m using the latest. I’m running:

Retort is a possible source, I guess? You could try quickly rebuilding with retort disabled and see if that helps?

I disabled it, then did ./launcher rebuid app - but still the same.
Is it enough to disable from the web interface or should I comment out the line in app.yml?

EDIT: Commented retort out in app.yml and rebuilt again - same thing :frowning:

2 Likes

This is a weird one maybe you can look into it Monday @dax?

There is nothing obvious about the reason why the profiles of these 2 users returning a 404 error. Can you check the site logs and see if you find something relevant when you click on their avatars?

I’m experiencing the same issue on some old accounts as well: I can access the admin page, but the email field won’t show, and the user profile returns a 404. I have an unconfirmed suspicion that this is somehow caused by usernames that are identical except for an underscore (in my case ‘MissB’ and ‘Miss_B’ - the underscore is a remnant from a vBulletin import). Both accounts had this issue, but on one of them it has since disappeared (the one with the underscore is still having the same problem).

I can see there are a smokyblue and a smoky_blue - there were also a Pro_Vapes user that had the issue, but his profile works now?!

I found another one, MixedUp (now called MixedUp1?) And Vapemixer is another user.

image

They’re easy to spot with that avatar …

Jyst FYI - I am using SSO.

Oh, so maybe SSO is interfering here and changing the state of the accounts somehow?

Migrated accounts from previous software that are not active is a different issue @bartv

I don’t think that’s the issue here - the MissB account was created after the migration (sorry, I wasnt’ specific there).

So:

  • MissB - created after migration
  • Miss_B - created before migration

When I rename MissB to MissBTest I can show the email and user profile. When I rename it back, the problem returns (also, MissB can’t log in with his username, logging in with email worked or reset his password).

Why not? Do the emails not match on the account? For old migrated accounts, as long as you control the email associated with the account, you should be able to get back in.

MissB is not a migrated account. Apparently he could not log in using a username+password, but he finally did succeed with email+password.

I have a sneaking suspucion that some username lookup returns > 1 results when usernames only differ by one _ character, and that this breaks things.

1 Like

So you think this is related to having two nearly identical usernames? :thinking:

@daath is this also a pattern in your examples? Near identical usernames and duplicate accounts?

1 Like

Hard to tell - I don’t think the nearly identical usernames is the reason in one of the cases, but then again, his profile suddenly works again.

When Discourse detects a username from my main site that clashes it just named it “UsernameX” where X is the next available number that makes an available username (my main site doesn’t have usernames, but display names that doesn’t need to be unique).

My feeling is that something else is going on, but I can’t spot what it is. The accounts I’ve spotted were all over a year old though.

The problem on my site isn’t widespread, but it’s super annoying to the active ones (though only SmokyBlue comes to mind right now).

1 Like

I have done nothing, really, and right now her profile is working:

Profile page:

Activity page:

Card:

Note how her avatar in the thread is still borked.

And now, a minute after it stopped working?! What is going on? :confused:

1 Like

Do you use SSO (single sign on) or traditional username/pass logins?

I am using SSO - One of the users, SmokyBlue, now looks completely normal. I am confused.

It’s likely that SSO is doing something to cause this, since it seems to be triggered by logins.

facing the same problem, reported here: May admins don't have any access to a user profile?

we don’t use sso. and we have seen the same behavior. e.g.:

2 Likes