Tino
Tino10mo ago

Deployment fails with "An internal server error occured" - no further details

Morning, I receive the mentioned message without any pointers of what the issue could be. The issue happened after I made a bunch of code additions, meaning the deployment worked just fine before. An actual error message would be really helpful to figure what code/package is failing. To be clear, on my local machine everything just works fine. Among others I am using the aws-sdk package and I've read that this could cause issues. The suggested solution is to add an env variable HOME=/src However, that didn't make any change. So I removed that script for to see what would happen. Still internal error. I can of cause keep going and ripping out script/code after code to see what causes the internal at the deployment stage but a more detailed error message would help here as well sending me in the right direction. Any pointers? Thanks Tino
2 Replies
Deno AI Helper
Deno AI Helper10mo ago
Hi Tino, I'm sorry to hear that you're experiencing issues with your deployment. Unfortunately, without more specific error messages, it's difficult to pinpoint the exact cause of the issue. However, I can provide some general advice on how to debug this issue. Please note that this advice isn't explicitly mentioned in the Deno documentation, but it's a common approach to debugging issues like this. 1. Check your code changes: Since you mentioned that the deployment worked fine before you made a bunch of code additions, it's possible that something in your new code is causing the issue. Try to isolate the changes you made and test them individually to see if you can identify the problematic code. 2. Check your dependencies: If you're using third-party packages like the aws-sdk, make sure they're compatible with Deno and that you're using them correctly. Also, ensure that you're importing them correctly in your code. 3. Check your environment variables: If you're using environment variables in your code, make sure they're set correctly in your deployment environment. 4. Check the Deno Deploy logs: If you have access to the logs of your Deno Deploy, they might contain more detailed error messages that can help you identify the issue. 5. Reach out to the community: If you're still unable to resolve the issue, consider reaching out to the Deno community. You can ask for help on the Deno Deploy feedback GitHub page. I hope this helps! Let me know if you have any other questions. 🦕
Tino
Tino10mo ago
the issue is, that the Deno logs don't show any further information. That is the reason for my request. I solved it in the last hours running through the code to see what might break deployment: it was the npm:aws-sdk package. I replaced it with https://deno.land/x/aws_sdk@v3.10.0.0?source