Skip to main content

Fix 4xx errors on Fourthwall

Understand and troubleshoot common client-side request errors

If you see an error message with a 4xx status code, such as 400, 401, or 403, it means Fourthwall received your request but was unable to complete it due to an issue with the request itself, insufficient permissions, or platform constraints.

This article explains what 4xx errors generally mean and how to troubleshoot them.

What are 4xx errors?​

4xx errors are client-side errors, meaning that while the request successfully reached Fourthwall, there was something invalid, unsupported, unauthorized, or conflicting about it. Simply retrying the same action without making any changes typically will not resolve a 4xx error.

Here are some activities that may lead to a 4xx error:

  • Saving or publishing a product
  • Creating or editing a custom page
  • Updating shipping settings
  • Connecting an app or integration
  • Publishing site or content changes

Some types of 4xx errors you may see​

You may encounter different 4xx codes depending on the action you are taking, such as saving/publishing a product, connecting an app or integration, making site or content changes, etc.

  • 400 Bad Request. The request contains invalid, incomplete, or conflicting data.
  • 401 Unauthorized. The request requires authentication or access that is missing or invalid.
  • 403 Forbidden. The request is understood but not allowed due to platform or permission restrictions.
  • 422 Unprocessable Entity. The request format is valid, but one or more values are incorrect, missing, or fail validation rules, so the request cannot be completed.

How to troubleshoot 4xx errors​

Follow these steps to identify and resolve the most common causes of 4xx errors.

Before making configuration changes, confirm the issue is not related to your browser or session state.

Try the following:

  • Refresh the page and retry the action
  • Open your Fourthwall in a private or incognito window
  • Log out of Fourthwall and log back in
  • Try a different browser or device
  • Temporarily disable browser extensions, especially ad blockers or privacy tools

If the action works in a different session or browser, the issue is likely related to cached data, cookies, or a local browser conflict rather than your Fourthwall settings. Otherwise, continue with the steps below.

Step 2: Check for missing or inconsistent inputs​

This is the most common cause of 4xx errors.

Make sure that:

  • All required fields are filled in
  • Optional fields are not partially or inconsistently configured
  • Product or site-level settings apply consistently

For example:

  • Pricing or compare-at settings must apply consistently across all product variants
  • Shipping and fulfillment settings must align with how the product is fulfilled

Step 3: Confirm the feature or configuration is supported​

Some actions fail because the behavior is not configurable or is limited by design.

Check whether:

  • The feature you are trying to use is supported for your product or fulfillment type (e.g., changing the shipping origin only works for self-fulfilled products)
  • The setting you are changing applies to all products or only certain ones (e.g., the compare-at price setting cannot be enabled or disabled for individual variants)
  • The option you are trying to enable is available in your dashboard (e.g., only currencies listed in your checkout settings can be enabled)

Step 4: Verify permissions and access​

Confirm that:

  • You are logged into the correct Fourthwall account
  • The action you are taking does not require additional permissions
  • The integration or app you are connecting to is officially supported by Fourthwall
note

Note: External documentation from third-party services does not guarantee compatibility with Fourthwall.

Step 5: Check for conflicts or duplicate actions​

Some 4xx errors happen when what you’re trying to do conflicts with something that already exists or is already in progress.

This can happen if you are:

  • Creating something that already exists. For example, trying to create a product, page, or setting that has already been set up on another browser tab/window.
  • Updating a resource that is not in a valid state. For example, editing a product that hasn’t been fully saved yet, is still processing a previous update, or was affected by a failed save attempt.
  • Performing multiple overlapping changes at once. For example, making several changes quickly or clicking Save multiple times before the first update finishes.

Before retrying the action, review your existing settings and make sure the item you’re updating is fully saved and not already being edited or processed.

Step 6: Rule out temporary platform issues​

In rare cases, a 4xx error may be caused by a temporary platform issue.

This may be the case if:

  • The error occurs even with minimal input
  • The same issue affects multiple users
  • The issue persists across browsers or sessions

If this happens, try again later and gather details before contacting support.

When to contact support​

Contact Fourthwall Support if you’ve confirmed your inputs, settings, and permissions are correct, the action is supported based on current documentation, and the error still occurs after completing the steps above. When reaching out:

  • Include what you were trying to do
  • The exact error message or status code
  • Screenshots or a short screen recording, and your browser and device details