I can't log in to Ory Network: `api.console.ory.sh...
# ory-network
b
I can't log in to Ory Network:
api.console.ory.sh/workspaces:1 Failed to load resource: the server responded with a status of 403 ()
, completely blocking us. Is there an issue rn?
Copy code
Request URL:
<https://api.console.ory.sh/workspaces>
Request Method:
GET
Status Code:
403 Forbidden
Remote Address:
104.18.1.146:443
Referrer Policy:
strict-origin-when-cross-origin
👀 1
s
hm it works for me 🤔 but I see an increased 403 on the endpoint for some time in the last minutes
b
I'm not able to log in at all, in any project
I don't know if it's related, but we disabled CORS for our Dev application to troubleshoot a
403
error when updating identities. No idea why that would affect logging in, but they're possibly connected
Or the
403
issue we had in the API is also manifesting in being unable to log in
(It used to work)
s
ok I know where the error comes from, but I am not sure why you would suddenly get it 🤔
b
Is it something I need to resolve?
s
not sure yet, still looking into it
b
ty, we're we headed into QA for a deadline today and am blocked by this, had to make a change 😕
s
stupid idea, but did you already try with an incognito window? I am struggling to understand how you could run into this really you get an internal error, that you should not be able to run into
b
Yep, didn't work
Still 403 on workspaces
[Report Only] Refused to load the script 'https://console.ory.sh/__ENV.js' because it violates the following Content Security Policy directive: "script-src 'none'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
s
ok good, at least it is consistent 😅
I think we have a bunch of such errors, but it is report only
b
I see
s
btw, I think you should still be able to do stuff through he cli
b
Yeah I can, it's just difficult 😕
Also need to verify identity creation
s
please try again now
when did you use the console successfully the last time?
I'd guess at least 10h back, because then I can explain the issue
b
Yeah like 12 hours ago
11-12 hours ago for certain
s
does it work now?
b
SUCCESS
s
🙏
b
Thank you for whatever it is you all did
Cheers to beta testing workspaces
s
I am really sorry, this was related to the migration to workspaces where I did apparently a mistake (human error). Basically, the error was always there, just until ~10h ago the console happily ignored it. Now it does not anymore. I fixed the issue by inserting a missing row....
thanks for your patients
b
🍻
🍻 1
All good, ty for the quick fix