I struggled with Activitypub when it first came out, no luck in getting it to work. Now I’m trying again! Activitypub plugin 2.2.0 installed. Webfinger 3.2.7 installed. All successful, but Site Health shows ‘Webfinger endpoint not accessible’ error message. There’s a dropdown link with that message that, when clicked on, should show some kind of explainer as to why. It does drop down but it’s blank, no text of any type displaying.
Blog running WP 6.5, all plugins and themes up to date.
It’s hard to troubleshoot without an explainer of some sort. Any idea of what might be a good step to test?
]]>Since the last update to the ActivityPub plugin I get this critical issue in my Site Health:
“WebFinger endpoint is not accessible”
Assistance would be appreciated.
]]>my blog is hosted in a subfolder, so i added a rewrite to my root .htaccess:
RedirectMatch "^\/.well-known/(webfinger|nodeinfo|x-nodeinfo2|activitypub)(.*)$" /blog/.well-known/$1$2
however, subsequently, the blog doesn’t know how to handle this, and throws a 404. So I change it to
RewriteRule "^\/.well-known/(webfinger|nodeinfo|x-nodeinfo2|activitypub)(.*)$" /blog/index.php?well-known [QSA]
But I get an error:
Fatal error: Uncaught Error: Call to undefined method WP_Error::get_url() in /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-content/plugins/activitypub/integration/class-webfinger.php:36
Stack trace:
#0 /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-includes/class-wp-hook.php(310): Activitypub\Integration\Webfinger::add_user_discovery()
#1 /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-includes/plugin.php(205): WP_Hook->apply_filters() 2 /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-content/plugins/webfinger/includes/class-webfinger.php(146): apply_filters()
#3 /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-includes/class-wp-hook.php(310): Webfinger::generate_user_data()
#4 /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#5 /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-content/plugins/webfinger/includes/c in /srv/home/blog/domains/blog.com/htdocs/www/blog/wp-content/plugins/activitypub/integration/class-webfinger.php on line 36
What did i do wrong?
]]>Hello!
Trying to wrap my head around how .well-known works. I already use the “Friends” and “ActivityPub” plugins for WordPress to put my blog hammyhavoc.com “on the fediverse”. That’s cool.
However, I also want to use Mastodon with my own domain (and likely my own instance as well) as there’s certain functionality from Mastodon that I want, am I also able to convey that information through WebFinger?
This may be 4am brain speaking, but if I already have a [email protected] account as part of the Friends plugin on my blog, then that means that a [email protected] probably won’t work for Mastodon as they’re both ActivityPub-based, right?
Treat me like a total noob. :- )
]]>Hi,
Still testing the various indieweb resources… The WebFinger plugin seems broken on both WP blogs:
https://webfinger.net/lookup/?resource=cybeardjm%40amf.didiermary.fr
https://webfinger.net/lookup/?resource=cybeardjm%40www.didiermary.fr
Request Log 15:42:12 Looking up WebFinger data for acct:[email protected]
15:42:12 GET https://www.didiermary.fr/.well-known/webfinger?resource=acct%3Acybeardjm%40www.didiermary.fr
15:42:13 Error getting JRD: 403 Forbidden
JSON Resource Descriptor (JRD)
null
But, the URL (in the example above) works and gives a full JSON page…
Any idea what I should test?
Sincerely
DJM
The WordPress plugin ActivityPub has got a great version 1. Now it is time for some publisher to move their @something@something mastodon account to their ActivityPub powered blog/fediverse.
Described by Mastodon moving followers https://docs.joinmastodon.org/user/moving/ (not al support moving) you should add your old handle as alias to your new account.
I’ve tried a couple of snippets to add an alias to the webfinger .wellknow, but haven’t had any result.
Although it is probably not that hard, but I am missing something.
How do you add an alias?
I have just set up a wordpress website and I need a webfinger to work on it. I added the webfinger plugin, but on webfinger.net I still get an “Error getting JRD: 404 Not Found” Is there other settings I need to set up or something that is blocking it from accessing the information? I am trying to set up a tailscale account with a custom domain but it needs a webfinger verification. Here is more info on that, https://tailscale.com/kb/1240/sso-custom-oidc/#requirements Thanks!
]]>This plugin publishes users’ private information without due notice. When users add a private email address, this will be revealed by webfinger.
Something like this should only be done with users’ explicit consent
]]>I am getting this error on my Site Health, and I understandably can’t find myself on Mastodon or Webfinger search either.
Your WebFinger endpoint https://africans.live/.well-known/webfinger?resource=acct:[email protected] does not return valid JSON for application/jrd+json.
According to my host (Hostinger) I am not using Cloudfare or something that should block it. I tried deactivating plugins one by one to see if there was a conflict, but to no avail.
I’m not sure what to do. I got it to work on other sites with a different host, but this one is the first I’m trying on Hostinger.
]]>The get_user_by_uri() static functiopn should support useranmes which are email addresses
I patched it by adding:
`case ‘acct’: // check acct scheme
if ($the_user = get_user_by(‘login’, $host)){
return $the_user;
}
Woocommerce and plenty of other plugins use the email address as the username. So probably best to support this. Can you please add this?
]]>Hi,
I’m quite new to webfinger.
I have a stupid question : I installed and activated the plugin but now I wonder how to use it. Which request should I submit to my website?
Thanks!
]]>Is there a way to make this work with multiblog installations? At the moment my webfinger just points to my author page of the main blog (machinespirit.net) but I would like it to point to my main sub blog (machinespirit.net/acegiak)?
]]>