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: Sat, 22 Nov 2025 02:04:20 GMT ETag: "0x8DDF5C624966A39" Set-Cookie: .te.csrf=pABNSNvKvBewd_CM3WywlNE5mU92D8PL-f4KtKVdWYk; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=_8XDBE4kNdgYScQ78ZtZmnbang2tDMtKF9xnW0UQi4FmCEVpNaWV6JP4TX7mN%2bftElwy%2fsEVfivdZyFLcQmEmkLWQbKl1jrPhOWzTs8JzGpQHbtsi80gOUB3XbVBBgL6qyg3FU4T6r0VkwJOJlJiUONPUDrvjy0scfEdyRqAm5W8wBKUSnIAxt%2bIwXOUKRa2LszP3spA0QJLChnRAUWaMtnKDAIAYXspzUbmDokVYp0NU7sxtzB1kYZ6oC95WbQt5A8y%2fS98Y7eceY34Fk95rxQ%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=109 Server-Timing: origin; dur=46 Server-Timing: ak_p; desc="1763777060458_34604952_496892052_15441_5719_5_10_-";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 3 subscribers
  • Views 24 views
  • Users 0 members are here
Related

Why you might see our Oops page

Dudley

You may occasionally run into what we call the Oops page:

image

This page appears for a few reasons:

  • Access restrictions: If you are trying to view something you are not allowed to, such as a private document. First, check whether you see the Oops page on the homepage or at an alternative URL.
  • Temporary issues: If the problem persists, the site may be experiencing an outage or you have triggered our bot protection. In both cases, the fix is simple: wait a few minutes and try again.

 

About Bot Protection

Our bot protection sometimes puts browsers into a short “time out” if it suspects automated traffic. This helps prevent traffic spikes from taking the site down. If this happens, it is rarely your fault. If you think you have been affected, even if the issue resolves, please report it.

 

When It Might Be More Serious

If the Oops page does not go away:

  • We could be offline due to an outage or a scheduled release.
  • Scheduled releases are announced on the site and rarely last more than three hours. If you still cannot access the site after four hours, it is unlikely to be a release.

 

What to Do Next

Use one of the contact methods listed on the Oops page. Discord is preferred. The #website-problems channel on discord is the fastest way to reach our Operations team.

And remember: do not assume we already know about the issue. If in doubt, reach out! Even if we are aware, your report helps us prioritise fixes.