ΛidanMorning. I still have NO idea why I can't get Mastodon to install and run properly. I've followed everything to a T and it just won't let me in.
It's so frustrating and no-one seems to have any idea why it's not working.
It's genuinely starting to upset me now. NOTHING I do works. Nothing I change affects anything positively. All I get is either a 403 or a redirect loop.
I don't know what to do!
@Do you know if it’s a host issue or a Mastodon issue?
@Flaky I don’t know. Either I get 403 errors from the browser or NGINX, or I get redirect loops. Nothing I change solves any of it.
Vaghrad@cleanycloth are you using cloudflare dns with proxy on?
@Vaghrad I am, yes.
@cleanycloth yeah. Turn the proxy off and try again in 5 mins. If the error is gone and you still want to use the proxy you gotta do a bunch of googling and ssl stuff, but at least you'd know where the error lies. Good luck 🤕
@cleanycloth just looked at your posts and seen that you're using the full cloudflare combo. Have you checked your cloudflare ssl/tls settings? Depending in your setup it should be either set to flex or full (when using cloudflare ssl certs). If that won't help i'm outta ideas too. Gave up on their whole song and dance after having nothing but trouble
@Vaghrad I just ripped it all out and tried Pleroma, same thing. Changing the SSL/TLS certs does absolutely nothing, even when I was using Cloudflare certs.
I'm at a complete loss now
@cleanycloth yeah the software doesn't matter, problem is definitely between you and cloudflare. It should be fedi software running on localhost http port xxxx -> reverse proxy exposing https port 443 with your certificate -> internet.
But using cloudflare tunnels and whatnot you probably want to tunnel it directly or else your reverse proxy is fucking up whatever cloudflare is doing. So you'd skip everything about it and point your cloudflare tunnel daemon directly at the pleroma http port (this is all conjecture i didn't try it myself). Or maybe just expose http over the reverse proxy and point the tunnel at it.
But using cloudflare tunnels and whatnot you probably want to tunnel it directly or else your reverse proxy is fucking up whatever cloudflare is doing. So you'd skip everything about it and point your cloudflare tunnel daemon directly at the pleroma http port (this is all conjecture i didn't try it myself). Or maybe just expose http over the reverse proxy and point the tunnel at it.