HELP! Logins lost from profiles
This all started when i wanted to use a user.js file for firefox.
I followed a youtube video to create a new profile to use the user script but I wanted to change the directory so I deleted it, made it anew and somehow the default profile file that i used was gone (I realised this only later). I think I had somehow overwritten it, but its weird because in my trashbin i did not find anything.
When asking me to login to sync I gave my password but it said it was wrong i realised I was using a vpn so i turned it off and then it worked, however then it asked me for a confirmation code from my email wich I also gave but it still refused saying it was wrong, which it wasn't!
After that I gave up and made a backup of my profiles and resetted my password still thinking I had my old profile file. My logins were gone and copying and pasting the login.json with the key4.db files from other profiles didnt give them back.
Luckily am still logged into my mobile app where i have my logins but there is now a warning sign to reconnect to resume syncronizing and Im afraid if i reconnect its going to delete my saved logins on the app instead of using them.
What do i do now? Is there a way to export all my data from the mobile app? Do I need to copy my logins one for one? Or can everything be resolved by reconnecting?
Zgjidhje e zgjedhur
Ok after manually saving a few important logins and reconnecting to synchronize it did NOT delete my logins on mobile but used them! fantastic! my problem has been resolved
Lexojeni këtë përgjigje brenda kontekstit 👍 0Krejt Përgjigjet (5)
You can try this in a new profile:
You can install the About Sync extension to check what data is stored on the Sync server via the about:sync page provided by this extension.
Close and restart Firefox to access the about:sync page added by this extension (see the about:about page for possible about pages).
Note that Firefox 111.0.1 is rather old (Firefox 116.0.1 has been released).
You can look a utility to browse System Restore points to see whether you can locate a logins.json and key4.db pair. You can open logins.json in a Firefox tab to see if it contains logins, the host/origin is in plain text, username and password are encrypted with the key stored in key4.db.
Hello thank you for responding
Sadly all the json files are basically empty with only my firefox account login info from when I logged in and synced. I could also see this with the sync extension.
So Is the reconnecting to resume synchronizing on mobile just going to delete my logins on the app or will it start syncing them to my pc? If its going to delete them is there an option for exporting all of my logins from mobile? Otherwise Ill just slowly reset all the passwords of sites with my emails (which I already copied the logins from the app)
I understand your frustration, and I'm here to help. It seems like your Firefox profile got mixed up while trying to use a user.js file, and you lost your logins. To address this, let's take a step-by-step approach. Firstly, regarding your mobile app, reconnecting shouldn't delete your logins, but to be cautious, you can export your logins from the mobile app if there's an option available. To recover your lost logins on your desktop, creating a new profile using the Profile Manager might help. Install the About Sync extension to understand what data is stored on the Sync server. You might also want to check if you have any System Restore points that could help you locate your logins.json and key4.db pair. Remember, your mobile logins can often be recovered with an email reset, and you can always contact Mozilla Support for more personalized assistance. Don't worry, we'll work through this together.
"your mobile logins can often be recovered with an email reset" what does this mean? I just need to be able to export them.. This reply feels like its ai generated ....
Zgjidhja e Zgjedhur
Ok after manually saving a few important logins and reconnecting to synchronize it did NOT delete my logins on mobile but used them! fantastic! my problem has been resolved