mattermost / mattermost/docker
Unable to activate plugin
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 533
- Forks
- 284
- PR merge metrics
- No merged PRs in 30d
Description
I have deployed the mattermost-team-edition in ubuntu server on an amazon ec2 using the mattermost docker.
I installed a plugin named [mattermost-plugin-oembed](https://github.com/mattermost/mattermost-plugin-oembed) by compressing it into tar.gz following the documentation of [plugin](https://developers.mattermost.com/integrate/admin-guide/admin-plugins-beta/) but I got following error while enabling the plugin.

I used the same plugin compressed file in my local environment without using docker it works fine but when I use it in my docker environment I get the following message in my server logs.
`{"timestamp":"2021-10-22 04:28:53.738 Z","level":"error","msg":"Unable to activate plugin","caller":"app/plugin.go:146","plugin_id":"com.mattermost.oembed","error":"unable to start plugin: com.mattermost.oembed: Unrecognized remote plugin message: \n\nThis usually means that the plugin is either invalid or simply\nneeds to be recompiled to support the latest protocol."}`
I am unaware why I am getting this error or is this an issue with the docker version of mattermost.
Additional Information:
1. MATTERMOST_IMAGE=mattermost-team-edition
2. MATTERMOST_IMAGE_TAG=5.33.1
3. Database Schema Version: 5.33.1
4. Database: postgres
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker deployment details in the issue, especially MATTERMOST_IMAGE_TAG=5.33.1, the PostgreSQL database, and the mattermost-plugin-oembed archive. Compare the local and Docker environments, then inspect the activation error reported at app/plugin.go:146; done means identifying why the plugin activates locally but not in this container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgres
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100