7
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

See title. I've checked the announcements community and here, but couldn't find anything mentioning this. I normally use old.reddthat, so I initially noticed the problem there, but then I looked into voyager.reddthat and alexandrite.reddthat and they're giving out cloudflare errors too. www.reddthat still correctly opens voyager though, so maybe it's just a DNS issue?

top 2 comments
sorted by: hot top controversial new old
[-] [email protected] 7 points 1 year ago

Fixed :)

Our server restarted recently (the host had a failure on the node we are hosting on) and the frontends didn't come back cleanly it seems. As we recently changed our endpoint monitoring (new status page: https://status.reddthat.com) I was only doing the

I've modified the all the frontends such that:

  • deployments will come back correctly now after an (unexpected) server restart
  • All alternate-frontends are now increased from 1 to 2, so we have a little "HA" incase one container crashes
  • I've added monitoring to the frontends

That should sort out the frontends so they are no longer "second class citizens".

[-] [email protected] 5 points 1 year ago

Thanks a lot again :)

this post was submitted on 29 Aug 2023
7 points (100.0% liked)

Reddthat Community and Support

705 readers
17 users here now

Reddthat Community & Support

This community is for us to chat about anything and everything, including support topics!

There is no defining specific rules for this community and it can be anything from "I do not like the weather" to "I've won the jackpot and want to give all the money away to charity!" ๐Ÿ˜„

Before posting, have you read the rules?

Introductory Required Reading


For anything else, try a search and see what turns up, if not post away!


Alternative Matrix Chatroom:

Alternative Support Forums:

founded 1 year ago
MODERATORS