after logging in via `prisma login` and running `p...
# prisma-whats-new
t
after logging in via
prisma login
and running
prisma delete
prisma deploy
, It now has me deployed to
<https://us1.prisma.sh/htc-files/dev>
instead of a public one? I am still getting no response in the playground, and the Authorization token has been added:
Copy code
Error: Server response was missing for query 'null'.
    at u (<https://cdn.jsdelivr.net/npm/graphql-playground-react/build/static/js/middleware.js:1:1675422>)
    at <https://cdn.jsdelivr.net/npm/graphql-playground-react/build/static/js/middleware.js:1:1675832>
    at <anonymous>
l
us1.prisma.sh is the public cluster. It'll name space you. The endpoint should go:
<https://us1.prisma.sh/${yourname}/${yourservice}/${yourstage}>
It looks like you're missing the name space.
t
ok, interesting since when I run
prisma info
I get
<https://us1.prisma.sh/htc-files/dev>
now I can get the schema docs at least, but all queries are still returning
Error: Server response was missing for query 'null'.
this is at
<https://us1.prisma.sh/todd-humphrey/htc-files/dev>
l
Your last url appears to be working. What happens when you use an authenticated token?
I just ran it with a token and the schema came up fine
t
ok, I refreshed the page after adding the token, queries are working now
thanks
👍 1
n
hey @Todd Humphrey the missing workspace name seems to be an issue that was resolved in the latest beta. here's more information: https://github.com/graphcool/prisma/issues/1945