e48131f7-096a-4b0a-8733-ecc43f93da7b

why the need for caddy to begin with?

also, please dont obfuscate things like this [xxxxxxx.xxxxxxx.com](xxxxxxx.xxxxxxx.com) its not helpful

sorry, ya no worries --> https://assignments-dev.coderscampus.com/ws/021/bntqbx12/xhr_streaming?t=1721787651124
Request Method:
POST
Status Code:
405 Method Not Allowed
Remote Address:
34.86.119.124:443
Referrer Policy:
strict-origin-when-cross-origin

I believe we were using caddy to generate a public domain

Railway generates a public domain for you with SSL

and for websocket connections wouldnt you send a GET request to wss://[assignments-dev.coderscampus.com/ws/021/bntqbx12/xhr_streaming?t=1721787651124](assignments-dev.coderscampus.com/ws/021/bntqbx12/xhr_streaming?t=1721787651124)

hmmm, Im getting the error main.js:73 Uncaught SyntaxError: The URL's scheme must be either 'http:' or 'https:'. 'wss:' is not allowed.

why would wss not be allowed for a websocket endpoint

does the request need to be a post type? are you sending data in the body?

hmm maybe its the library Im using? Im not exaclty sure, using sock-js-client

nope, just trying to connect

either way, why caddy?

send the caddyfile so i can get an idea of what you are trying to do

ya for sure, ```{ # global options
admin off # theres no need for the admin api in railway's environment
persistconfig off # storage isn't persistent anyway autohttps off # railway handles https for us, this would cause issues if left enabled
log { # runtime logs
format console # set runtime log format to console mode
}
servers { # server options
trustedproxies static privateranges # trust railway's proxy
}
}

:{$PORT} { # site block, listens on the $PORT environment variable, automatically assigned by railway
log { # access logs
format console # set access log format to console mode
}

# health check for railway
respond /health 200

# serve from the 'build' folder
root * build

# enable gzipping responses
encode gzip

# serve files from 'build'
file_server

# if path doesn't exist, redirect it to 'index.html' for client side routing
try_files {path} /index.html

}```

this just serves a frontend website

i know that, because i wrote that

ooo nice! Thanks for writing it! We were just experimenting, my co worker and I and we came on some examples, so far its working as it should, but you think its overkill? Maybe messing with the domain?

no one has ever had issues with that caddyfile that i know of, using caddy to serve a frontend website is going to be by far the best way to do it on railway in my experience

so the issue is elsewhere

can you send a screenshot of your project canvas please

yup for sure, is this it here?

okay and what is the caddy proxy for?

i wrote that too, but i see a lot of people using it when they actually dont need to be

well, it looks like all we're doing here is connecting our front and back end under one domain

is that strictly needed?

honestly cant say for sure, Id have to ask my co worker but is there an alternative you think instead? By removing the caddy proxy, you think it should clear the air?

oop, holdup, I may have sent you the wrong caddy file --> ```# global options
{
admin off # theres no need for the admin api in railway's environment
persistconfig off # storage isn't persistent anyway autohttps off # railway handles https for us, this would cause issues if left enabled
# runtime logs
log {
format json # set runtime log format to json mode
}
# server options
servers {
trustedproxies static privateranges # trust railway's proxy
}
}

site block, listens on the $PORT environment variable, automatically assigned by railway

:{$PORT} {
# access logs
log {
format json # set access log format to json mode
}

reverse_proxy {$FRONTEND_HOST} # proxy all requests for /* to the frontend, configure this variable in the service settings

# the handle_path directive will strip /api/ from the path before proxying
# this is needed if your backend's api routes don't start with /api/
# change paths as needed
#handle_path /api/* {
    # this strips the /api/ prefix from the uri sent to the proxy address
#    reverse_proxy {$BACKEND_HOST} # proxy all requests for /api/* to the backend, configure this variable in the service settings
#}

# if your backend's api routes do start with /api/ then you wouldn't want to strip the path prefix
# if so, comment out the above handle_path block, and uncomment this reverse_proxy directive
# change paths as needed
reverse_proxy /api/* {$BACKEND_HOST} # configure this variable in the service settings

}```

i think there are some misunderstandings on your side as to why you need the proxy, i would eliminate it and go from there

have your frontend call the backend's domain directly, you of course will need to setup cors on your backend but thats a 5 minute tutorial and done

okay ya for sure! I'll try this and get back to you. Thanks for your help!

no problem

oh and the reason you where getting 405 Method Not Allowed is because the path /ws/021/bntqbx12/xhr_streaming is a path in the frontend.
my proposed solution still stands though