Skip to content

Storage calculated based on 'pooled' instead of domain limit? #456

@dexbleeker

Description

@dexbleeker

This might be me misunderstanding, but I think I have found a bug in the SaaS-version. I should preface by saying that I'm a relatively new but happy customer otherwise, but have not yet been able to utilize your services fully, because of this:

Am I understanding correctly that if:

  • My global storage limit is 20GB (10 default + extra 10)
  • A domain has a global limit of 10GB (the setting on the domain page's 'advanced settings' is called Storage Max Quota Per Alias)
  • Currently 7.35GB is used in total (across all my domains, the app refers to this as pooled if I'm not mistaken), so not even close to the total available 20GB
  • The domain in question uses 5.93GB

I should have available to the domain: 10GB (domain limit) - 5.93 (in use) = 4.07GB? Instead, I have 2.65 available, which suggests it is calculated like 10GB (domain limit) - 7.35 (pooled) = 2.65GB?

Is this a bug? Or is it not possible to have a domain-wide limit for each domain?

Screenshot:
Image

Thanks in advance!

Checklist

  • I have searched through GitHub issues for similar issues.
  • I have completely read through the README and documentation.
  • I have tested my code with the latest version of Node.js and this package and confirmed it is still not working.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions