Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
90 changes: 90 additions & 0 deletions account/abuse-procedure.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
---
title: Abuse Procedure
description: How bunny.net handles abuse reports for content hosted or delivered through our platform.
---

bunny.net is a platform service provider acting as a passive distributor of third-party information. We are not a publisher and do not moderate content except as set out in our published procedures (updated from time to time). bunny.net takes no responsibility to our Customers or users for data and content uploaded by Customers or third parties, and is not liable for that content.

We take abuse reports seriously while giving customers a fair opportunity to review and address complaints. This procedure outlines how we handle general abuse reports, including how we verify complaints and how customers can respond.

<Note>
We operate on a good-faith, voluntary basis, aiming to meet industry best practice while taking into account relevant national and international regulatory guidance and applicable legislation. We have no obligation to respond to allegations of abuse or to take action, and we are not liable for our acts or omissions other than as set out in our [Terms of Service](https://bunny.net/tos). We reserve the right to amend or withdraw this procedure at any time.
</Note>

## What is abuse?

We consider the following to be abuse, or complaints of alleged abuse:

- Misinformation (sometimes known as "fake news")
- Violation of our Terms of Service (such as publishing illegal content, or harmful activity such as hacking, phishing, or malware)
- Violent threats and harassment
- Child Sexual Abuse Material (CSAM)

Misinformation may be described as verifiably false or misleading information created, presented, and disseminated for economic gain or to intentionally deceive the public, and which may cause public harm.

We do **not** consider the following to be abuse:

- Disagreements over political or news articles
- Attempts to silence commentary or alternative points of view
- Defamatory, aggressive, or insulting content
- Reviews of service providers or products

## Our process

Reports can be submitted via our [abuse form](https://bunny.net/abuse/).

### Receiving and reviewing the report

When we receive an abuse report related to content hosted or delivered through our platform, our team reviews it to determine:

- Whether the allegation is valid and specific (vague or generic complaints may require further clarification)
- Whether the content violates applicable laws or our Acceptable Use Policy

We do not take immediate action unless the content is clearly illegal (such as phishing, malware, or CSAM). For all other cases, we first notify the customer and allow them to review the allegations.

### Notifying the customer

Once we verify the report, we notify the customer responsible for the content by email, and the report is visible in the customer dashboard. The notice includes:

- A summary of the allegation, including the details provided by the reporter
- A request to review the report and take action if necessary
- A response timeline, typically 48 hours for all abuse reports except those related to misinformation

Until the response period has passed, no action is taken on the content. We do not, as a matter of routine, provide the customer with personal data relating to the complainant.

### Customer response options

- **Address the report:** Modify or remove the content, or provide additional information to clarify the situation.
- **Dispute the report:** Explain why the content should not be removed, and share any supporting documentation (such as licenses or legal permissions).

We review the response and, if necessary, work with the customer to ensure compliance with applicable regulations or our Acceptable Use Policy.

### No immediate suspension or blocking

Unlike DMCA or CSAM reports, we do not suspend Pull Zones or remove content for general abuse allegations. Our goal is to work with the customer to verify and resolve the issue. However, if a customer fails to respond in time, or the content clearly violates our policies, we may take further action.

### Repeat offenses

If a customer repeatedly receives abuse reports and does not take appropriate action, we may require faster response times for future reports, restrict access to certain services or features, or suspend or terminate the account. We always attempt to work with the customer first before escalating.

## Frequently asked questions

**Will my Pull Zone or content be suspended for fake news or misinformation?**

No. We do not suspend Pull Zones or remove content solely based on abuse reports alleging fake news or misinformation.

**Will my Pull Zone or content be suspended immediately?**

No. We do not suspend Pull Zones or remove content immediately for general abuse reports. We give customers an opportunity to review and address the complaint first.

**What happens if I don't respond to an abuse report?**

If no response is received within the given timeframe, we may take further action, including potential suspension of the specific URL. This depends on the type of abuse report.

**Can I dispute an abuse report?**

Yes. If you believe a report is incorrect or invalid, submit a response explaining why, along with supporting evidence. bunny.net will review the response and decide, at its own discretion and with no liability, whether to uphold the allegation or reinstate the content in whole or in part.

**What types of abuse reports require immediate action?**

Reports related to illegal activity (such as CSAM, phishing, or malware) may require immediate content blocking and further escalation. All other reports follow this procedure.
49 changes: 49 additions & 0 deletions account/account-suspended.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
---
title: Account Disabled or Suspended
description: Why a bunny.net account becomes disabled or suspended, and how to resolve each state.
---

If you see a message that your account is disabled or suspended, this guide explains the possible reasons and how to resolve them. There are two distinct states.

## Temporarily disabled

This is usually a temporary status that you can resolve by addressing the underlying issue.

**Common causes:**

- **Trial expired:** Trial accounts are automatically disabled when the trial period ends, unless you top up your account. This prevents unexpected charges.
- **Negative balance:** If charges accrue without successful payment for several days, the account may be disabled until the outstanding balance is cleared.

**Resolution:**

1. Log in to your account. You'll be guided through recharging or resolving your balance.
2. If you need help, [contact support](https://bunny.net/contact/).

## Suspended

A suspension is more serious. It can result from automated risk detection or a manual review following a violation of our [Terms of Service](https://bunny.net/tos) or [Acceptable Use Policy](https://bunny.net/acceptable-use/).

**Common causes:**

- **Signup risk detected**, based on signals such as:
- Use of VPNs, proxies, or anonymized IP addresses during signup
- Mismatches between IP address and billing information
- Registrations from regions flagged as high-risk by our payment processor
- **Policy violations**, such as:
- Attempted fraud or abuse of platform resources
- Hosting prohibited content or engaging in restricted activities

**Resolution:**

1. [Contact support](https://bunny.net/contact/) to request details about the suspension.
2. Be prepared to provide identification, account verification, or additional context to assist the review.

Depending on the nature and severity of the issue, some accounts suspended for policy violations may not be reinstated.

<Note>
Accounts created using anonymizing services such as VPNs or proxies may be permanently restricted. If your account was suspended under these conditions, you may need to create a new account using a different email address and a direct, non-anonymized connection.
</Note>

## Need help?

If you're unsure which state your account is in or what to do next, [contact support](https://bunny.net/contact/). We can help review your account status and determine the right resolution.
40 changes: 40 additions & 0 deletions account/dmca-procedure.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
title: DMCA Procedure
description: How bunny.net handles DMCA and copyright takedown requests for customer content.
---

bunny.net takes DMCA and copyright requests seriously, protecting intellectual property rights while giving customers a fair chance to respond. This page outlines how we handle DMCA and copyright notices related to customer content.

## Receiving and verifying the report

When we receive a DMCA or copyright report, we first verify its authenticity. Our team reviews the report to confirm it meets the legal requirements of a valid claim, ensuring it is not fraudulent and that it pertains to content hosted on our platform.

## Notifying the customer

Once we verify a claim, we notify the customer responsible for the content. Our support team sends an official notice by email, and it is also available in your dashboard. The notice includes the details of the report and clear instructions on the next steps.

Customers have **48 hours** to respond from the time the email is sent, with two options:

- **Option 1: Remove the content.** If you believe the claim is valid, remove the infringing content from your account. In the dashboard, open the Abuse Case to verify the content has been removed. Once confirmed, the case is marked resolved.
- **Option 2: File a counter-claim.** If you believe the report is incorrect or invalid, file a counter-claim within the same 48-hour window. A counter-claim is a legal statement contesting the validity of the request, and it triggers the next steps in the resolution process.

## Blocking the content

If no action is taken within the initial 48 hours (the content is neither removed nor a counter-claim filed), the content is blocked and the Pull Zone may be suspended. The content stays inaccessible to the public until the matter is resolved.

When a counter-claim is submitted, the content stays blocked while the reporter is notified. The reporter has **10 to 14 days** to respond or initiate legal action. If they don't within that window, we unblock the content after the 14-day period.

## Illegal or highly sensitive content

Some content types are treated differently from standard claims:

- **Illegal content** (such as phishing or malware): We block it immediately. The DMCA process does not apply, and the content remains blocked pending further investigation or legal action.
- **Sports streams:** Because of copyright and broadcasting rights, we immediately block content reported as an unlicensed sports stream. To unblock it, you must provide proof that you are licensed to stream the content. Without proof, it remains blocked.

## Restoring content after a takedown

Once a valid takedown has occurred, you may not restore or re-upload the removed content, whether under the same name or a different one. If content is repeatedly re-uploaded after being taken down, we will issue further notices and require its removal again. Continued re-uploads may result in suspension of the entire account, to ensure compliance and protect intellectual property rights.

## After a report is filed

Once a report is filed and the content is blocked or a counter-claim is submitted, the next steps are governed by legal requirements. If the reporter does not respond or take legal action within the 10 to 14 day window after a counter-claim, the content is unblocked and restored. If legal action is initiated, the content remains blocked until the dispute is resolved.
22 changes: 22 additions & 0 deletions cdn/connectivity.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,28 @@ On the Standard Network, IPv6 origin connectivity is provided on a best-effort b

If guaranteed IPv6 connectivity to your origin is required, enabling Origin Shield routes all origin traffic through a Volume Network location with native dual-stack support.

## 502 and 504 errors
Comment thread
dbContext marked this conversation as resolved.

A `502 Bad Gateway` means an edge server received an invalid response from your origin. A `504 Gateway Timeout` means the origin didn't respond in time. When the origin is unreachable, edge servers serve from cache where possible and only return the error when the file isn't cached. Common causes:

- **Origin offline:** The most common cause. Edge servers can't connect to your origin and the file isn't in cache.
- **Firewall blocking edge servers:** Because the CDN proxies all your traffic, origin firewalls or security software can mistake the volume of edge requests for an attack and block them. Whitelist the [edge server IP list](https://api.bunny.net/system/edgeserverlist) ([IPv6](https://api.bunny.net/system/edgeserverlist/ipv6)) and update it periodically as the network changes.
- **Network congestion:** A rare, transient routing problem between an edge location and a distant origin.
- **Timeouts:** By default Bunny waits 10 seconds for a TCP connection and 60 seconds for the origin to start sending data. Immediate 502s usually mean an origin firewall or WAF is rejecting the connection. These timeouts are configurable via Safehop.

Use the [bunny.net diagnostic tools](https://tools.bunny.net/) to test latency, traceroutes, and HTTP requests from over 120 locations and see whether specific regions are blocked or the origin is slow. If you've ruled out the causes above, contact [support@bunny.net](mailto:support@bunny.net).

## Origin redirect loops

If your CDN URLs return a 301 redirect back to your own domain, the origin is issuing that redirect and the CDN is forwarding it. Bunny CDN never returns a 301 on its own, except for hotlink protection. Check the following:

- **Origin URL host:** Make sure the Pull Zone Origin URL matches the exact domain your site serves from, including the `www` or non-`www` version. A mismatch triggers your origin's canonical redirect.
- **Origin URL protocol:** If your server forces HTTPS, set the Origin URL to `https://`. An `http://` Origin URL against an HTTPS-only origin produces a redirect.
- **Origin redirect or rewrite rules:** Check your server configuration for redirect or rewrite rules affecting your assets.
- **Hotlink protection:** If enabled, whitelist every domain the CDN serves (both `www` and non-`www`), with no protocol or slashes in the hostname field.

After any change, purge the full Pull Zone cache and wait for it to sync, since cached 301s persist on the edge.

## CDN Acceleration and IPv6 Origins

bunny.net's CDN Acceleration feature supports dual-stack origin connectivity when used with Bunny DNS.
Expand Down
38 changes: 37 additions & 1 deletion cdn/integrations/cms/discourse.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,41 @@
---
title: Discourse
description: Speed up your Discourse forum with bunny.net CDN for faster page loads and improved performance.
url: https://support.bunny.net/hc/en-us/articles/360000549272-How-to-speed-up-Discourse-with-BunnyCDN
---

Discourse has built-in CDN support. This guide walks you through pointing it at Bunny CDN.

<Steps>
<Step title="Create a Pull Zone">
Log in to your [bunny.net dashboard](https://dash.bunny.net) and open the **Add Pull Zone** page. Choose a name for your zone, then set the origin URL to your Discourse forum (for example, `discourse.example.com`).

<Frame>
![Creating a Pull Zone for Discourse](/images/cdn/integrations/cms/discourse-add-zone.png)
</Frame>

Select a pricing tier and click **Add Pull Zone**. For more detail, see [How to create your first Pull Zone](/cdn/quickstart).
</Step>
<Step title="Configure Discourse with your Pull Zone">
Open your `app.yml` configuration file and find the following lines:

```yaml
## the origin pull CDN address for this Discourse instance
DISCOURSE_CDN_URL: https://discourse-cdn.example.com
```

If they aren't present, add them below the other `DISCOURSE_` variables. Replace the `DISCOURSE_CDN_URL` value with your Pull Zone hostname.

<Frame>
![Setting DISCOURSE_CDN_URL in app.yml](/images/cdn/integrations/cms/discourse-cdn-url.png)
</Frame>
</Step>
<Step title="Rebuild the Discourse container">
Apply the new configuration by rebuilding the container:

```bash
./launcher rebuild app
```

Once the rebuild finishes, your forum is served through Bunny CDN. To confirm everything is working, see [Verify your configuration](/cdn/verify-configuration).
</Step>
</Steps>
47 changes: 46 additions & 1 deletion cdn/integrations/cms/drupal.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,50 @@
---
title: Drupal
description: Integrate bunny.net CDN with your Drupal website for faster content delivery and improved performance.
url: https://support.bunny.net/hc/en-us/articles/360018510091-How-to-speed-up-your-Drupal-website-with-BunnyCDN
---

Drupal supports CDN delivery through the [CDN module](https://www.drupal.org/project/cdn), which rewrites your asset URLs to serve them through Bunny CDN. This guide walks you through installing and configuring it.

<Steps>
<Step title="Create a Pull Zone">
Log in to your [bunny.net dashboard](https://dash.bunny.net) and create a new Pull Zone with your Drupal site as the origin URL. For details, see [How to create your first Pull Zone](/cdn/quickstart).

Match the protocol of your site exactly. If your Drupal site runs on HTTPS, enable HTTPS on the Pull Zone; if it runs on HTTP only, leave HTTPS disabled. A mismatch will cause errors.

<Note>
You can set a long Cache-Control time for Drupal. The CDN module serves updated elements from new URLs, so changes appear immediately without waiting for the cache to expire.
</Note>
</Step>
<Step title="Install the CDN module">
Download the latest `.tar.gz` release of the [Drupal CDN module](https://www.drupal.org/project/cdn) and copy its download URL. You'll need SSH or FTP access to your site.

In the Drupal admin, select **Manage**, then **Extend**, then **Install new module**.

<Frame>
![Drupal Extend page with the Install new module button](/images/cdn/integrations/cms/drupal-extend-install-module.png)
</Frame>

Paste the `.tar.gz` URL, click **Install**, and provide your SSH/FTP credentials when prompted. When the installer finishes, click **Enable newly added modules**.

Scroll to the **Web Services** section, select the **CDN** and **CDN UI** modules, then click **Install**.

<Frame>
![Enabling the CDN and CDN UI modules](/images/cdn/integrations/cms/drupal-enable-cdn-modules.png)
</Frame>
</Step>
<Step title="Configure the CDN module">
Go to **Manage → Configuration**, scroll to the bottom, and click **CDN Integration**. On the **Status** tab, make sure **Serve files from a CDN** is enabled.

<Frame>
![Enabling Serve files from a CDN](/images/cdn/integrations/cms/drupal-cdn-status.png)
</Frame>

Open the **Mapping** tab, select **Simple** mapping, choose **Serve all files**, and enter your Pull Zone hostname in the field on the right. Click **Save configuration**.

<Frame>
![Configuring the CDN mapping](/images/cdn/integrations/cms/drupal-cdn-mapping.png)
</Frame>
</Step>
</Steps>

Your Drupal site now serves static assets through Bunny CDN.
Loading