The user davidkingham encountered an SSO login issue after a rebuild, resulting in a “The requested URL or resource could not be found” error when trying to access Discourse. While the /u/admin-login route resolved admin access, new users still couldn’t sign up due to a PostgreSQL unique violation error related to the idx_tag_users_ix1 index. The issue was traced to a corrupted index caused by a tag notification setting, which was resolved by removing the tag from default muted status. However, the problem reappeared, and the user now seeks to identify the problematic tag ID (842) from the logs to address the recurring database error. pfaffman and RGJ provided troubleshooting steps, including reindexing and checking tag settings, ultimately helping diagnose the root cause.
I use Memberful as my SSO and after a rebuild today I started getting the error “The requested URL or resource could not be found.” when logging in to Discourse, I can’t even get into the admin side now. I am able to login into Memberful successfully, just can’t get into Discourse. How do I troubleshoot from here? I have rebuilt with no plugins, ran discourse-doctor and I don’t see anything strange.
Prior to rebuilding I was having issues with new member signups not being created as a user in Discourse. I was getting the following errors in the console, but after the rebuild even existing users can’t login. Please help!
He said this looks like an issue in the forum itself. We’re not sure if it is related to the screenshot you sent us (the original error log screenshot), but when we try to synchronize members, we receive an internal server error:
Oops - Error 500
Oops
The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience.
Detailed information about the error was logged, and an automatic notification generated. We'll take a look at it.
No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site's feedback category.
This happens for POST requests to /admin/users/sync_sso.
He suggests contacting your Discourse host or admin to see if they can help prevent this error.
I was able to login to get admin access again thanks to @pfaffman who reminded me of the /u/admin-login route, thanks Jay!
So the requested url... is not an issue anymore, but the other issue of new users not being created is still is there. Jay, you were able to login because you already had a login, but new users cannot and get the login error.
@RGJ I did make changes to this recently, do you really think this could cause login issues? I created one tag and set it to muted by default, that was the only change.
Sorry this is a bit scattershot, there were a lot of issues going on this morning!
Up until an hour ago, no. But the idx_tag_users_ix1 index is complaining. It might be corrupt, so we might be fighting symptoms, but disabling those notifications might at least help getting your forum usable again, since those are set upon user creation.
Jay beat me to it as we’ve been talking behind the scenes, but yes Richard this was the solution! You sir are brilliant. I removed the tag from default muted, applied to all users and now it works again. I’ll be doing some testing to see if I can turn this back on to determine if it was just a corruption or some sort of bug. Thank you, thank you!
Edit: a follow up, it was indeed corrupt, I put the tag notification back in place and everything works properly.
I’m afraid this problem is back and now removing the tag that was causing the problem is not working. How do I identify the tag id 842 that I see in the logs? Thanks!