-
• #2
Cheers for the heads up and your tireless efforts as ever Boss
-
• #3
I don’t know what those words mean but thank you for making it all work again. Was wondering if the missing pics were just me or everyone was getting them.
-
• #4
<hold onto your butts gif>
Good luck dude and much appreciated!
-
• #5
I don’t know what those words mean but thank you for making it all work again
Seconded!
-
• #6
I am at step 4 of this:
- Auth0 has been updated to send from
auth0@microcosm.app
- Sendgrid has been configured to send from
microcosm.app
- Confirmed that Sendgrid can send with the new config
- Re-wrote every reference in
microcosm
app to pointmicrocosm.app
tomicrocosm.app
And now I need to deploy the updated app... at this point, things will 100% guaranteed break.
- Auth0 has been updated to send from
-
• #7
Live surgery about to begin.
-
• #8
I think Brixtons forum is down as well, I can put something on our WhatsApp group. We don’t actually use the forum much
-
• #9
Just completed these steps:
- Purchased new TLS wildcard cert for
*.microcosm.app
(£250!!!) - Updated all references to
microcosm.app
within the Microcosm Go API - Updated all references to
microcosm.app
within the Python web site - Updated all references to
microcosm.app
within the https://microcosm.app site - Updated all
/etc/hosts
references - Updated the load balancer
- Installed the TLS cert
- Restarted everything
- Purchased new TLS wildcard cert for
-
• #10
Good job
-
• #11
Hah, thanks... there was a non-zero chance that this site did not come back.
-
• #12
Fast work. Now I'm curious why microcosm.app was suspended.
-
• #13
Hopefully the support ticket with Gandi will reveal this.
But it's done... this was a very expensive domain name and I intended to move off of it, so whatever the reason I'll not be renewing in 6 months time.
They could've just changed the domain rules for .sm or something silly... could be anything really.
-
• #14
It's a shame, I always thought microcosm.app was very elegant, but obviously there are more practical considerations.
-
• #15
A San Marino domain name, and a renewal process that required sending a fax in Italian was always a pain in the ass to be honest.
This is why I committed to move immediately... the chances of reaching the right person in the office within San Marino who can make sense of what happened and undo it... are low.
-
• #16
I'm done and am going to bed...
3.5 hours to move domain name of a SaaS platform and perform live surgery on a production system is pretty freaking stressful.
I think everything works.
-
• #17
Now I'm curious why microcosm.app was suspended.
.
A San Marino domain name, and a renewal process that required sending a fax in Italian
prolly brexit innit
-
• #18
You're a star
-
• #19
Do you need to run a DB migration or something to unfurl all shortened urls?
-
• #20
FYI outbound links in posts still refer to microcosm.app
-
• #21
Great success, thanks!
Re-wrote every reference in microcosm app to point microcosm.app to microcosm.app
Hope you changed them all to an env var ;)
-
• #22
Thanks boss.
Appreciate all your hard work. -
• #23
I thought of this after I went to bed. I need to purge the caches, but I'll do it in a little bit
-
• #24
That was impressive work, fixing the whole site in so little time.
-
• #25
Thanks for the emergency surgery!
The underlying domain name for this website is
lfgss.microco.sm
and I've just discovered that themicroco.sm
domain name has been suspended (why?!) bynic.sm
that manages it.The domain name has been suspended!!!!
https://www.nic.sm
This was discovered by people reporting broken avatars and image attachments.
I've opened a support case with Gandi (the domain registrar), but will start moving things to a spare domain.
I'll be moving from
microco.sm
tomicrocosm.app
which I already own and it is active on Cloudflare already, which means that I can adjust the DNS records there and expect < 10s for each change.There will 100% be breakage during this process as
microco.sm
is a SaaS platform and it changing breaks the many websites using it (of which LFGSS is the largest)... One doesn't just change the domain name for a SaaS service, but I shall.Started: 2023-05-15T21:26
Finished: 2023-05-16T11:25
Duration of incident: 13h 59m
Impact: 1h 3m of total outage from 21:26 to 22:24 on 2023-05-15
Costs: £550 (TLS certs, email campaigns updating people on some sites, domain renewal / extension, DNS provider, new domain name)
auth0@microcosm.app
microcosm.app
microcosm
app to pointmicroco.sm
tomicrocosm.app
*.microcosm.app
(£250!!!)microco.sm
within the Microcosm Go APImicroco.sm
within the Python web sitemicroco.sm
within the https://microcosm.app site/etc/hosts
referencesmicroco.sm
microco.sm
withmicrocosm.app
in all commentsmicroco.sm
had cross-user CNAME grandfathered in, andmicrocosm.app
does not, which means that other forums with their domains on Cloudflare cannot CNAME their custom domain.microcosm.app
microcosm.app
domain to 10 years (cost of £110)microcosm.app
to DNS Made Easy, and pay 1 year (cost of £180)microcosm.app
from Cloudflare to DNS Made Easy as I need to temporaily get off Cloudflare whilst the CNAME does not workmicrocosm.app
, tested nothing broke, awaiting nameserver updates to flush through.microco.sm
in Gandi (why pay for a suspended domain!?)microcosm.app
off of Cloudflare is more than double, verified that we have a fast enough set of SSDs and also several 4Gbps links and should be able to keep up. But, I shall prep a load balanced second cache machine to bear the load if needed.microcosm.ch
as one should always have a spare domain name lying around in case you need it.microco.sm
tomicrocosm.app
, the old domain will exist until mid-December, which is enough time for everything to be pointed at the new URLs.Note: microcosm.app now has DNS hosted by Akamai Linode rather than Cloudflare. As such we'll have higher outbound traffic fees in the future. The reason for this is I worked at Cloudflare and microco.sm was on a free (staff) Enterprise plan, but microcosm.app has no such favour given to it, and so it does not allow the same configuration to be achieved without a high price tag.
No-one has "your domain name of your SaaS provider is suspended" on their disaster recovery playbooks, which goes to show the art of the game is to be able to handle the unexpected. Top tips for those doing disaster recover plans... just model the following scenarios: compute failure, DNS failure (including domain name), network failure, storage failure. If you have those modelled, you can compose the response to cover any scenario.
Attachment shows impact to web traffic... it's about 1h3m of total outage, but mostly things have recovered. There is still a bumpy ride expected as DNS records flush through.
1 Attachment