I would try it in incognito first, to validate that this is not a cookie or cache issue.
It could also be your router/modem that is blocking some contents or a ACL/Firewall rule.
Are you using a VPN?
I tried incognito, clearing all cookies & also attempted to use IE / Firebox; still, get the same issue.
I am not using a VPN, I guess it could be my router/modem ACL/firewall rules, but it was working a few days ago and I have not touched route/modem configs.
Try to fetch the lock.min.js with cURL in enhance verbose mode to ensure that it’s not something really strange between your browse and the target. If cURL successfully gather the context from this content distribution network but your browser denies it, the witch-hunt begins.
@James.Morrison - Would you mind taking a look at this? I think there is a problem with the load balancer auth0 is using and its causing login issues for me.
@James.Morrison - Looks like the load balancer is sending me to 99.84.101.153 now, so I’m not experiencing any more issues.
Do you know if this was in-fact an issue with the load balancer not being updated?
If so, are there any steps I can take if I experience this issue again?
Is there anything non-technical users of my app can do if they experience login problems related to this?
If it was not a load-balancer issue, do you have any theories of what it might have been? This essentially locked me out for 48 hours so i’d like to get ahead of it happening again.
I hadn’t heard if this was actually the factor or not.
Relay it to you and please notify us again.
I don’t have any details on this front, I sent off the request to our team to investigate but no word as of yet.
I will continue to keep this topic open for another two weeks just in case you experience another issue with this. I will also update the thread if I hear anything back. Thanks!