Site Health Json error

I’m having this same trouble. Flywheel is asking for the file to put into wellknown but I don’t know what file that is. Same error as above

And it looks like this needs to be in wellknown but I can’t get it to work. https://sethgoldstein.me/wp-content/plugins/webfinger/webfinger?resource=acct:[email protected]

• This reply was modified 1 year, 10 months ago by Seth Goldstein.

I am sorry, I haven’t read this before (forgot to subscribe to the comments)

There is no real file, the WebFinger plugin is using mod-rewrite (like WordPress also does) to generate a virtual path.

This is the (not rewritten) URL btw.: https://sethgoldstein.me/index.php?well-known=webfinger&resource=acct%3Aseth%40sethgoldstein.me

Sadly some hoster have problems with their letsencrypt setup (which could also use the .well-known folder) and mod-rewrite.

I have Activitypub and Webfinger plugins installed on my WP site. My site is https://www.sgclark.com.

I’m seeing the same error as noted below.

Your WebFinger endpoint?https://www.sgclark.com/.well-known/webfinger?resource=acct:[email protected]?does not return valid JSON for?application/jrd+json.

My site is hosted at Siteground. What exactly would I need Siteground to do to make this work?

I recreated the URL you noted above for Seth and it does seem to be working for me on my site –> https://www.sgclark.com/index.php?well-known=webfinger&resource=acct%3Asgclark%40www.sgclark.com

However, in the ActivityHub plug in area on my site, it is still giving me the error I note above.

@sgclark you have the same issue as @goldsteinmedia ! The index.php must not be part of the URL, otherwise Mastodon can‘t find it! Does siteground use nginx? Otherwise you have to contact siteground. The error you get is a siteground error, so the request is not routed to WordPress, but blocked way before. So I can not really help here ??

Didn’t include /index.php with anything related to ActivityHub. Are you saying the system needs to “ignore” that page? Or are you saying the page /index.php needs to be removed? How would my WP site work if I removed the /index.php page? Why can’t Mastodon find my site if index.php is present?

I have no idea what nginx is. I will talk with Siteground to see if they know how to handle this.

• This reply was modified 1 year, 9 months ago by sgclark.

@sgclark ok, maybe this was a bit misleading! Please do not delete the index.php file! Then WordPress would indeed no longer work!

I meant the link you sent me! There is an index.php in front of the .well-known/webfinger and that is wrong! Mastodon will search for this URL https://www.sgclark.com/.well-known/webfinger?resource=acct:[email protected] if it is not accessible (or has the index.php in the path) then mastodon can not find your profile informations.

• This reply was modified 1 year, 9 months ago by Matthias Pfefferle.
• This reply was modified 1 year, 9 months ago by Matthias Pfefferle.

Ah…got it. When I do that, then that URL goes to a 404 page, which then takes us back to talking to Siteground. Which ai will do today. Thanks for your help!

This is the response I am getting from Siteground:

If something needs to be placed in the mentioned .well-known folder, you can upload the file that it’s trying to find in it, as per the screenshot above. And in case the people from the webfinger-endpoint plugin have any specific suggestions on any server changes that we may apply, do let us know what they are. We’d be happy to test them out.

And I’m slightly puzzled as well. I’m not understanding what exactly is missing or what functionality that SiteGround needs to enable on the server side? What is throwing that error on my WordPress “Site Health” area?

This is the error I am seeing:

WebFinger endpoint is not accessible
Your WebFinger endpoint https://www.sgclark.com/.well-known/webfinger?resource=acct:[email protected] does not return valid JSON for application/jrd+json.

When I go to the URL noted in the error, I get a Siteground generated 404:

https://www.sgclark.com/.well-known/webfinger?resource=acct:[email protected]