On Monday September 25th from 10PM EDT - 12AM EDT (2AM UTC - 4AM UTC on September 26th), we will be performing system maintenance on the Firefox Accounts databases for two hours. During the maintenance window, there will be brief periods of a few minutes where users will not be able to login to their accounts. Please try again at a later time.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Learn More

"The server encountered an error", unable to view activity or file owner information in google drive

  • 3 отговора
  • 0 имат този проблем
  • 44 изгледи
  • Последен отговор от cor-el

more options

I am currently unable to view any file activity or ownership information in Google Drive in a shared folder. I have tried the following troubleshooting steps:

  • Quit and reopen firefox
  • Relaunched firefox in safe mode/extensions disabled
  • Cleared cookies
  • Tried in other browsers (works in Librewolf, Brave and Chromium; doesn't work in any Firefox browser (Nightly, beta, standard)
I am currently unable to view any file activity or ownership information in Google Drive in a shared folder. I have tried the following troubleshooting steps: * Quit and reopen firefox * Relaunched firefox in safe mode/extensions disabled * Cleared cookies * Tried in other browsers (works in Librewolf, Brave and Chromium; doesn't work in any Firefox browser (Nightly, beta, standard)
Прикачени екранни снимки

Избрано решение

cor-el said

You can check for issues with Total Cookie Protection. You can check the Web Console for relevant-looking messages.

Thank you for your help. Using the web console, I noticed there was a referrer mismatch in a bad request. Changing network.http.referer.spoofSource from true to false in about:config fixed the issue for me.

Прочетете този отговор в контекста 👍 0

Всички отговори (3)

more options

Полезно?

more options

Избрано решение

cor-el said

You can check for issues with Total Cookie Protection. You can check the Web Console for relevant-looking messages.

Thank you for your help. Using the web console, I noticed there was a referrer mismatch in a bad request. Changing network.http.referer.spoofSource from true to false in about:config fixed the issue for me.

Полезно?

more options

network.http.referer.spoofSource is false by default. Did you change this pref (and possibly others) because you read about this?

WARNING: modifying prefs directly via the about:config page can sometimes break Firefox or cause strange behavior, and there is no guarantee that this will keep working in future Firefox releases, so be cautious with modifying prefs if you aren't sure you understand their purpose. You should only do this if you know what you're doing.

Полезно?

Задаване на въпрос

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.