Skip to content

Adding channels: Mastodon Social is still popping up in the authorization flow despite MASTODON_URL env #780

Closed
@candidexmedia

Description

@candidexmedia

📜 Description

Despite adding the MASTODON_URL env variable (per #708), I'm not able to get it working with my instance of choice.

👟 Reproduction steps

  1. Deploy Postiz on railway.app using the following template: https://railway.com/deploy/Rd76MM
  2. Follow the instructions to generate a domain and assign a port, per https://station.railway.com/templates/postiz-standalone-981f9b01#qxwz
  3. Redeploy
  4. Follow the doc instructions for Mastodon and send the curl request for your account/instance (replacing the mastodon.social links with mastodon.design)
  5. Add an env variable called MASTODON_URL with the value "https://mastodon.design"
  6. Redeploy
  7. Open your Postiz deployment, and try to add a new Mastodon channel

👍 Expected behavior

Redirects to your assigned Mastodon instance

👎 Actual Behavior with Screenshots

You're still redirected to mastodon.social:

Image

Image

Image

I even tried modifying the auth URL to make it mastodon.design instead, and got this:

Image

💻 Operating system

Something else

🤖 Node Version

?

📃 Provide any additional context for the Bug.

Railway deployment

👀 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?

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions