Why You May See a 403 Forbidden Error While Editing Your Website

What This Is

A 403 Forbidden error means the request was blocked before the website or editor could complete the action.

In most cases, this does not mean your website is broken. It usually means a security system temporarily blocked the request because the activity appeared unusual or automated.


Why This Happens

Bounce Rental Solutions uses AWS-based security protections to help prevent:

  • Spam traffic
  • Automated bot activity
  • Fake form submissions
  • Abusive requests
  • Website overload attempts

These protections are important because public websites are constantly targeted by automated systems attempting to abuse forms, overload pages, or send repeated requests.

Sometimes, legitimate user activity can accidentally trigger these protections.


Common Causes

A 403 Forbidden error is most likely to happen when:

  • Saving website edits repeatedly in a short period
  • Refreshing pages excessively
  • Moving through the editor very quickly
  • Triggering many requests at once
  • Performing rapid repetitive actions

From the security system’s perspective, this behavior can resemble automated bot traffic, even when the activity is legitimate.


What To Do First

If you encounter a 403 Forbidden error:

  • Stop refreshing the page repeatedly
  • Wait a few minutes before trying again
  • Slow down editing activity temporarily
  • Retry the action after the temporary block clears

In many cases, the restriction removes itself automatically after a short period.

Continuing to spam refreshes or repeated saves can extend the block duration.


When to Contact Support

If the issue continues after waiting, contact support and include:

  • The page you were editing
  • The action you were attempting
  • Approximately when the error occurred
  • Any screenshots of the error message

This helps the support team review what triggered the block and determine whether security settings need adjustment.


Important Notes

A 403 error is usually security-related, not a sign of data loss or website failure.

Most cases are temporary and triggered by behavior patterns that accidentally resemble automated traffic.

Because these protections help defend tenant websites against real abuse and spam attacks, they cannot simply be disabled entirely.