i’m re-branding all my online systems to fit a consistant domain name. But i wanted to keep all the old names active for a transitionary period.

so, i pop the new domain into my apache configuration and… the new names work.. but not the old ones.

it turns out letsencrypt only sign for one host name.

so i migrate early and cut compatability with the old name.. who needs that anyway.

i have left behind a 301 for the first migrated service, to kick people to the new name.. but this breaks some things.. hopefully the redirect along with a strongly worded email will move my clients to the new service.. after all i gave them a warning.

it is only after this that i realise i could have simply enabled a new reverse proxy for the new name.. oh well.. best to cut ties hard and fast.

so.. yeah