Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Troubleshooting: "Bad Request" Error

What this means? 

 A "Bad Request" error is a bit different from a connection drop. While your internet might be fine, the data your app tried to send got "scrambled" or corrupted on its way to the server. Think of it like a letter that got smudged in the rain and the post office can’t read the address anymore.

How to fix it:

1. The "Quick Refresh" Sequence

Most malformed requests are temporary glitches caused by a tiny data packet getting lost.

  • Wait and Retry: As the error suggests, wait about 10–20 seconds. This allows any temporary server-side traffic jams to clear before you try again.
  • Soft Refresh: Press the Refresh button or F5. This forces the app to try sending the data "from scratch" rather than retrying the corrupted version.
  • Check Your Input: If you just filled out a form, look for special characters (like symbols, emojis, or extra spaces) that might be confusing the system.

2. Clearing the "Digital Clutter"

If a simple retry doesn't work, the app might be stuck using old, "bad" data stored in its orary memory (cache).

Action Why it works
Restart the App Closing the app fully (not just minimizing it) clears its immediate working memory and forces a fresh login/session.
Clear Browser Cache If using a web browser, old "cookies" can sometimes send expired information, leading to a "Bad Request."
Log Out and Back In This resets your security "token," which is a common cause for requests becoming "malformed."

3. Steps You Might Have Missed

If the basic restart doesn't do the trick, the issue might be hidden in your settings or browser extensions.

  • Check for Extension Conflicts: Ad-blockers or privacy extensions can sometimes "edit" the data your app sends, making it look "malformed" to the server. Try turning them off temporarily.
  • Update the App: If you are using an older version of an app, it might be trying to talk to the server in a "language" the server no longer understands. Check for updates in the App Store or settings.

4. When to Escalate

If you have restarted the app and cleared your cache but still see "Bad Request":

  1. Try a Different Browser/Device: Open the app on your phone or a different browser (like switching from Chrome to Edge). If it works there, the issue is specific to your original browser's settings.
  2. Check the URL: If you typed the address manually, ensure there aren't any weird symbols (like %20 or ??) at the very end of the link.

Still stuck?  If this happens while uploading a file, the file itself might be too large or in a format the server doesn't support. Try renaming the file to something simple (no spaces or symbols) and try again.  If the issue is still not resolved after following these steps, please contact our support team for further assistance.