Prevent this from happening during update?

[Cate_Soule]

During updates, my forum sometimes experiences a brief period of downtime. The site was unavailable for a short time while the update was running. Since I update my forum frequently, sometimes daily. I’m concerned that it could negatively affect SEO and user experience. Can we fix this from occuring? I have 3vcores 4.2ghz. 8gb ram. Low traffic. I’ve rebuilt my forum multiple times and even reinstalled it multiple times.

[tobiaseigen]

Hi Cate! This is a normal part of updating and is quite short. I honestly wouldn’t worry too much about SEO, but you could let your members know that you update frequently so they know to just check back later if the site appears to go down for a few minutes while you are updating.

Also, if you update from the UI the site will remain mostly available during the update.

There is a trick to show an “under maintenance” page while updating but I don’t recommend it.

Add an offline page to display when Discourse is rebuilding or starting up

This guide is intended for advanced users, who are already using nginx outside the docker container. By following this guide you make your setup more complicated and will loose some speed benefits like HTTP2 if you’re not running Ubuntu 16.04 or later. Proceed with caution! When Discourse is rebuilding or starting up, your users will usually either see an error message from their browser… [image] …or a not-so-nice 502 error message from Nginx: [image] If you’re a perfectionist…

[Cate_Soule]

@tobiaseigen

Hi Cate! This is a normal part of updating and is quite short. I honestly wouldn’t worry too much about SEO, but you could let your members know that you update frequently so they know to just check back later if the site appears to go down for a few minutes while you are updating.

Also, if you update from the UI the site will remain mostly available during the update.

There is a trick to show an “under maintenance” page while updating but I don’t recommend it.

But I was updating through the admin dashboard. I use 503 http during rebuild. My previous site was delisted in Google due to multiple downtimes so I had to change domain.

[tobiaseigen]

@Cate_Soule

But I was updating through the admin dashboard.

Well, I did say “mostly”! It’s not possible to avoid the downtime entirely because the container has to be restarted during the update. But in my experience the downtime is never more than a minute or so.

I update daily myself but my sites are quite small and I am obsessive about seeing the latest changes. Nobody has ever complained to me about the downtime.

I am curious..why are you updating daily?

@Cate_Soule

I use 503 during rebuild.

What does this mean?

@Cate_Soule

My previous site was delisted in Google due to multiple downtimes so I had to change domain.

That really surprises me! How much downtime did you have and for how long?

I am out of my depth talking about google. I don’t worry about it for my sites (they are small and private). Also, google is such a black box! It can be hard to know why things happen there.

[Cate_Soule]

I use 503 response (instead of 502 error) during maintenance mode like rebuilds (only when Discourse requires me to). My previous server was slow, so sometimes updates took longer and the site stayed too long during updates. So I got delisted. Now my new server is overkill, so I only have issues like this occasionally during update.

There are new updates every day, every hour so I update whenever I see new updates.

[Ed_S]

(Sorry, this is unsolicited advice and doesn’t answer your question… I’d suggest updating less often - not only will you have less of the unavoidable downtime, you’ll be less likely to update at a time when things are a bit broken. Personally I update when releases come out, but I also wait a day or so to give a chance for breakages to be fixed.)