--- title: Fix 4xx errors on Fourthwall shortDescription: Identify and resolve 400, 401, 403, and 422 errors when using your Fourthwall dashboard. articleType: Troubleshooting primaryTopic: fix-4xx-errors categories: - Troubleshooting tags: - 4xx-errors - bad-request - unauthorized - forbidden - error-codes - troubleshooting - browser-issues - permissions - dashboard-errors - partner-dashboard tasks: - Identify the type of 4xx error - Rule out browser or session issues - Check for missing or inconsistent inputs - Verify permissions and access - Resolve duplicate or conflicting actions - Report a Partner Dashboard redirect loop terms: - 400 error fourthwall - 401 unauthorized - 403 forbidden - 422 error - bad request error - dashboard error - fix error fourthwall - client side error - permission error - partner dashboard 400 - partners.fourthwall.com redirect loop - stuck in redirect labels: - troubleshooting - errors contextString: Available on all plans. Applies to all dashboard actions. breadcrumbPath: "Frequently asked questions > General FAQs > How to Fix 4xx Errors on Fourthwall" relatedModules: [] last_updated: '2026-05-19' path: frequently-asked-questions/account-and-plans/fix-4xx-errors --- # Fix 4xx errors on Fourthwall 4xx errors are client-side errors, meaning Fourthwall received the request but could not complete it due to invalid data, missing permissions, or platform constraints. Retrying the same action without changes will not fix a 4xx error. ## What are 4xx errors? 4xx errors indicate that the request reached Fourthwall successfully, but something about the request itself was invalid, unsupported, unauthorized, or conflicting. Common actions that can trigger 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 The specific error codes you may see: - **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 ### Step 1: Rule out browser or session-related issues Before making any 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 Fourthwall in a private or incognito window - Log out 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 caused by cached data, cookies, or a local browser conflict rather than your Fourthwall settings. ### Step 2: Check for missing or inconsistent inputs Missing or inconsistent inputs are 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 Examples: - 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 is supported for your product or fulfillment type (for example, changing the shipping origin only works for self-fulfilled products) - The setting applies to all products or only certain ones (for example, the compare-at price setting cannot be enabled or disabled for individual variants) - The option is available in your dashboard (for example, 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 External documentation from third-party services does not guarantee compatibility with Fourthwall. ### Step 5: Check for conflicts or duplicate actions Some 4xx errors occur when what you are trying to do conflicts with something that already exists or is in progress. This can happen when: - Creating something that already exists (for example, a product, page, or setting already set up in another browser tab) - Updating a resource that is not in a valid state (for example, editing a product that hasn't been fully saved, 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, review your existing settings and confirm the item is fully saved and not already being edited or processed. ### Step 6: Rule out temporary platform issues In rare cases, a 4xx error may stem from a temporary platform issue. Signs this may be the cause: - 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. ## Partner Dashboard 400 with a stuck redirect loop If you visit a valid `partners.fourthwall.com` URL and the page is stuck in a redirect loop or returns a persistent 400 error, and the shop is verified active, this is a platform-side issue. The browser troubleshooting steps above do not apply here. Do not spend time clearing cookies, switching browsers, or disabling extensions. This pattern usually means the Partner Dashboard route is failing to load on Fourthwall's end and needs engineering to replicate and fix. When you see this: - Copy the exact `partners.fourthwall.com` URL from your address bar - Contact [support@fourthwall.com](mailto:support@fourthwall.com) and share the URL so the team can replicate the loop and escalate to engineering - Include the creator or shop name if you have it, and the time you first saw the error ## 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 - Your browser and device details A persistent 400 with a redirect loop on a valid `partners.fourthwall.com` URL for an active shop is a platform-side issue that requires engineering escalation. Send the URL to support so the team can replicate it.