case: (Default)
Case ([personal profile] case) wrote in [community profile] fandomsecrets2023-07-06 04:54 pm

[ SECRET POST #6026 ]


⌈ Secret Post #6026 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.



__________________________________________________



02.



__________________________________________________



03.



__________________________________________________



04.



__________________________________________________



05.



__________________________________________________



06.



__________________________________________________



07.
























Notes:

Secrets Left to Post: 01 pages, 09 secrets from Secret Submission Post #861.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Re: 503 Backend Cache Errors

(Anonymous) 2023-07-07 01:07 pm (UTC)(link)
503 errors aren’t caused by high traffic, it’s caused by site maintainers either failing to clear their server cache or setting the limit too high. The site is working now so either they finally got around to clearing the cache they needed to do the instant they pushed the code or Varnish deployed a temporary fix on their behalf. If it happens again at the next peak time, it means Varnish stepped in to provide a short term solution but the site will remain broken until the maintainers do what they’re supposed to.
pantswarrior: "I am love. Find me, walk beside me..." (Default)

Re: 503 Backend Cache Errors

[personal profile] pantswarrior 2023-07-07 11:39 pm (UTC)(link)
Ah my bad, I was getting the error that was mentioned in the maintenance journal post, and was not paying attention enough to realize this comment was about another error. What I get for posting while up too late and half asleep. ;)