Netlify Identity login dialog misbehaving - https://identity-js.netlify.com/v1/netlify-identity-widget.js not found

[ajfhodgson]

We have been using Netlify Identity to protect the CMS editing part of our website for several years. We haven't changed anything recently.

Chrome console says https://identity-js.netlify.com/v1/netlify-identity-widget.js is 404 not found

Describe the bug Logging in to the private portion of our website (protected by Netlify Identity) no longer works

To Reproduce

1. Go to https://twogenerations.co.uk/admin/#/

2. You will see

Entering the credentials here does nothing - the page just hangs and Chrome's console says

Expected behavior

When it was working, you would see:

Then after clicking the button, you get

where you can enter your credentials successfully and pass to the protected pages.

Screenshots

See above

Applicable Versions:

• Decap CMS version: [e.g. 2.0.4]
• Git provider: [e.g. GitHub, BitBucket]
• OS: [e.g. Windows 7]
• Browser version [e.g. chrome 22, safari 11]
• Node.JS version:

CMS configuration

Chrome console says:

GET https://identity-js.netlify.com/v1/netlify-identity-widget.js net::ERR_ABORTED 404 (Not Found)
index.js:15 `window.CMS_MANUAL_INIT` flag set, skipping automatic initialization.
setupCMS.ts:53 Using login system: git-gateway
setupCMS.ts:54 Currently targetting branch: production
bootstrap.js:26 netlify-cms 2.4.2

Additional context

Something similar happened to us back in Apr 2021. At that time it spontaneously recovered after a few days and we closed the internal issue with Cannot Reproduce.

[ajfhodgson]

Recording the solution in case someone else has the same problem:

Our source has been loading https://identity-js.netlify.com/v1/netlify-identity-widget.js since at least 2019.

Looking closely at the docs to see if netlify-identity-widget.js is no longer usable,, I noticed that the examples all show loading https://identity.netlify.com/v1/netlify-identity-widget.js rather than https://identity-js.netlify.com/v1/netlify-identity-widget.js.

I removed the -js, and everything burst back into life.

So it looks like they silently retired an old host-name that had been there for years, without seeing if anyone was still loading from it!

But all is now well and my users are relieved!