So at this point this seems related to my IP address. Switching to another router and things work again. Switch back and they are broken again.
One important note is that I accidentally ran a script that made a bunch of API calls right before this started. So I’m wondering if that triggered a per-IP ban somewhere…
Apparently this is a widespread problem for my users.
I’m not sure what to do at this point. Are there some commands that I can run to check the database for issues, clear out state from various Discourse components, etc.?
As another follow up, this seems to be related to logout and suspend functionality. At some point today one of my scripts broke, which caused all users to be suspend and logged out using the API functionality. Somehow that seems to have borked the session state causing the problems I described above.
Deleting all user sessions using the API seems to have cleared things up… I hope. Not sure what caused the initial problem however, since it seems reasonable to expect the suspend and logout APIs to not cause this problem…
Spoke too soon—this is still happening. Seems confined to my user at this point. Now it is manifesting itself as sudden logouts after just a minute or two.
Any help with this? It’s super confusing and disconcerting. Note that this still has the strange IP address dependency that it did previously, in case that’s helpful. Moving to a different subnet solves the problem.
What’s so weird about this is how episodic it is. Right now I’m logged in to my forum and things are working fine. But in a few minutes, I’ll suddenly be logged out. (Somehow this always happens right in the midst of a hugely enlightening post, of course.)
I’ve seen notes from @sam about the session coherency protocol, so I’m wondering if I’m triggering some instability or corner case there…
Am having the same problem also. This is a recent issue for me since I have been running discourse for close to 6 months with no problem. Also after getting logged out once I try to log in again I get
The requested URL or resource could not be found.
After this once I reload the site everything returns to normal for a while.
I wish I could remember what I did that solved the problem. I think there was some stale data stuck in a cache somewhere, but it was far from clear how to fix it. If you’re really stuck let me know and I’ll try digging into our server logs in case there’s anything useful…
Just got this on the homepage and have never seen this before. Didn’t do anything recently to cause this (i.e. update)
Any ideas yet what’s caused this?
P.S. I have also experienced your referenced “you don’t have access to that category” errors randomly in the past, when a reload (maybe 2 or 3) loads fine.
I am not sure if this totally applies, but I just had something like this happen to me. I am running through a script I wrote with the Discourse API. I changed one of my SSO settings which incidentally changed my discourse admin username to something else. Since I have to make API calls with my API key and my API username, I started receiving this message after a happy day of scripting. Since my discourse api_username changed, the calls were rejected.
If anyone has this problem, here are your two simple options:
A) Change the api_username to the new discourse username in your script
B) Change the discourse username in the site front-end to match the api_username you are sending.
Again, this may not help @jesselperry but might help others since I landed on this thread during troubleshooting.
이 문제는 Discourse 1.9에서 2.3으로 업그레이드한 후에 발생하기 시작했습니다.
우리는 항상 MealMentor라는 시스템 계정을 사용해 왔습니다. 설정을 확인하고 키를 여러 번 재발급했지만, “요청한 URL 또는 리소스를 찾을 수 없습니다.”라는 메시지는 해결되지 않았습니다. 그래서 api_username을 제 개인 관리자 계정인 Scott_Team_MM으로 변경했는데, 즉시 문제가 해결되었습니다.
수개월간 프로덕션 환경에서 운영해 온 우리 앱에서 지난 수요일부터 동일한 문제가 발생하기 시작했습니다. 현재 Discourse 버전은 2.8입니다. Docker 컨테이너를 재시작하면 문제가 일시적으로 해결되지만, 오늘 아침 다시 발생했습니다. Discourse에서 SSO를 사용하고 있으며, a) 문제가 실제로 해결될지 확신이 서지 않고 b) 왜 문제가 해결되는지 원인을 정확히 파악하지 못한 상태이므로 사용자 이름을 변경하는 데 주저하고 있습니다. 오래된 주제인 것을 알지만, 우리가 겪고 있는 증상을 정확히 설명하는 곳은 여기가 유일합니다.
