Fixed the dumb static file mistake and federation seems to be working. I guess I'll continue over on that account if anything else happens.

That fixed the staging domain on the identifier, but css/js still seems messed up. Will see what I can do about that

Show thread

nope, that didn't seem to do anything. maybe a total server reboot will?

Show thread


instead of a 500 i now actually get _something_ even if broken.

gonna clear nginx's caches, maybe that'll fix it

Show thread

bonus: my hacky "use templates outside ansible" script doesn't seem to care about prod vs staging, so that's another todo

Show thread

wait no no no

Nginx _is_ reaching the Mastodon backend. I am getting POST's to /inbox and they seem to work fine (return 204). The web interface just doesn't work.



Show thread

Yeah Nginx isn't even reaching the mastodon backend for some weird reason but I'm more interested in HOW THE STAGING DOMAIN GOT IN HERE

gonna re-run ansible, maybe that'll fix it somehow

Show thread

ripgrep cannot seem to find any references to "staging.local" in mastodon's files, did it somehow stick in the database? how would it?

Show thread


Why is Mastodon thinking it's running on my staging domain? the ".env.production" file has the correct domain and nginx routes the correct domain, what?

Show thread

Well, if my internet connection didn't find the perfect few hours to unnecessarily slow down even more than it is that would be sweet.

(Thank god for mosh!)

Show thread

Let's Encrypt setup worked (I assume, certs got generated)

Re-building all configuration that accidentally got built w/ ssl disabled and hopefully everything* should be up soon.

*: Mastodon might not be. I migrated the database and the public/system folders but I am still not sure about it yet.

Show thread

youch! i must've accidentally disabled ssl in my prod config, probably happened while i was copying my staging config and i just forgot to enable it :/

Show thread

unwanted update 2:

migrated database content for gitea and miniflux, also moved over the data and repos folders for gitea

gitea seems to show repository contents but i cannot be 100% sure because the only way i could test is via curl'ing localhost because the ssh setup hasn't run yet

miniflux also shows up a login page instead of straight-up crashing, so that's a good sign (even if it wasn't, miniflux is private so no one really cares)

Show thread

unwanted update: seems to be going really well so far, no unexpected errors, though mastodon itself isn't installed yet and that's the only piece of software i am worried about. maybe except the ssl config.

Show thread

"main" account at toot.ebc.li is currently down because i'm migrating to a new server with better infrastructure and i shut mastodon down just to be safe

ain't it great that i still haven't deleted the 2fa setup for this one?

Show more

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!