Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All Containers Lost after FF Crash - HELP #1968

Closed
akasaka99 opened this issue Feb 19, 2021 · 3 comments
Closed

All Containers Lost after FF Crash - HELP #1968

akasaka99 opened this issue Feb 19, 2021 · 3 comments

Comments

@akasaka99
Copy link

Hi-
I'm using FF 85.0.2 on MacOS 13.6.

  1. After a sudden FF crash which I do not know the reason, all my containers disappeared even though I had FF sync on.
  2. However, it looks like the add-on has started from fresh without taking into account the sync feature??
  3. I recall to usually be prompted to re-sync my Multi-Container add-on in such cases but for some reason this time I was not prompted to sign in the add-on for it to re-sync so I am not sure if it has re-sync or not as it appear totally fresh.

So I would like to know how I could recover my containers by either :

  1. "forcing" the add-on to re-sync which it does not seem to have done this time
  2. where are those containers data located on my Mac as I do a regular disk back-up so I could restore them from a previous backup but I do not know what/where they are.

Many thanks for your help.

@rpl
Copy link
Member

rpl commented Feb 19, 2021

2. where are those containers data located on my Mac as I do a regular disk back-up so I could restore them from a previous backup but I do not know what/where they are.

The list of containers (the one that Firefox itself stores, the extension itself may have some additional metadata on its own, but the containers definitions still need to be part of this file) is in a file named containers.json stored in the Firefox profile directory.

@akasaka99
Copy link
Author

Great found it. So I would just have to replace the current "blank" JSON file with the backed-up JSON file and hotepguly that's it? Thnks !

@dannycolin
Copy link
Collaborator

Duplicate of #1236

@dannycolin dannycolin marked this as a duplicate of #1236 Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants