Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Saved passwords are missing and logins.json file has .corrupt at the end of it

  • 13 wótegrona
  • 0 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót cor-el

more options

Hi ,


after update i have a big problem that might be related or might not. First of all, all the saved email logins are still there and still autofill in, but the passwords don't show up in the autofill anymore.

in my profile folder i have  3 files called logins.json-1.corrupt , logins.json-2.corrupt, logins.json-3.corrupt (380 ko )

i have doing this  : 1.Open the Firefox web browser. 2.Type about:support on address bar and Enter. 3.Click on the "open folder" (this opens the profile folder) Windows > Open Folder Linux > Open Directory 4.Close Firefox. 5. In profile folder, Check if you see a file called logins.json.corrupt. 6.If you do, rename the file to logins.json to fix it. 7.Start Firefox. The passwords should be available again.

the file logins.json become again logins.json-1.corrupt

i tried with diffèrent version of firefox jasonvieuw no solution file is corrupt plz any solution ? many thx

Hi , after update i have a big problem that might be related or might not. First of all, all the saved email logins are still there and still autofill in, but the passwords don't show up in the autofill anymore. in my profile folder i have 3 files called logins.json-1.corrupt , logins.json-2.corrupt, logins.json-3.corrupt (380 ko ) i have doing this : 1.Open the Firefox web browser. 2.Type about:support on address bar and Enter. 3.Click on the "open folder" (this opens the profile folder) Windows > Open Folder Linux > Open Directory 4.Close Firefox. 5. In profile folder, Check if you see a file called logins.json.corrupt. 6.If you do, rename the file to logins.json to fix it. 7.Start Firefox. The passwords should be available again. the file logins.json become again logins.json-1.corrupt i tried with diffèrent version of firefox jasonvieuw no solution file is corrupt plz any solution ? many thx

Wšykne wótegrona (13)

more options

It sounds like there is an actual problem with the file. Could you try this:

Starting in your profile folder, with Firefox closed:

  • right-click logins-backup.json > Copy
  • right-click a blank area of the folder > Paste
  • right-click logins-backup - Copy.json > Rename to logins.json

Can Firefox read that one at the next startup? Note that it probably will be missing the last update to the file.

more options

I tried, the problem persists, 6 years of work disappeared during a blink of an eye. because of a cursed update I am really very sad I am blocked since 1 one week to seek a solution vainly! one thing is abnormal the logins.json-3.corrupt with (380 ko/kb ) and the logins-backup.json file is only 3 kb/ko ! is there any other solution thank you very much

more options

It sounds like the backup was from a fresh setup and doesn't have the old data.

If you edit the name of the one of the .corrupt files to end with .json and view it in a tab in Firefox, how readable is the data? If Firefox thinks it is valid JSON, it will use a structured view, but if not, it may look a bit like a text scramble. As a small example (structured view on the left, Raw view on the right):

There are JSON editors that might be able to repair the structure of the file if it's just missing a } or ] somewhere, but if the file contents don't look like the example (only the user name and password fields have gibberish text), then it might not be usable.

more options

You can try to open such a corrupt file in a Firefox tab to check whether the file content is valid JSON. To make Firefox use the built-in JSON viewer, the file extension need to be .json.

You can try this with the most recent logins-#.json.corrupt file.

Wót cor-el změnjony

more options

You can possibly set signon.debug = true on the about:config page. You restart Firefox and place logins.json and check the Browser Console for login related messages. Do not forget to reset signon.debug to false after you are done testing.

more options

hi jscher2000 - cor-el

thank you for your help, I tried it and it gives me the following:


with 2 online editor :

https://jsoneditoronline.org/

JSON value expected but got ' 'at line 1 column 1

https://jsonformatter.org/json-editor Parse error on line 1:

Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined'


usine Browser Console signon.debug = true on the about:config page.

1666515036242 addons.xpi WARN Checking C:\Program Files\Mozilla Firefox\distribution\extensions for addons Login storage: Opening database at C:\Users\HP\AppData\Roaming\Mozilla\Firefox\Profiles\gron0mpq.default-release-1665413386372\logins.json. storage-json.js:85:14 JSON.parse: unexpected character at line 1 column 1 of the JSON data JSONFile.jsm:240:12 LoginManager: initializationPromise is resolved, updating isPrimaryPasswordSet in sharedData LoginManager.jsm:90:16 LoginManager: Searching for logins matching origin: chrome://FirefoxAccounts formActionOrigin: null httpRealm: Firefox Accounts credentials LoginManager.jsm:494:14 Login storage: Returning 1 logins for specified origin with options [object Object] storage-json.js:622:10 Login storage: Returning 1 logins. storage-json.js:695:10 ExtensionError: No such native application mozillavpn ExtensionUtils.jsm:57:5 L’évènement « key » n’est pas disponible pour certaines dispositions de clavier : key="x" modifiers="accel,alt" id="" browser.xhtml L’évènement « key » n’est pas disponible pour certaines dispositions de clavier : key="q" modifiers="accel,alt" id="" browser.xhtml L’évènement « key » n’est pas disponible pour certaines dispositions de clavier : key="s" modifiers="accel,alt" id="" browser.xhtml L’évènement « key » n’est pas disponible pour certaines dispositions de clavier : key="t" modifiers="accel,alt" id="" browser.xhtml L’évènement « key » n’est pas disponible pour certaines dispositions de clavier : key="i" modifiers="accel,alt,shift" id="key_browserToolbox" browser.xhtml Content Security Policy: « 'report-sample' » ignoré à l’intérieur de script-src : l’attribut « strict-dynamic » est spécifié Content Security Policy: « 'unsafe-inline' » ignoré à l’intérieur de script-src : l’attribut « strict-dynamic » est spécifié Content Security Policy: « https: » ignoré à l’intérieur de script-src : l’attribut « strict-dynamic » est spécifié Content Security Policy: « http: » ignoré à l’intérieur de script-src : l’attribut « strict-dynamic » est spécifié Content Security Policy: « 'report-sample' » ignoré à l’intérieur de script-src : l’attribut « strict-dynamic » est spécifié Content Security Policy: « 'unsafe-inline' » ignoré à l’intérieur de script-src : l’attribut « strict-dynamic » est spécifié Content Security Policy: « https: » ignoré à l’intérieur de script-src : l’attribut « strict-dynamic » est spécifié Content Security Policy: « http: » ignoré à l’intérieur de script-src : l’attribut « strict-dynamic » est spécifié WebExtension context not found! 2 ExtensionParent.jsm:1285 this.window.gBrowserInit is undefined

my computer knowledge is limited, I just downloaded the damaged file on mediafire, logins.json.corrupt if some one can help me by reparing the domaged file thx

https://www.mediafire.com/file/53bgmi18d4filpv/new_-_Copie.rar/file

more options

Did you try to open the file in a Firefox tab as it is likely that the file is corrupted and not valid JSON ?

more options

yes i did , the problem persists I am disappointed, friends is there a service to which I can send the sensitive files for repair? I've been suffering in silence for more than a month

more options

The two files in the RAR archive are basically empty (NUL characters). (Or maybe I didn't decompress the file correctly?) If you open any of your logins files in a plain text editor, do they contain readable text?

I don't know whether you have considered the possibility of a backup file. During updates, Windows may capture a copy of your Firefox data into a restore point. To avoid mangling other data, do NOT use system restore. Instead, try a program that lets you selectively export data out of restore points. Here are two options for that:

Before using them, set Windows to show hidden files and folders before diving in: https://support.microsoft.com/en-us/windows/view-hidden-files-and-folders-in-windows-97fbc472-c603-9d90-91d0-1166d1d9f4b5

Then within the most recent restore point shown in the program, you can explore along this path to see whether you can find a shadow copy of your profile:

\Users\your-user-name\AppData\Roaming\Mozilla\Firefox\Profiles\your.profile

If you find a logins.json file that appears to have real data, export out both logins.json and key4.db to your live desktop for further analysis.

Let us know what you find.

more options

hi jscher ,

thx for your help

right The two files in the RAR archive are basically empty (NUL characters) because of the update my firefox could not repair the file

about :

    ShadowExplorer: http://www.shadowexplorer.com/
   Shadow Copy View: https://www.nirsoft.net/utils/shadow_copy_view.html 

nothing is displayed the page is blank, restore point is disabled


are there any office where can i send logins.json and key4.db for reparation ? thx

Wót i.ghoufrane změnjony

more options

hey guys , any solution plz i have lost +100 password

more options

key4.db is a binary file and it's normal that it's not easily readable. logins.json is text so if it's not readable, it's not usable. As far as I know, there's no way to convert null characters back to the original characters.

more options

Key4.db is actually a SQLite database file. Note that you should reset signon.debug to its default value false if you haven't done this yet. The only purpose with setting it to true is to display more detail in the console about what is going on with reading logins.json.