I understand that you're encountering an "Internal Server Error: Get Spec job failed" error when adding a new connector in Airbyte. This issue can be caused by various factors. Here are some possible solutions based on the information extracts: 1. Make sure you have pulled the image to your machine before adding the custom connector. If you're using an EC2 instance, pull the image to the EC2 machine ([source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1666713517970759)). 2. Ensure that your Docker image is built correctly and that all the requirements are properly set in the

setup.py

file. Also, verify that your

Dockerfile

follows the same logic as other connectors ([source](https://discuss.airbyte.io/t/2248)). 3. If you're using Airbyte on Kubernetes, make sure the repository name is a valid Kubernetes name. Invalid names may work locally on Docker but cause errors on Kubernetes ([source](https://docs.airbyte.com/integrations/custom-connectors)). 4. Check if your Airbyte instance has access to the internet, as it might be unable to reach the image repository ([source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1670252832457049)). 5. If you're using a private repository, ensure that both your CI environment and your Airbyte instance are authenticated ([source](https://discuss.airbyte.io/t/3958)). If none of these solutions work, you may want to check the logs for more information on the error. You can use

docker logs container_name

to view the logs of the Airbyte server. If you still need assistance, please provide more information about your setup, such as the Airbyte version, deployment method, and any customizations you've made.