a year ago
Hi, i have a problem with deploy, i use prisma ORM, with NestJS, and he's show me this log error:
$ /app/node_modules/.bin/prisma migrate deploy
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "railway", schema "public" at "-----railway.internal:5432"
Error: P1001: Can't reach database server at ------.railway.internal
:5432
Please make sure your database server is running at -------.railway.internal
:5432
.
error Command failed with exit code 1.
0 Replies
a year ago
what's with the ------
a year ago
why is your service named ------
i'm only hidden the name, but he's: postgres-windelback.railway.internal
a year ago
it's not sensitive information fwiw
a year ago
is postgres in the same project of the service that's trying to connect to it
a year ago
please read this docs section
a year ago
yeah looks good
other topic.
i'm using template to uptime kuma, and i create a subdomain to this, but the ssl is not working very good
a year ago
who is your domain dns provider?
he's redirect me to certificate railway.app
a year ago
show me your dns settings for that domain please
a year ago
^
a year ago
<#727685388893945877> #5
a year ago
okay and show me the dns settings in your dns provider
a year ago
please remove the red, this is not sensitive information
a year ago
send that domain in a clickable format please
instead winsocket-develop, is https://monitor.windel.com.br
with this cname: kdcrvfsv.up.railway.app
a year ago
the screenshot shows a different domain than what you just sent
yeah, i not have a screenshot from this domain, because the sysadmin is not answering me, but the config is like this
a year ago
please be clear and concise here, what domain are you having issues with?
a year ago
how long ago did you set that up
a year ago
show me the dns settings for monitor.windel.com.br please
a year ago
show me the domain in railway
a year ago
remove it, and then re-add it without touching any dns settings
a year ago
only your custom
i will need for my coworker update it, and tomorrow i'll let you know if it worked or not
a year ago
as i just mentioned, without touching any dns settings