Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Using Multi-User Containers together with Temporary Containers exceeds sync quota

  • 4 trả lời
  • 1 gặp vấn đề này
  • 8 lượt xem
  • Trả lời mới nhất được viết bởi cor-el

more options

Setting up a new computer, have enabled syncing in both Firefox and Multi-User Containers, everything syncs fine with Firefox, but my settings from MUC refuses to sync.

From the sync log:

1588437492041 Sync.Engine.Extension-Storage ERROR Syncing @testpilot-containers: request failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Collection maximum size exceeded (209440 > 204800 Bytes).)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: ServerResponse@kinto-http-client.js:2771:5 processResponse@kinto-http-client.js:2925:13

1588437492041 Sync.Engine.Extension-Storage WARN Syncing failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Collection maximum size exceeded (209440 > 204800 Bytes).)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: ServerResponse@kinto-http-client.js:2771:5 processResponse@kinto-http-client.js:2925:13

1588437492042 Sync.Status DEBUG Status for engine extension-storage: error.engine.reason.unknown_fail

1588437492042 Sync.Status DEBUG Status.service: success.status_ok => error.sync.failed_partial

1588437492042 Sync.ErrorHandler DEBUG extension-storage failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Collection maximum size exceeded (209440 > 204800 Bytes).)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: ServerResponse@kinto-http-client.js:2771:5 processResponse@kinto-http-client.js:2925:13

Since I am using Temporary Containers, I think MUC is syncing every new tmp* container, thus the need for how much to sync is growing each time I open a new tab, and now it has hit the limit.

  • Is there a setting so that MUC doesn't sync certain containers (such as tmp*, as these will never be used again)?
  • Can I manually purge tmp* from MUCs sync? By editing some database or file?
  • Is there some other solution?
Setting up a new computer, have enabled syncing in both Firefox and Multi-User Containers, everything syncs fine with Firefox, but my settings from MUC refuses to sync. From the sync log: 1588437492041 Sync.Engine.Extension-Storage ERROR Syncing @testpilot-containers: request failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Collection maximum size exceeded (209440 > 204800 Bytes).)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: ServerResponse@kinto-http-client.js:2771:5 processResponse@kinto-http-client.js:2925:13 1588437492041 Sync.Engine.Extension-Storage WARN Syncing failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Collection maximum size exceeded (209440 > 204800 Bytes).)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: ServerResponse@kinto-http-client.js:2771:5 processResponse@kinto-http-client.js:2925:13 1588437492042 Sync.Status DEBUG Status for engine extension-storage: error.engine.reason.unknown_fail 1588437492042 Sync.Status DEBUG Status.service: success.status_ok => error.sync.failed_partial 1588437492042 Sync.ErrorHandler DEBUG extension-storage failed: Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Collection maximum size exceeded (209440 > 204800 Bytes).)(resource://services-common/kinto-http-client.js:2771:5) JS Stack trace: ServerResponse@kinto-http-client.js:2771:5 processResponse@kinto-http-client.js:2925:13 Since I am using Temporary Containers, I think MUC is syncing every new tmp* container, thus the need for how much to sync is growing each time I open a new tab, and now it has hit the limit. * Is there a setting so that MUC doesn't sync certain containers (such as tmp*, as these will never be used again)? * Can I manually purge tmp* from MUCs sync? By editing some database or file? * Is there some other solution?

Được chỉnh sửa bởi jagenheim vào

Tất cả các câu trả lời (4)

more options

You can possibly check the containers.json file in the profile folder.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.

more options

No, I'm totally stumped on what is causing this problem.

I disabled all add-ons (except for MUC), I disabled syncing for tabs, history and login-information.

I removed container.json entirely (since it only contains default information anyway, no loss).

Then I restarted firefox.

Still can't sync MUC. Still the same EXACT number of bytes that is needed to sync which is not available.

Is it filled by my other computers and thus I need to clean the containers.json from there, hoping that will clean up my sync folder on firefox services?

Can I sync against something else? Like my own NAS, Google Drive or a USB stick or whatever? I kind of need MUC because it contains all the seperation I need for different work accounts / private life.

more options

Is this - https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/ - the add-on that you are referring to?

If so, this - https://github.com/mozilla/multi-account-containers/issues is listed as the "support site" for that specific add-on.
This "issue" - https://github.com/mozilla/multi-account-containers/issues/1708 - sounds similar to what you described.

And this - https://github.com/mozilla/multi-account-containers/#readme - is listed as the "homepage".

more options

You can install the About Sync extension in Firefox 72 and newer on desktop to check what data is stored on the Sync server via the about:sync page provided by this extension.

You may have to close and restart Firefox to access the about:sync page added by this extension (see the about:about page for available about pages).