Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Add-Ons page recognizing wrong Firefox version

  • 2 回覆
  • 1 有這個問題
  • 25 次檢視
  • 最近回覆由 linoleum

more options

I have installed Firefox 65.0 on Debian Stretch following the instructions on this website: https://linuxconfig.org/how-to-install-latest-firefox-browser-on-debian-9-stretch-linux. When I execute "firefox --version" on my terminal I get "Mozilla Firefox 65.0", the same which is shown in "Help -> About Firefox".

However, when I try to install some add-ons I get a warning "You're using Firefox 51.0"- it seems to think that I'm still using the old version. Am I? How can I fix it?

I have installed Firefox 65.0 on Debian Stretch following the instructions on this website: https://linuxconfig.org/how-to-install-latest-firefox-browser-on-debian-9-stretch-linux. When I execute "firefox --version" on my terminal I get "Mozilla Firefox 65.0", the same which is shown in "Help -> About Firefox". However, when I try to install some add-ons I get a warning "You're using Firefox 51.0"- it seems to think that I'm still using the old version. Am I? How can I fix it?
附加的畫面擷圖

被選擇的解決方法

The User Agent you used to post this thread is Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0

So it appears to be either from a UA related Extension you have installed or it was manually modified.

https://support.mozilla.org/en-US/kb/how-reset-default-user-agent-firefox

從原來的回覆中察看解決方案 👍 1

所有回覆 (2)

more options

選擇的解決方法

The User Agent you used to post this thread is Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0

So it appears to be either from a UA related Extension you have installed or it was manually modified.

https://support.mozilla.org/en-US/kb/how-reset-default-user-agent-firefox

由 James 於 修改

more options

You're right. It was manually modified by an old add-on I had already removed a long time ago. The link you provided solved the issue, thanks.