How do I get started with this after install? #155
Replies: 6 comments 49 replies
-
You shouldn't have to do anything (though BuddyPress is also a fantastic piece of software, but not needed for this plugin to work.) The dinformation which you seek is found under your profile; under followers (Fediverse). You can see those who follow you; notice that you will immediately be discovered; look at it on another fediverse instance to which you have access. |
Beta Was this translation helpful? Give feedback.
-
I'm running WordPress on my own domain, with the URLs being at the root level, no subdirectories. I've installed WebFinger and ActivityPub, I see my profile identifier says I should search for I'm stumped. |
Beta Was this translation helpful? Give feedback.
-
Same problem, also on Dreamhost + Apache + LetsEncrypt. Following the recommendation to allow access to .well-known referenced here, I had Dreamhost Support add a bypass for .well-known. I'm still getting a 400, and
|
Beta Was this translation helpful? Give feedback.
-
I put this in my top-level .htaccess and it seems to be working. Also Dreamhost+Apache+Let's Encrypt, but on a VPS, so I'm not sure if that makes a difference. RewriteRule ^.well-known/(host-meta|webfinger|nodeinfo|x-nodeinfo) /blog/.well-known/$1 [L] I'm able to find and follow the author account through Mastodon again |
Beta Was this translation helpful? Give feedback.
-
I have some really weird info to add to this issue. I have the plugin working (on my Dreamhost VPS with LetsEncrypt) on my www domain (https://www.invincible.ink -> The setup on the www domain has an interesting quirk: The wordpress install is actually a couple of subfolders deep compared to the domain root, but I used a workaround to force the www as the wordpress URL for the sake of having it look nice. This involved copy/pasting the normal (core) WordPress htaccess snippet into the htaccess file in the domain root, then adding an index.php that loads the Wordpress header—and thus the entire software:
As weird as this is, it's always worked like a charm and has run the blog site correctly without getting in the way of a dozen other subdomains and subfolders. More importantly, that's just about the only meaningful difference between the two sites I'm trying to get working. And it does mean that the actual folder where the blog is located doesn't contain .well-known/.htaccess. Could that be why it's behaving there, in spite of known Dreamhost issues, and not on the second site? |
Beta Was this translation helpful? Give feedback.
-
Hello! I'm also having issues getting this plugin to work. I'm on Wordpress 6.1.1, installed on a linode VPS. I do have let's encrypt. After installing, got the "not valid json" message on site health, and went digging here for answers. Tested my website on webfinger.net/lookup, and got that my webfinger is 404'ing. Saw that several answers involved messing with .htaccess, and checked in my server: my wordpress install directory does not seem to have any explicit .htaccess file (it is a pretty vanilla install, I did almost no hacking other than soft-linking some other directories for static files), and no .well-known directory either. So I'm finding all the "add this to your .htaccess file" suggestions in this thread not very useful :-( Any suggestions of things that I should try are welcome! Extra info:
|
Beta Was this translation helpful? Give feedback.
-
I've installed the plug in, and BuddyPress in case it is needed. I can't see, however, any output from the plug in as such.
Do I need to take some extra steps to ensure that information about how to follow etc is displayed? Or has something gone wrong with my install (on WP's hosted site)?
Beta Was this translation helpful? Give feedback.
All reactions