4 months ago
I have separate web part and server part running, I am trying to keep server part with internal name, e.g no public name.
Trying to call rest from the web and got: net::ERR_NAME_NOT_RESOLVED
Redeployed both just in case.
server: shadowkissed.railway.internal
Pinned Solution
4 months ago
The frontend sits on the client machine, so yes, the client is the one trying to reach the backend. SSR only means the webpages are rendered server-side, but after that, the rendered pages are sent to the client.
4 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
4 months ago
Your frontend needs to call the backend through a public URL. Client machines (machines which access your frontend) cannot access Railway private networking.
4 months ago
Clients machines do not care about backend, this is standard design - you access only the frontend part everything else can be in private network.
Client machines do not made requests to the backend, but only to front end.
The only client is browser ->http->frontend->http(rest)->backend.
Oh wait ..... this JS is running in the browser, thus client IS trying to reach backend ...... ? I would assume server side rendering, but.....
4 months ago
The frontend sits on the client machine, so yes, the client is the one trying to reach the backend. SSR only means the webpages are rendered server-side, but after that, the rendered pages are sent to the client.
Status changed to Solved brody • 4 months ago