Join private board

Hi There,

After a recent upgrade (self-hosted omnibus 9.4.2 > 9.5.2) I’m seeing the following message when I try and look a Boards under a specific team:

Join Private Board
You are about to join a private board . . . .
Cancel / Join

If I select join I can never join, I just loop through this message endlessly. This pop-up and loop has the added effect of preventing me from creating a board of my own in this team.

Is this a bug, or a feature :slight_smile:

Thanks,

D.

2 Likes

further to this . . . here’s my error at /var/log/mattermost.log

{"timestamp":"2024-03-19 20:35:03.366 Z","level":"error","msg":"category ID specified in input does not exist for user","caller":"app/plugin_api.go:1003","plugin_id":"focalboard"}
{"timestamp":"2024-03-19 20:35:03.368 Z","level":"error","msg":"API ERROR","caller":"app/plugin_api.go:1003","plugin_id":"focalboard","code":"500","error":"\"category ID specified in input does not exist for user\"","api":"/api/v2/teams/i6o1g4d1t78j3j8umxb7ja9u5e/categories/7fywkijquebnozy75aooxmt6jmy/boards/burrma483e7bebjojjy98fpx4ce"}
{"timestamp":"2024-03-19 20:38:07.179 Z","level":"error","msg":"{boards} not found","caller":"app/plugin_api.go:1003","plugin_id":"focalboard"}
{"timestamp":"2024-03-19 20:38:07.300 Z","level":"error","msg":"{boards} not found","caller":"app/plugin_api.go:1003","plugin_id":"focalboard"}
{"timestamp":"2024-03-19 20:38:09.106 Z","level":"error","msg":"{boards} not found","caller":"app/plugin_api.go:1003","plugin_id":"focalboard"}
{"timestamp":"2024-03-19 20:38:09.845 Z","level":"error","msg":"{boards} not found","caller":"app/plugin_api.go:1003","plugin_id":"focalboard"}
{"timestamp":"2024-03-19 20:38:10.464 Z","level":"error","msg":"{boards} not found","caller":"app/plugin_api.go:1003","plugin_id":"focalboard"}
{"timestamp":"2024-03-19 20:38:11.079 Z","level":"error","msg":"{boards} not found","caller":"app/plugin_api.go:1003","plugin_id":"focalboard"}
1 Like

We have the same situation with v9.5.1

What database are you using for Mattermost?

Were using PostgreSQL 13.14 (Ubuntu 13.14-1.pgdg22.04+1)

I have a test server where I’m not seeing this problem though . . . and both servers are running PostgreSQL 13.1, on Ubuntu 22.04.4 LTS. I have yet to find a reason they are behaving differently :slight_smile:

D.