#Railway does not resolve custom domain
55 messages · Page 1 of 1 (latest)
Project ID: N/A
it may be a DNS cache on our end, the custom domin is already working here
depends on your machine
mac
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
it might still not work tho, the DNS resolver might be different if your ISP provides one
if it doesn't solve, wait 1-2 hours and it should work
just tested on mac
first time hitting that url
so its not cache
its like a wrong setup or smth
another mac*
oh that's probably another error
im getting a 502 from your application
make sure to follow this doc
https://docs.railway.com/reference/errors/application-failed-to-respond
does railway supply PORT env
import { Elysia } from "elysia"
const app = new Elysia().get("/", "test").listen(process.env.PORT ?? 4000)
export type App = typeof app
console.log(`Server is running at ${app.server?.hostname}:${app.server?.port}`)
is my server
perhaps it overwrites my port
yep railway provides the PORT variable but I don't know if it would provide a random port instead of the defined one
well try it and lmk
maybe try to set the env variable "PORT" to 4000? on railway
railway won't override the port variable if the user provides one manually
ok i see
it actually manually sets it to 8080
ok til
im so confused
thats with
301 is a redirect
but i dont have redirect set