-
Notifications
You must be signed in to change notification settings - Fork 6
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
Cannot connect any client to Wordpress #43
Cannot connect any client to Wordpress #43
Comments
I'm also getting the same error with Ice Cube: I also have IndieWeb plugins installed on my Wordpress instance (eg. Micropub, Webmention etc.) Do they need to be removed? |
I'm also seeing this with various apps I've tried. Elk, Phanpy, Fedilab... |
Anyone had any more luck with the recent updates to the plugin? I'm still getting errors. |
Hi everyone, sorry about this. It works for me. Would you be so kind and try https://akirk.github.io/mastodon-api-tester/ to connect to your WordPress site via the API? I hope it can reveal where things fail for you individually. |
Hey @akirk I just tested the latest update to the plugin and it still doesn't work for me. Edit: do I have to send you the logs, or do you have them already? |
No, sorry, I don't see any logs, it's all client side. Were you able to connect and do you see that reflected in your Mastodon Apps settings? |
@akirk Please find the log attached. The Mastodon Apps settings do show the Mastodon API Tester, but then it has always been able to show the other apps as well (eg. Ivory, IceCube), but the apps themselves can't connect to the WordPress site. In the past, they showed the error message mentioned in the OP, but now it just silently fails. |
@vishae thanks! Could you also click one of the endpoints in the Tester like |
@akirk thanks so much for helping sort this out (and writing the plugin to begin with). I also ran the test link you sent and log is here: I see the same results as @vishae where the Mastodon API Tester shows up with a token and as an application in my Mastodon Apps Settings but that has always been the case. I then clicked on /api/v1/accounts/verify_credentials as you just suggested and here is the log from that: If I click on /api/v1/timelines/home I get the same message in the log "invalid access token" Hope this helps! V |
Thank you, this is helpful! Looks like something is wrong with storing the access token for later use. I'll investigate a little later in my day today. |
Could you check in the "Access Tokens" section that @StarrWulfe posted a screenshot of, when you hover over the app name, you should see the actual access token. Is it being displayed? |
After some more testing, I think it might be caused by the IndieAuth plugin, do you have that one installed and active? |
I do have that one installed. Let me deactivate and test in a little bit.
…On Fri, Jan 12, 2024, 05:30 Alex Kirk ***@***.***> wrote:
After some more testing, I think it might be caused by the IndieAuth
plugin, do you have that one installed and active?
—
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVLNIRZ4BAC3NT4KPVWVYTYOE3JFAVCNFSM6AAAAAA6EY72OWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZGIYTGMRVGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I submitted a patch on the IndieAuth plugin to fix this: indieweb/wordpress-indieauth#263 |
I disabled IndieAuth and just reconnected to my site with Phanpy and it
works! Amazing! Thank you so much and double thanks for patching IndieAuth!
V
…On Fri, Jan 12, 2024 at 7:30 AM Alex Kirk ***@***.***> wrote:
I submitted a patch on the IndieAuth plugin to fix this:
indieweb/wordpress-indieauth#263
<indieweb/wordpress-indieauth#263>
—
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVLNIR5LV4WCXOG7H54UODYOFJKZAVCNFSM6AAAAAA6EY72OWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZGUYTGOBSHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
*Vaughn*
social.vaughnhannon.com
|
I just released the fix of @akirk Thanks for the fix! |
Oh wow, glad my submissions could help with this one! |
@akirk So I tried disabling Indieauth (before the update), and it did allow me to connect IceCube with my site. But IceCube wasn’t able to load any of my posts: Using the API testers, it looks like everything is fine, but I'm not sure. As for the Indieauth update, it didn't seem to fix anything for me. After updating Indieauth and re-enabling it, I still get the invalid token when I try to authorise: |
Interesting, according to your log, the |
@vishae Could you update Enable Mastodon Apps to 0.6.4 which includes the above and try again? Thank you! |
@akirk in trying to test this plugin I've somehow broken the indieweb-ness of my site (ie. when I try to use the Mastodon API tester, it says I'm trying to figure out what I've done (I just turned all my other plugins off to see if it was interfering with the Mastodon app and turned it back on) and see if I can fix it. Then I will try continuing testing the Enable Mastodon Apps plugin. |
@akirk the Mastodon API tester isn't letting me authorise now: I can authorise using IceCube (but still can't see any posts, even when I post a new one) |
@akirk I also had some issues with "old" tokens (already connected apps) these days and the solution was to remove all of the already created ones. |
Errors out of the following response shows:
Other times it times out with:
In all cases tokens are saved but never used.
Client: Ice Cubes, Tusker and official Mastodon app
The text was updated successfully, but these errors were encountered: