This message was deleted.
# general
m
This message was deleted.
f
VITE_ORY_SDK_URL should point to kratos docker container that is by default running at 4433 port
c
maybe that's the problem. The ui is running with a nx serve, the ory stack running in docker-compose. So the
kratos
container name is not visible to the host (the ui)
f
What I have is docker-compose running kratos. Reverse proxy to make it outside world where that VITE_ORY_SDK_URL points to.
c
yup. tried to use the oathkeeper reverse proxy - but then got hit by a cors error (ui is running on 4200-somehost, reverse proxy on 8081-somehost)
f
If you run everything locally just to test things, it's easy to get kratos, self-service-ui and your site using elements
c
ha! yay
f
UI and kratos has to be under same domain for cookies to work eg. kratos.some.domain and ui.some.domain
c
I mapped port 4433 in docker to the host
now have no errors, and the "dashboard" appears 😉
🙌 1
only thing is I didn't think I logged in 🤣
onwards and upwards. thanks for your help
f
Great that you got it working. Towards next debug!
c
urg no
maybe firewall
checking