I have same issues difficuly when style inside iframe element

Hello,

I am using mongo-express image in a docker-compose.yml file. I set the following parameters:

      ME_CONFIG_BASICAUTH_USERNAME: "${ME_CONFIG_BASICAUTH_USERNAME}"
      ME_CONFIG_BASICAUTH_PASSWORD: "${ME_CONFIG_BASICAUTH_PASSWORD}"
      ME_CONFIG_MONGODB_SERVER: "${ME_CONFIG_MONGODB_SERVER}"
      ME_CONFIG_MONGODB_ADMINUSERNAME: "${ME_CONFIG_MONGODB_ADMINUSERNAME}"
      ME_CONFIG_MONGODB_ADMINPASSWORD: "${ME_CONFIG_MONGODB_ADMINPASSWORD}"

Every worked just fine, but I am today facing an issue. When landing on the mongo-express page, the sign-in pop up appears as expected. When entering the ME_CONFIG_BASICAUTH_USERNAME and ME_CONFIG_BASICAUTH_PASSWORD, the sign-in pop up appears again.

• When I click on "Cancel", I can see everything from the mongo-express page but without style.
• When I click on "Sign in", the sign-in pop up appears again.

I would really appreciate if you could tell me whether there is something that I am missing and that I should do?

Let me know if you would like more details.

Thank you

I refreshed the page and it works again ... Not sure why. Thank you and great image!

Hello,

I am using mongo-express image in a docker-compose.yml file. I set the following parameters:

      ME_CONFIG_BASICAUTH_USERNAME: "${ME_CONFIG_BASICAUTH_USERNAME}"
      ME_CONFIG_BASICAUTH_PASSWORD: "${ME_CONFIG_BASICAUTH_PASSWORD}"
      ME_CONFIG_MONGODB_SERVER: "${ME_CONFIG_MONGODB_SERVER}"
      ME_CONFIG_MONGODB_ADMINUSERNAME: "${ME_CONFIG_MONGODB_ADMINUSERNAME}"
      ME_CONFIG_MONGODB_ADMINPASSWORD: "${ME_CONFIG_MONGODB_ADMINPASSWORD}"

Every worked just fine, but I am today facing an issue. When landing on the mongo-express page, the sign-in pop up appears as expected. When entering the ME_CONFIG_BASICAUTH_USERNAME and ME_CONFIG_BASICAUTH_PASSWORD, the sign-in pop up appears again.

• When I click on "Cancel", I can see everything from the mongo-express page but without style.
• When I click on "Sign in", the sign-in pop up appears again.

I would really appreciate if you could tell me whether there is something that I am missing and that I should do?

Let me know if you would like more details.

Thank you

Bumps normalize-url from 4.5.0 to 4.5.1. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/sindresorhus/normalize-url/commits">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

The only thing that worked for me is setting a timeout before resetting the recaptcha

setTimeout(() => recaptchaRef.current.reset(), 500);

Not the best approach, and not 100% crash-free but it doesn't crash every time.

got similar trouble, Import will works correct if edit export file like {"_id":{"$oid":"5fda28190d4b6097afba6340"},"sent_date":"2020-12-12T02:01:00.000Z"}

⚠️Caution⚠️ bad solution. By this way it seems, this dates become a strings and it is not a okay. After all, i was try to export(by first yellow btn) from mongo-express and import into mongo thru the shell and now it seems correctly.