Only took 7 minutes just now for me on a $20/month DigitalOcean instance, site down (refusing connections) for about 6 minutes, 502 from nginx for last seconds before app back up. Similar when rebuilding to install a plugin which makes sense given it is the same command.
If you’re already on site when it goes down, clicking on a topic obtains a nice looking message
Topic failed to load
Sorry, we couldn’t load that topic, possibly due to a
connection problem. Please try again. If the problem persists, let us
know.
[Try Again]
It’d be really nice if a maintenance webserver stated up while the app is down so a nice message rather than connection refused could be displayed. Presumably that’d be a lot of juggling for a small benefit. Maybe some enterprise customer will want the appearance of zero downtime and pay for it someday.
Maybe? I’m not exactly sure what domain registration would have to do with this, so perhaps you can say more of what you’re thinking about?
Generally, we’re very happy with our Discourse uptime, but when it does go down for (planned or unplanned) maintenance, it’s a bit annoying to get additional help desk tickets when the same people are already dealing with the outage/upgrade.
Presumably @jesselperry means having DNS point to a different host during maintenance. This would only make sense for extended downtime given that DNS needs to propagate.
Most registrars let you set up a subdomain Forward temporarily to override DNS (as long as Nameserver is set to the registrar’s) it will be an immediate change.
I can’t found topic about temporary page setup (possibly with apache2 or nginx on host) when rebuilding container… I’ve seen some howto here in forum which I struggle to find…
Can’t somebody point me there or share their strategy for site down times? I’d like to display “Site under maintenance” message to users…
In general: Is it reasonable solution to have host server to serve that page? How do you guys do it here on meta?