Deployment to AWS - Internal Server Error
See original GitHub issueDescribe the bug
I think the deployment was successful. Although I did have to run qhub deploy -c qhub-config.yaml --dns-provider cloudflare --dns-auto-provision
twice because the first time, mid-way through, it times out.
After the second time of running qhub deploy ...
it returns the following:
[terraform]: Outputs:
[terraform]:
[terraform]: ingress_jupyter = {
[terraform]: "hostname" = "ad62fe3e09d7342c8ac1944e1aca19bf-1738926673.us-west-2.elb.amazonaws.com"
[terraform]: "ip" = ""
[terraform]: }
Unfortunately, when I access the url, and start a server, I get a server error:

The pods don’t look so healthy
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Troubleshoot "internal server" error status code 500 for API ...
I sent an HTTP request to my Amazon API Gateway API endpoint that integrates with AWS Lambda (for example, /lambda-resource GET).
Read more >Deployment on AWS Lambda gives Code 500 Internal Server ...
The logs are saying "Could not establish a connection to the http server".
Read more >Server Error 500 deploy AWS RDS
The 500 internal server error can be caused by several things which at times might be triggered by invalid API call causing the...
Read more >AWS - Serverless - "message": "Internal server error" when ...
I have a problem when deploying a project using Serverless framework and Amazon Web Services (more specifically API Gateway service).
Read more >I get an internal server error when I call a Lambda function via ...
For more details see the Knowledge Center article with this video: https:// aws. amazon.com/premiumsupport... Shruti shows you why you get an ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Okay, after I updated the security user group in the config file, it worked. Yay.
Hi @rileyhun, glad to hear it working and thanks for following up!
Closing issue.