حدث خطأ: ليس مسموحًا لك بعرض المصدر المطلوب

One of our users is getting the following message when trying to create a post: “An error occurred: You are not permitted to view the requested source.” The user is in several groups that all have access to publish to the category where he is experiencing this error. Both groups have “see/reply/create” access in this category. The user is not suspended or silenced. The user has tried clearing the cache with CTRL+F5. Any ideas about what is causing this error?

Edit: The user reports he is unable to post to any category. When I try logging in as this user, I don’t see any “New Topic” button. The user has TL1, which should be able to post new topics.

You need to have the user open his browser tools to determine what is refusing the request.

It is possible that it’s Discourse itself, but it could also be a proxy (e.g. Cloudflare) or a corporate proxy interfering.

إعجابَين (2)

I’ll share this feedback with the user. This is the only user I’m currently seeing this problem with and the only users with access to this forum are employees, so it doesn’t seem like a corporate proxy.

Do you know why I wouldn’t be able to see the “New Topic” button when I impersonate other users?

I would expect it’s because the user is currently not allowed to create topics. If you impersonate them again, you can add /new-topic to the URL (e.g. https://meta.discourse.org/new-topic) to open the composer. Then you can try to create the topic and check the browser console for errors.

When I add /new-topic to the forum URL logged in as my account (admin) it opens a new topic interface. When I add /new-topic to the forum URL when logged in as another user, it redirects me to /categories and does not open a new topic interface.

Interesting. I silenced a user on my test site and I see the same problem with the redirect. It didn’t happen when I tried before, suggesting that because I have a link to /new-topic, a custom sidebar section there, and that works - no idea why. It seems the link also works if I put it into a PM to the user. Maybe you can try that, too.