10 months ago
Trying to deploy my mastra server (node/npm project) in my staging environment. It works fine locally at the default urls
│ Studio: http://localhost:4111
│ API: http://localhost:4111/api
But it does not work for me in my staging environment. proto-os-mastra-develop
I've set
host to 0.0.0.0
port to 8080
And made sure my mastra server uses that for the deployment
6 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Production Railway app returns This site can’t be reached while staging works fine with identical setup
- 🧵 SMTP Issue After Deployment
- 🧵 Cannot deploy my fast api python backend (times out)
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
The Studio url is whats not working in staging. the actual swagger-api / api seem to be working fine
10 months ago
Can you define "does not work"?
Have you made sure all variables in prod are also present in staging?
10 months ago
The local dev environment -- http://localhost:4111/ -- has a full ux experience. My staging environment -- https://proto-os-mastra-develop.up.railway.app/ -- is something completely different. See here for what its supposed to be / what it is locally -- https://mastra.ai/docs/getting-started/studio
I'm guessing its something with host/port configuration, but i dont know
10 months ago
Are you sure you're deploying the correct branch into staging?
It seems like two completely different codebases...
vihardesu
The local dev environment -- <http://localhost:4111/> **\-- has a full ux experience. My staging environment --** <https://proto-os-mastra-develop.up.railway.app/> **\-- is something completely different. See here for what its supposed to be / what it is locally --** <https://mastra.ai/docs/getting-started/studio> **I'm guessing its something with host/port configuration, but i dont know**
10 months ago
use api public url as an environment variable in studio.
if it works, reply me to diag the issue.