Hosting Plunk in railway and custom domain redirect to railway domain causing CORS error.
joncoronel
TRIALOP

a year ago

I deployed a plunk instance through the preset service found in the railway dashboard. Have it all setup with AWS and working fine.

I then set a custom domain for the plunk dashboard which works fine initially and get send to a login page. But when I try to login, the request is sent to a railway domain instead of the custom domain I am signing in through so I then get a CORS error and I am unable to login/signup.

1 Replies

joncoronel
TRIALOP

a year ago

99c05a53-0d78-42be-a999-facbe73c27f4


Loading...