Mastodon connection failed because of passing "scope" instead of "scopes" in the query string
Author: olivierlambertCreated Dec 27, 2025Updated Sep 17, 2026
Labelstype: bugstale
Description
Hi,
When using the connection with Mastodon, I have:
The requested scope is invalid, unknown, or malformed.
But the URL is using:
https://<serverURL>/oauth/authorize?client_id=<client_ID>&response_type=code&redirect_uri=https%3A%2F%2F<Postiz_Server>%2Fintegrations%2Fsocial%2Fmastodon&scope=write:statuses+profile+write:media&state=<some_state>
See scope while it should be scopes. If I manually change it to scopes, then this time I'm seeing the app authorization from the Mastodon server.
Reproduction steps
- Connect your mastodon instance with the right ID/secret and URL
- See the error message
- Change
scopetoscopesin the URL and it works
Expected behavior
It should work with the right query string
Actual Behavior with Screenshots
By default:
After changing to scopes:
Operating system
Linux
Node Version
Using the Docker compose
Provide any additional context for the Bug.
No response
Have you spent some time to check if this bug has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
Yes I am willing to submit a PR!
Source: gitroomhq/postiz-app