HI, my users are getting an error saying contact technical support, is there a problem with the lock error again?
I can confirm that we have the same issue. In the console I can see 404 when loading https://cdn.eu.auth0.com//js/lock/11.24.5/en.js
This is the same error that occurred in August. I just tweeted at both auth0 and auth0status.
Yes! - hello again! - are you affected again? - it was a lock error.
Same here. Hope this gets noticed quickly.
Hello,
Same issue here, it happens for all website on which we implemented ācustomā login, for example when we want to add fields in the login.
@James.Morrison itās supposibly the same issue like this one: Issues with Lock Internationalization ā¢ Auth0 Status Page
You commented on this according community post the last time: Hosted login page only shows: Something went wrong. Please contact technical support - #30
@pododesk-operations can you share a link to your tweet(s) here, so affected people can maybe count in on that!
For us, this would be a neck breaker if not fixed until in about 10 hoursā¦
Around that time we go to hell if people still canāt log in.
Thanks for flagging this, we are currently investigating what is occurring and will be sure to share as we find out more on our status page as we well as in this thread:
happening to me too!!!
Thank you @James.Morrison!
But shouldnāt the status page show this as āunder investigationā then!?
Itās not up there at allā¦
Looks like we had an intermittent issue with CDN for a small subset of free customers in EU region using older Lock versions, and it has been resolved. Please give it a peek to see if the issue is still occurring
I am still experiencing this issue.
We are on US-1 - Free.
Thanks!
Same still experiencing
Thanks EU has been fixed, now working on applying same fix state side.
Same still experiencing this issue.
Waiting.
Tks
Fixed should have been applied now to the US instances. Can you please confirm?
Thanks in advance!
Weāve received positive feedback on the issue being resolved across the board. Marking the challenge solved but if you run into any further issues related to this please let us know!