Alternative way to make the plugin work?

  • Resolved jla

    (@javierleiva)


    3 years, 5 months ago

    Hi!

    I installed the plugin and got an issue I see is recurring: Webfinger endpoint is not accessible.

    I read it has to do with the .well-known path being disallowed because of the “let’s encrypt” ssl configuration, so I contacted my hosting provider about it. They replied this:

    We cannot disallow our use of the .well-know folder, as it’s necessary for the SSL certificate renewal to work.

    So my question is: is there any other way to make it work?

    Thanks!

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Matthias Pfefferle

    (@pfefferle)

    3 years, 5 months ago

    They do not have to dissallow their usage! But it should be possible to configure the webserver in such a way, that it should be possible to register .well-known routes, especially if they are only virtual!

    Otherwise there is no real way to make it work with Mastodon. WebFinger (which uses the .well-known URI) is not part of the ActivityPub spec, so it should be able to use your author page instead of WebFinger on some plattforms, but Mastodon seems to require WebFinger.

    Thread Starter jla

    (@javierleiva)

    3 years, 5 months ago

    Thank you for your reply. I’ll talk to them and see if they are willing to help with that. 🙂

    Plugin Author Matthias Pfefferle

    (@pfefferle)

    3 years, 5 months ago

    Let me know if I can support you in any way.

    Thread Starter jla

    (@javierleiva)

    3 years, 5 months ago

    Thank you, I appreciate your support.

    They said that I should be able to make it work now. They also placed a test file in the .well-known folder, and it loads correctly:

    https://javierleiva.com/.well-known/hyd.php

    However, this returns a 404:

    https://javierleiva.com/.well-known/webfinger?resource=acct:javier@javierleiva.com

    Do you have any suggestions? The only thing that comes to mind is that I have the WordPress on a /blog folder, not in the domain’s root, and maybe that is messing something up (probably nothing to do with it, but mentioning it just in case).

    Thank you again 🙂

    Thread Starter jla

    (@javierleiva)

    3 years, 4 months ago

    In case it helps someone else: I managed to make it work by moving my blog from a folder to the domain root.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Alternative way to make the plugin work?’ is closed to new replies.