Skip to content
This repository has been archived by the owner on May 13, 2024. It is now read-only.

Latest commit

 

History

History
57 lines (36 loc) · 4.23 KB

troubleshooting.md

File metadata and controls

57 lines (36 loc) · 4.23 KB
Raw

Index ┊ Back

Troubleshooting

Sometimes things go south. The GitHub Actions deployment can fail for some reason, or some configuration changed or was accidentally removed.

Starting over

If you attempted to deploy Wildebeest in your account and something failed, or you simply want to reinstall everything from scratch again, you need to do manual checkups and cleaning before you start over.

  • Go to your zone DNS settings and delete the CNAME record that points to wildebeest-username.pages.dev
  • Go to your account Pages section and delete the wildebeest-username project (make sure you remove the custom domain first if it's been configured).
  • Go to your account Workers section and delete the wildebeest-do and wildebeest-consumer-username workers.
  • Go to your account Workers / KV section and delete the wildebeest-username-cache and wildebeest-terraform-username-state namespaces.
  • Go to your account Workers / D1 and delete the wildebeest-username database.
  • Launch Zero Trust, select your account, go to Access / Applications and delete the wildebeest-username application.
  • Go to https://deploy.workers.cloudflare.com/, open the site settings in your browser and delete all the cookies and local storage data.
  • Delete your GitHub wildebeest forked repo.

You can now start a clean install.

Error 1102

Wildebeest runs cryptographic functions and can process lots of data internally, depending on the size of the instance and social graph. It's possible that, in some cases, a request exceeds the Worker's resource limits in the free plan.

We will keep optimizing our code to run as fast as possible, but if you start seeing 1102 errors when using your Wildebeest pages and APIs, you might need to upgrade to Workers Unbound, which provides much higher limits, as mentioned in the requirements:

  • Go to your Account Page / Pages, select the wildebeest-username project, go to Settings / Functions and change the usage model to Unbound.
  • Go to your Account Page / Workers, select the wildebeest-do project, go to Settings / General and change the usage model to Unbound. Do the same for the wildebeest-consumer-username project. Go to Account Page / Workers / Overview again and make sure the Default Usage Model is Unbound.

unbound

After you change your Pages project to Unbound, you need to redeploy it. Go to GitHub Actions in your repo, select the latest successful deploy, and press Re-run all jobs.

WAF false positives

If your zone is on Free plan, you do not need to worry about false positives. We have crafted free WAF rules covering targeted high severity vulnerabilities.

If your zone is on Pro plan or above and you have deployed WAF managed rules in this zone, there is a chance a few incoming messages are blocked as malicious, such as messages containing code examples. When this happens, you may miss these messages in your feeds. These blocking events can be examined further using Security Events where matching ruleset and rule is logged.

Block event example

Block event example screenshot

Depending on your existing setup, you can:

  • Lower OWASP ruleset's sensitivity

  • Skip (part of) managed rules, matching hostname social.example which path contains /ap/users/ and /inbox

    Skip rule example

    Skip rule example screenshot

Index ┊ Back