Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tool gives an error when connecting to Sharkey instance #68

Open
Plusichan opened this issue Jan 26, 2025 · 8 comments
Open

Tool gives an error when connecting to Sharkey instance #68

Plusichan opened this issue Jan 26, 2025 · 8 comments

Comments

@Plusichan
Copy link

Plusichan commented Jan 26, 2025

I'm attempting to import my followers from X to my account in a Sharkey instance: verse.averagedood.xyz
Once I click Connect, the "Authorization required" screen shows up, I click on Accept, then the tool returns Erreur de configuration, with both buttons that say Retour à l'accueil.

@FannyCaulfield
Copy link
Collaborator

Hello can you try again pls ? :)

@csolisr
Copy link

csolisr commented Jan 29, 2025

Something similar is happening but with my Friendica instance.

@Plusichan
Copy link
Author

Hello can you try again pls ? :)

Still gives the same error.

@Plusichan
Copy link
Author

My instance has now migrated to Sharkey (same domain and subdomain, same data; just a different service) and the issue still persists.

@FannyCaulfield
Copy link
Collaborator

Hello, what is your Mastodon API version pls ? Seems like upgrading to 4.3.0 can fix the issue. Sorry for the delay, let me know if the problem persists :)

@AverageDood
Copy link

Iceshrimp had almost full v2. Sharkey has a bit of both v1 and v2, but mostly v1

@Plusichan Plusichan changed the title Tool gives an error when connecting to Iceshrimp instance Tool gives an error when connecting to Sharkey instance Mar 1, 2025
@Plusichan
Copy link
Author

As of March 1st, this is still not resolved and the same issue occurs.

@csolisr
Copy link

csolisr commented Mar 1, 2025

As of March 1st, this is still not resolved and the same issue occurs.

The related issue #70 is also still having the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants