Replies: 2 comments 6 replies
-
I think that could be an issue with your ingress configuration that is returning 504 gateway timeout, maybe you could check your ingress logs The CORS configuration can be checked inside the API logs when the application is starting like the following: |
Beta Was this translation helpful? Give feedback.
0 replies
-
These are the api logs, and the pod goes healthy after the init sequence.
|
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have set up Terrakube on a K8s Cluster on Azure. Currently, after accessing the UI and creating my first organization, I get an cors error displayed in the console. Does anyone know what could be the reason for cors to throw those errors? The login with sso for azure ad went without any problems.
Error 1:
Error 2:
requests.js:1
Beta Was this translation helpful? Give feedback.
All reactions