Prisma1: Getting error "Could not connect to cluster prisma-us1 with host https://us1.prisma.sh ..."

Created on 31 Jul 2018  路  6Comments  路  Source: prisma/prisma1

Describe the bug

Getting the error:
"Could not connect to cluster prisma-us1 with host https://us1.prisma.sh. Did you provide the right port?"

This error shows on the console when I run yarn start.

My Prisma services work for months until Jul 29. It started showing the error on Jul 29. I tried starting the service again on Jul 30 and it's gone. But, it happens again today morning (Jul 31).

To Reproduce
Steps to reproduce the behavior:

  1. Run yarn start
  2. See error

Expected behavior
Prisma service must be started as usual.

Screenshots

prisma-error

Versions:

  • OS: Windows 10
  • prisma CLI: prisma/1.12.0
bu0-needs-info

Most helpful comment

@marktani That was my mistake. I have my nodejs project setup with the prisma (v1.5) installed locally somehow, and prisma (v.1.13.3) installed globally.

@IvanVolkov-12devs Double check if you have local prisma installed in your project. Remove it from package.json and run npm install. That will help set prisma to use the global one.

All 6 comments

The same problem!
Starts from yesterday (31 July)
I can manage for existing Data from - https://app.prisma.io/ but - "Yarn Start" return me this error...

@kvo1 , @IvanVolkov-12devs : Are you running it behind a proxy?

@divyenduz Nope, mine isn't behind any proxies. It's still an issue now.

@kvo1 I also don't use proxy.
I had to run it locally - https://www.prisma.io/docs/tutorials/setup-prisma/create-new-db/mysql-gui4peul2u/ in conjunction with https://github.com/somus/prisma-admin that i found

The demo server runs on 1.13.3, can you reproduce this with the same CLI version?

Also, please provide more information about your project setup - it is not clear what yarn start will do in your specific project 馃檪

@marktani That was my mistake. I have my nodejs project setup with the prisma (v1.5) installed locally somehow, and prisma (v.1.13.3) installed globally.

@IvanVolkov-12devs Double check if you have local prisma installed in your project. Remove it from package.json and run npm install. That will help set prisma to use the global one.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jannone picture jannone  路  3Comments

sedubois picture sedubois  路  3Comments

nikolasburk picture nikolasburk  路  3Comments

ragnorc picture ragnorc  路  3Comments

thomaswright picture thomaswright  路  3Comments