a month ago
Hi, im trying to connect chatgpt actions with a server hosted in railway named "miraculous-trust", but i don´t can make it talk each other. Im pretty shure my server and worker are working, cause i can make them run from my terminal, but my GPT with Actions still get the message "ClientResponseError" when we try to contact from GPT. I wanna ask if there´s some restriction or is just a coding error. Im trying to read about it but i cannot find a lot of info.
4 Replies
a month 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!
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • about 1 month ago
a month ago
hey, its likely that the servers urls aren't reaching (ie the endpoints arent reachable) from what i can tell. can you share the exact ClientResponseError errors? (ie are you getting 3xx/4xx errors or anything else) that can be impacting it?
a month ago
A few things to check for ChatGPT Actions with Railway:
Make sure your Railway service has a public domain configured - ChatGPT can't reach private networks. Check that you have a railway.app domain or custom domain set up.
ChatGPT Actions require HTTPS with a valid SSL cert. Railway provides this automatically on their domains, but verify your endpoint URL starts with https://.
Your API needs to return proper CORS headers. ChatGPT makes requests from OpenAI's servers, so you need to allow their origin. Add these headers to your responses:
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, OPTIONS
Test your endpoint directly with curl from outside Railway to see if it's actually reachable:
If it works from curl but not ChatGPT, the issue is likely CORS or response format.
caullenomdahl
A few things to check for ChatGPT Actions with Railway:Make sure your Railway service has a public domain configured - ChatGPT can't reach private networks. Check that you have a railway.app domain or custom domain set up.ChatGPT Actions require HTTPS with a valid SSL cert. Railway provides this automatically on their domains, but verify your endpoint URL starts with https://.Your API needs to return proper CORS headers. ChatGPT makes requests from OpenAI's servers, so you need to allow their origin. Add these headers to your responses:Access-Control-Allow-Origin: *Access-Control-Allow-Methods: GET, POST, OPTIONSTest your endpoint directly with curl from outside Railway to see if it's actually reachable:curl -v https://your-service.railway.app/your-endpointIf it works from curl but not ChatGPT, the issue is likely CORS or response format.
a month ago
im gonna check those points, thanks