Localhost cors problems

Original message was deleted

TheRabber•7/16/25, 1:31 PM

here wo go with the docker-compose

docker-compose.yml3.58KB

TheRabber•7/16/25, 1:49 PM

nginx for laravel:
server {
listen 80;
server_name laravel.local;

location / {
proxy_pass http://laravel.test:80;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}

and for zitadel:
server {
listen 80;
server_name zitadel.local;

# CORS headers
add_header 'Access-Control-Allow-Origin' '*' always;
add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS' always;
add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range,Authorization' always;
add_header 'Access-Control-Allow-Credentials' 'true' always;
add_header 'Access-Control-Max-Age' '1728000' always;

location {
proxy_pass http://zitadel:8080;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;

# WebSocket support
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}

SaarPhil•7/16/25, 3:56 PM

proxy_pass http://laravel.test/;proxy_pass http://laravel.test/; doesn't look right to me
Also redirecting shouldn't cause CORS errors..

TheRabber•7/16/25, 6:02 PM

Happend without the nginx as well, so this is probably not the root cause.
The pass should just push the traffic towards the internal docker containers if I'm not mistaken...

So I have a route /login in the controller I do
return Socialite::driver('zitadel')->redirect();
which is according to socialite

TheRabber•7/17/25, 3:05 PM

Ok, I'm really giving up.
I did create a clean application, this time used traefik for the laravel.localhost and zitadel.localhost domains.
under the application in zitadel I added the http://laravel.localhost/auth/callback... and also as an additional domain, but still getting the cors error, has anyone tried the docker-compose setup? I really have no clue why I'm getting this.

The user is clicking on Login, calling the /login route, this one does the redirect to zitadel and throws the cors in the end

TheRabber•7/17/25, 9:35 PM

Problem found... it's not configuration related but the way inertia is linking...
it does it via <link> and not via <a> changes this fixes the problem

TTheRabber Problem found... it's not configuration related but the way inertia is linking.....

SaarPhil•7/19/25, 8:01 AM

Well

<link>

<link>

is not what it appears to be at first glance.
Maybe the element's name is a bit unlucky. <a>....</a><a>....</a> is for links like this: https://zitadel.com

<link>

<link>

is used to define relationships between documents. Most likely you'd use it to include stylesheets etc.

TheRabber•7/19/25, 6:46 PM

yeah the <link> thingy was set by default from inertia to redirect to the internal login.
That's probably why it caused a problem when I tried to redirect from the original controller to Zitadel.

Everything works fine now and as expected, just normal logic stuff that needs to be implemented around it