Hello, thank you for your reply. I have enabled debug logs in both the console and in a file.
I think I’ve found a silent bug, XD.
However, I finally identified the problem, but I don’t understand why it’s occurring.
Experimental chronicles:
To eliminate historical context and dependencies from my GitLab instance, I built a fresh, independent instance of Mattermost.
Even with a fresh install, the same problem occurs. So, it seems the issue lies in the execution context of my instance.
I use SeaweedFS for network storage. Therefore, I moved the plugins and client-plugins directories into local storage.
Success! All plugins can start now. But why? I checked in GitLab, and found that using local storage resolves the issue.
This is good news, but I want to understand why the binary of the plugin starts normally on local storage and not with network object storage when using FUSE mounting.
I find this very strange.