200 X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self'; X-UA-Compatible: IE=Edge X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff X-Telligent-Evolution: 12.x Pragma: no-cache Connection: close Accept-Ranges: bytes Cache-Control: no-store, no-cache, max-age=0 Date: Tue, 23 Sep 2025 17:03:12 GMT ETag: "0x8DDF5C624966A39" Set-Cookie: .te.csrf=c1zvjSbXh428T7HZ70iXXnVasXeuLgAe_RcNmJi6-2g; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=_lUjsF0OCKnBHUGqQA7MyuvSXPfkXHog0uaPsnTI%2fdcKTjrT%2fFpqU9g7DBhMipWIEm7bYEcbLiGXcuHJLdsfpcDm2CP8JiEOmYB8nF6julzV5x%2foDkpukdXe8a9UNjjqGZhL0oncRe6%2byzh9Eom1uaMYaAcsbTSWdHPQ9Lx%2fF16ZS2rG212pIJFHzqjlF4saZnj2G6Zsz6D5Ujjn4OfWYj1Mv0MmK7v2CXxbJEYjiOnGlFuqZ5iCrBFL7KLAJdxF1tbiTkgunP%2bL2g%2b%2b2BRaCjQ%3d%3d; path=/; secure; HttpOnly; SameSite=Lax Set-Cookie: e14Guest=1; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Country=NL; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Language=en; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14TimeZone=Etc/UTC; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=46 Server-Timing: origin; dur=35 Server-Timing: ak_p; desc="1758646992322_34864907_273092888_8030_4953_6_8_-";dur=1 Strict-Transport-Security: max-age=86400 ; includeSubDomains ; preload #set ($UserId = $core_v2_user.Accessing.Id) #set ($Roles = $core_v2_utility.MakeList('Moderators', 'Almost Admins', 'Administrators')) #set ($IsAdminLike = $e14_utils.IsUserInRoleOrAdmin($UserId, $Roles)) #if($IsAdminLike == 'False') #end
Actions
Forum Thread Details
  • Replies 0 replies
  • Subscribers 2 subscribers
  • Views 256 views
  • Users 0 members are here
Related

Resolved: Unscheduled downtime and site restart

cstanton

At around 3pm UK time on the 13th of March the site became unresponsive and returned about 10 minutes later. The site then went down as the server stack was restarted by the server administration team.

We suspect this outage was caused by a bug with custom site administration tools and shouldn't be typical behavior.