Conversation

Notices

1. Embed this notice
   Lapsus (lapsus@mastodon.is-a.horse)'s status on Friday, 14-Jun-2024 12:40:15 JST Lapsus

   It looks like I can change from mastodon.is-a.horse to just is-a.horse by having the main domain just point at mastodon directly, instead of doing the "fun" nginx redirecting stuff for certs/webfinger, now that this is definitively the main use for the domain.

   I'm guessing things will explode if I were to remove the mastodon subdomain, but aside from that, does anyone know if there's some other hidden problems I'm not seeing?

   #fediadmin #mastoadmin

   • Embed this notice
     BeAware :fediverse: (beaware@social.beaware.live)'s status on Friday, 14-Jun-2024 12:40:14 JST BeAware :fediverse:

     in reply to

     @Lapsus I don't think you can change domain settings at all once you have the instance running, or else youll break everything...like completely broken federation because your instance federating relies on other instances that know the domain.😬

   • Embed this notice
     Lapsus (lapsus@mastodon.is-a.horse)'s status on Friday, 14-Jun-2024 12:49:42 JST Lapsus

     in reply to

     • BeAware :fediverse:

     @BeAware Yeah, I'm pretty sure everything dies if I heck up the mastodon subdomain, but from a frontend perspective it looks like the user side of things will work / is working without the additional redirect?

     All the federation is still happening on the subdomain, but I'm wondering if there's a hidden snag of the users using the frontend on the main is-a.horse domain?

     Federation hasn't broken (yet?) with the main domain pointing directly at mastodon for the users, so I'm hopeful.