TheBaby5 reported that after updating Discourse, user profile and other feature pages (e.g., messages, activity, drafts) returned a “page doesn’t exist or is private” error. Disabling unofficial plugins didn’t resolve it initially, and rebuilding the site caused downtime. After a second rebuild, the site recovered, but only after disabling two specific plugins: discourse-follow and discourse-quick-messages. jomaxro suggested isolating the problematic plugin by re-enabling them one at a time and reporting issues on Meta. angus later confirmed both plugins have been updated to support the latest Discourse version, with a working demo available at try.thepavilion.io. The issue appears resolved via plugin updates, and users are advised to ensure compatibility after Discourse upgrades.
When trying to access user profile page that is www.website.com/u/example the below error popups, I recently updated the discourse. Also I tried disabling all unofficial plugins, the problem still occurs.
Also, the other page like message page, Activity page, Drafts page showing Oops! That page doesn’t exist or is private.
Please look into this asap!
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.
What plugins (especially unofficial) are you running?
Did you install Discourse via the Official Instructions? If not, how did you install it?
Any errors in your site logs (/logs)?
Is your site public? If so, can you share a link?
Best guess is there’s a plugin incompatibility, or other configuration issue. User profiles work just fine here on Meta, as well as try.discourse.org, both of which are running the very latest code.
Great! Glad it is up. Your next step would be figuring out which plugin is causing the issues. You can check the plugin topics here on Meta to see if it is a known issue. If not, try installing 1 plugin at a time and see when the issue returns. Once you know which plugin it is, write up a report in the appropriate topic here on Meta so the Pavilion team can take a look and fix it.