We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

I get bad request from the official Mozilla repo

  • 3 ответа
  • 0 имеют эту проблему
  • 3 просмотра
  • Последний ответ от cor-el

more options

I get bad request from the official Mozilla repo: Err:8 https://packages.mozilla.org/apt mozilla/main all Packages

 400  Bad Request [IP: 34.160.78.70 443]

Did the URL change or smth?

I get bad request from the official Mozilla repo: Err:8 https://packages.mozilla.org/apt mozilla/main all Packages 400 Bad Request [IP: 34.160.78.70 443] Did the URL change or smth?

Все ответы (3)

more options

What are you doing??? How about providing more detail on exactly what you're doing to get that error. What OS? What Desktop? X11 or Wayland?

more options

I had installed firefox for debian using the mozilla's official repo.

no problems for months but now i am getting that bad request error that i had mentioned above when i try to update my system using `apt update` and `apt upgrade`.

OS: Debian GNU/Linux trixie/sid x86_64 Host: Z170XP-SLI Kernel: 6.7.12-amd64 Uptime: 3 hours, 25 mins Packages: 3229 (dpkg) Shell: bash 5.2.21 Resolution: 3440x1440 DE: Plasma 5.27.10 WM: KWin Theme: [Plasma], Breeze [GTK2/3] Icons: [Plasma], breeze [GTK2/3] Terminal: konsole CPU: Intel i5-6500 (4) @ 3.600GHz

Изменено szemawy

more options

A 400 "Bad Request" error issue is usually caused by corrupted cookies.

You can try these steps in case of issues with webpages:

You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • hold down the Shift key and left-click the Reload button
  • press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • press "Command + Shift + R" (Mac)

Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Settings), click the padlock icon (Clear cookies and site data) for the domain in the selected tab.

"Remove the Cookies" for websites that cause problems:

  • Settings -> Privacy & Security
    Cookies and Site Data: "Manage Data"

"Clear the Cache":

  • Settings -> Privacy & Security
    Cookies and Site Data -> Clear Data -> [X] Cached Web Content -> Clear

Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or if userChrome.css/userContent.css is causing the problem.

  • switch to the Default System theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window

You can check for issues with Enhanced Tracking Protection. Firefox shows a purple shield instead of a gray shield at the left end of the location/address bar in case Enhanced Tracking Protection is blocking content.

  • click the shield icon for more detail and possibly disable the protection

You can check the Web Console for relevant-looking messages like blocked content.