# \[Resolved\] Is MantisBT and the wiki being inaccessible for everyone?

**URL:** <https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510>\
**Category:** Feedback\
**Created:** [April 23, 2025, 6:08pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510 "2025-04-23T18:08:33Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [April 23, 2025, 6:08pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/1 "2025-04-23T18:08:33Z")

</div>

I am getting a Bad Gateway error when trying to browse to the wiki or MantisBT portions of [gramps-project.org](http://gramps-project.org) domain. MantisBT was accessible yesterday.

We were getting a similar error for the wiki a while ago. Maybe it is the same problem? Or a flaky piece of network hardware at our host?

 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/e/e20ae3bb059afd7a4361a5f1575e3512c5cf087e.png)

### References:

- [[Resolved]Suddenly… Forbidden access to Gramps Wiki](https://gramps.discourse.group/t/resolved-suddenly-forbidden-access-to-gramps-wiki/7092/12) on 24 Feb 2025
- [Where is CloudFlare implemented in resolving Gramps-project.org URLs](https://gramps.discourse.group/t/where-is-cloudflare-implemented-in-resolving-gramps-project-org-urls/6833)

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [April 23, 2025, 6:19pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/2 "2025-04-23T18:19:35Z")

</div>

It looks like we are having problems with our server again.

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [April 23, 2025, 6:24pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/3 "2025-04-23T18:24:30Z")

</div>

I used your link to gramps-project and the page took several minutes to load. From there, the link to ‘Bugs’ took even longer but again, the page did eventually load.

I gave up trying to log in to Mantis; it’s too slow to be usable.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [April 23, 2025, 6:48pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/4 "2025-04-23T18:48:49Z")

</div>

Our webmaster ( @gramps-project ) will need some time to see this thread and contact our hosting service.

Don’t give up on filing [that bug](https://gramps.discourse.group/t/descendant-indented-tree-local-workaround-no-longer-working-in-5-2-4-plus-total-failure-in-6-0-1/7447/14). Just put the task in your backpocket for a couple days.

---

<div class="post-metadata">

**Author:** ![gramps-project](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/gramps-project/32/398_2.png) [@gramps-project](https://gramps.discourse.group/u/gramps-project)\
**Post date:** [April 23, 2025, 9:05pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/5 "2025-04-23T21:05:44Z")

</div>

Investigated the issue.

External spike in website traffic looks to be automated and now blocked.

 ![2025-04-24 11_39_33-gramps-project.org _ gramps-project.org _ Cloudflare](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/b/b6b44642323b07c281aae227b612908311853d61.png)  
Five times the normal website traffic seems to have been an AI-bot!

Websites are working.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [April 23, 2025, 10:24pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/6 "2025-04-23T22:24:21Z")

</div>

We seem to have a new “Verifying you are a person” test.

 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/9/90197963de0c696aa6b352f7eeb935c4dfbc0d9b.png)

This “Verify you are human by completing the action below.” verification can cause problems. So inserting this troubleshooting note for future reference.

The “verify you are human” loop on Cloudflare often occurs due to browser settings or extensions interfering with the verification process. To resolve this, try clearing your browser cookies, disabling any ad blockers or privacy extensions, and using your browser’s safe mode or private browsing mode.

---

<div class="post-metadata">

**Author:** ![gramps-project](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/gramps-project/32/398_2.png) [@gramps-project](https://gramps.discourse.group/u/gramps-project)\
**Post date:** [April 23, 2025, 10:42pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/7 "2025-04-23T22:42:00Z")

</div>

> [@emyoulation](#):
>
> We seem to have a new “Verifying you are a person” test.

~~It is temporary and will go away soon.~~

The cloudflare test seems to have gone.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [April 24, 2025, 2:05am UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/8 "2025-04-24T02:05:24Z")

</div>

Thanks for the update and working on this.

That CloudFlare verification uses cookies. So will probably be periodic … until the cache expires.

---

<div class="post-metadata">

**Author:** ![Nick-Hall](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/nick-hall/32/95_2.png) [@Nick-Hall](https://gramps.discourse.group/u/Nick-Hall)\
**Post date:** [April 24, 2025, 4:23pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/9 "2025-04-24T16:23:54Z")

</div>

It seems very slow again today.

---

<div class="post-metadata">

**Author:** ![PLegoux](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/plegoux/32/413_2.png) [@PLegoux](https://gramps.discourse.group/u/PLegoux)\
**Post date:** [April 25, 2025, 10:48am UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/10 "2025-04-25T10:48:12Z")

</div>

I’m seeing this check more and more often these days. I haven’t noticed if it’s on Cloudflare every time, but yes, there are measures taken against something, AI-bot or otherwise, on the internet lately.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [June 4, 2025, 1:54pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/13 "2025-06-04T13:54:49Z")

</div>

MantisBT is being very slow for me today. Is it my system or the site?

Slow in loading the initial view. Glacial when adding a note to an issue.

---

<div class="post-metadata">

**Author:** ![Cynwrite](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@Cynwrite](https://gramps.discourse.group/u/Cynwrite)\
**Post date:** [June 4, 2025, 5:29pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/14 "2025-06-04T17:29:25Z")

</div>

It is super slow for me as well.

---

<div class="post-metadata">

**Author:** ![l0f4r0](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@l0f4r0](https://gramps.discourse.group/u/l0f4r0)\
**Post date:** [June 4, 2025, 5:51pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/15 "2025-06-04T17:51:57Z")

</div>

Yes, very slow right now from France as well, no matter the browser

---

<div class="post-metadata">

**Author:** ![gramps-project](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/gramps-project/32/398_2.png) [@gramps-project](https://gramps.discourse.group/u/gramps-project)\
**Post date:** [June 4, 2025, 9:51pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/16 "2025-06-04T21:51:49Z")

</div>

> [@gramps-project](#):
>
> External spike in website traffic looks to be automated and now blocked.

Same issue as before external spike in website traffic, I’ve blocked the ip range temporarily.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [June 5, 2025, 12:41am UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/17 "2025-06-05T00:41:24Z")

</div>

Thanks for fixing that, Sam!

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [June 5, 2025, 2:05pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/18 "2025-06-05T14:05:49Z")

</div>

> [@gramps-project](#):
>
> Same issue as before external spike in website traffic,

Other (non-genealogical) forums I frequent have had to implement anti-bot features recently. Most seem to be using Cloudflare. They had to do that because they were being swamped (number of users on line: 10,000) by badly behaved bots that were scraping everything. I’ve also noticed that some on-line retail outlets are also using Cloudflare to verify visitors to their site are human and not bots before letting you browse their site.

I’d hazard a guess the bots are all looking for content to use to train AI models.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [June 8, 2025, 6:58am UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/19 "2025-06-08T06:58:44Z")

</div>

And [gramps-project.org](http://gramps-project.org) is suddenly unresponsive again tonight.

More than a minute between request and response.

(Remember the bad old days of acoustical modem dialup to BBS systems where that would have been an excellent response time?)

---

<div class="post-metadata">

**Author:** ![gramps-project](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/gramps-project/32/398_2.png) [@gramps-project](https://gramps.discourse.group/u/gramps-project)\
**Post date:** [June 8, 2025, 8:52am UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/20 "2025-06-08T08:52:37Z")

</div>

> [@emyoulation](#):
>
> And [gramps-project.org](http://gramps-project.org) is suddenly unresponsive again tonight.

Blocked yet another range of IP addresses! Third time in five days!

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [June 8, 2025, 3:46pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/21 "2025-06-08T15:46:54Z")

</div>

> [@gramps-project](#):
>
> Blocked yet another range of IP addresses

On the main forum I frequent, that approach didn’t work, The problem was not fixed until the Admins implemented Cloudflare’s anti-bot software. It does mean you have to wait for a few seconds while Cloudflare checks you are human but a few seconds delay is waaaaaaay better than waiting ages or not even being able to reach the site at all.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [June 8, 2025, 5:14pm UTC](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510/22 "2025-06-08T17:14:42Z")

</div>

Do you know which Cloudflare service those Admins are using? [Admin: Free plan]

[Cloudflare has been active](https://gramps.discourse.group/t/where-is-cloudflare-implemented-in-resolving-gramps-project-org-urls/6833) on **gramps-project.org** since the beginning of the year. That’s probably using the **Bot Fight Mode** that comes with the Free plan.

Cloudflare’s Pro and Business plans have **Super Bot Fight Mode**. And for the really ambitious, there are hands on customizable tools in their **Bot Management for Enterprise** level.

[Next page](https://gramps.discourse.group/t/resolved-is-mantisbt-and-the-wiki-being-inaccessible-for-everyone/7510.md?page=2)
