connection error: request error, status_code: 503

[Liupuzhuo]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.13

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Anyone has met this issue?
When I adding new api endpoint, there is a bug report:
connection error: request error, status_code: 503, content: <he

✔️ Expected Behavior

Add a api endpoint

❌ Actual Behavior

issue 503

[dosubot[bot]]

Encountering a 503 status code error when adding a new API endpoint in a self-hosted Dify instance (version 0.6.13, running on Docker) could be due to several reasons. Here are some steps to resolve it:

1. Check Container Status: Ensure all containers are running correctly.

   docker compose ps

2. Inspect Logs: Check the logs of the docker-api-1 and docker-nginx-1 containers for any errors.

   docker logs docker-api-1
   docker logs docker-nginx-1

3. Resource Allocation: Ensure your Docker VM has sufficient resources allocated (minimum 2 vCPUs and 8 GB of memory).

4. Environment Variables: Verify that the environment variables in your .env file are correctly configured.

5. Restart Services: Restart the services to apply any changes.

   docker compose down
   docker compose up -d

6. Network Configuration: If you are integrating local models deployed with Ollama, ensure that the Ollama service is accessible from the Docker container. Replace localhost with host.docker.internal in the service URL.

   http://host.docker.internal:11434

7. Nginx Configuration: A 503 error can also be caused by Nginx forwarding the service to the wrong location. First, make sure the container is running, then run the following command with root privileges:

   docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'

   Find these two lines in the output:

   /docker-web-1: 172.19.0.5
   /docker-api-1: 172.19.0.7
   

   Open the location where you stored the Dify source code, open dify/docker/nginx/conf.d, replace http://api:5001 with http://172.19.0.7:5001, and replace http://web:3000 with http://172.19.0.5:3000. Afterward, restart the Nginx container or reload the configuration.

If the issue persists, further investigation into the specific error messages in the logs will be necessary ^[1][2][3].

To continue talking to Dosu, mention @dosu.

[crazywoola]

The image is broken.

[Liupuzhuo]

[Hardenqiu]

I had the same problem. So , how to solve it? Please.

[yuncengshangdepingyuan]

me too

[yuncengshangdepingyuan]

my nginx is on the 0.0.0.0:80.it's ok?