Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter kamikazen

    (@kamikazen)

    I just realized my Let’s Encrypt certificate might be causing this problem, since thew .well-known contains?s the following .htaccess file:

    # Permit access to the challenge files but nothing else
    Order allow,deny
    Allow from all

    RewriteCond %{REQUEST_URI} ^/[.]well-known/acme-challenge/[a-zA-Z0-9_-]+$
    RewriteRule .* – [L]

    RewriteRule .* – [F]

    Could this be the culprit? If so, how could it be fixed without breaking anything?

    Plugin Author Matthias Pfefferle

    (@pfefferle)

    Sadly most of the current issues are because of the letsencrypt/.well-known problem. I sadly have no easy/perfect solution for that yet, because it is very different configured/setup on different shared hosting envs (do you use Bluehost?).

    Thread Starter kamikazen

    (@kamikazen)

    Thanks, I sadly suspected as much. It appears Letsencrypt hijacks the .well-known directory and there’s no easy way to grant access without breaking the certificate. ??

    I’m currently on a Dreamiest VPS, trying to work with their TS to see if there’s a way to fix this. Makes me wonder if it would be possible to run a Mastodon instance, or any federated ActivityPub software with them as I planned.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Getting 403 error on finger’ is closed to new replies.