prisma/prisma1

ERROR: GraphQL Error (Code: 400) The request could not be satisfied

roberta-pavel opened this issue · 1 comments

roberta-pavel commented

Bug description

We have a Kubernetes setup where our app is trying to connect to Prisma. Everything was working fine until a couple of weeks ago when at a new deployment of our app, we got the following error:

 { "error": "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>400 ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size=\"1px\">\nBad request.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n<PRE>\nGenerated by cloudfront (CloudFront)\nRequest ID: GJKdSbqH5krDadgmgd6omdKRqVANP_dFeM52ve03KZALfvNtUpcx4Q==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>",   "status": 400}

This comes from the command "prisma deploy" which is a prerequisite for our app.

How to reproduce

run "prisma deploy"

Expected behavior

The app can connect to Prisma

Environment & setup

  • Database: PostgreSQL
  • Node.js version: 8 (it is a prerequisite from the app)
  • Prisma version: 1.34.10
  • Kubernetes version: Major: 1, Minor: 18+
roberta-pavel commented

The issue was with an update of Kubernetes.

The service that exposed Prisma changed from NodePort to LoadBalancer and from 4466 to 80. So changing the url that our app is using to access Prisma fixed the issue