OpenAI is not accessible with getaddrinfo
#3828
-
📦 EnvironmentDocker 📌 Versionv1.15.19 💻 Operating SystemUbuntu 🌐 BrowserFirefox 🐛 Bug DescriptionThe LobeChat is unable to access the OpenAI API, despite the server having successful access. This issue appears to be isolated to the LobeChat application, as other AI models (e.g., Claude, Perplexity) are functioning correctly. The server can successfully access the OpenAI API. The nextjs Docker container itself can access the OpenAI API. LobeChat frontend displays an error as shown. I am using a production docker-compose installation
{
"error": {
"cause": {
"errno": -3008,
"code": "ENOTFOUND",
"syscall": "getaddrinfo",
"hostname": "api.openai.com"
}
},
"endpoint": "https://api.openai.com/v1",
"provider": "openai"
}I am able to access OpenAI from both VM and nextjs container: 📷 Recurrence Steps
🚦 Expected BehaviorLobeChat should be able to communicate with the OpenAI API successfully, as the server and Docker container can. 📝 Additional InformationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 20 comments 2 replies
-
|
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
|
Hey there, @unitythemaker! I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this issue together! I found some similar issues that might be relevant to your problem:
Regarding your specific issue, the
By following these steps, you should be able to identify and resolve the DNS resolution issue affecting your LobeChat's connectivity to the OpenAI API. |
Beta Was this translation helpful? Give feedback.
-
|
I tried to manually add # Start a sh shell in container as root user
docker exec -u 0 -it lobe-database sh
# Open hosts file
vi /etc/hosts
# I added this line:
# 104.18.6.192 api.openai.comTried to check the connection again, it worked: |
Beta Was this translation helpful? Give feedback.
-
|
@hezhijie0327 is this same as before? |
Beta Was this translation helpful? Give feedback.
-
|
I got the same error for |
Beta Was this translation helpful? Give feedback.
-
|
@unitythemaker have a try to mapping host's |
Beta Was this translation helpful? Give feedback.
-
|
Umm, server uses systemd-resolved (Ubuntu 24), so that wouldn't work because host's resolv.conf looks like this, the nameserver is localhost: When I try nslookup with However, I believe the issue is not about DNS configuration but also I am confused. Because, host can resolve it, container can resolve it, even the node can resolve it but for both deepseek and openai lobe app can't. This is an image from container where I tried to fetch OpenAI API: I am not sure if that could be a problem but I've changed the docker-compose a little:services:
postgresql:
image: pgvector/pgvector:pg16
container_name: lobe-postgres
ports:
- '5432:5432'
volumes:
- './data:/var/lib/postgresql/data'
environment:
- 'POSTGRES_DB=${LOBE_DB_NAME}'
- 'POSTGRES_PASSWORD=${POSTGRES_PASSWORD}'
healthcheck:
test: ['CMD-SHELL', 'pg_isready -U postgres']
interval: 5s
timeout: 5s
retries: 5
restart: always
networks:
- lobe-network
minio:
image: minio/minio
container_name: lobe-minio
ports:
- '${MINIO_PORT}:${MINIO_PORT}' # MinIO API
- '9001:9001' # MinIO Console
volumes:
- './s3_data:/etc/minio/data'
environment:
- 'MINIO_ROOT_USER=${MINIO_ROOT_USER}'
- 'MINIO_ROOT_PASSWORD=${MINIO_ROOT_PASSWORD}'
- 'MINIO_DOMAIN=${MINIO_DOMAIN}'
- 'MINIO_API_CORS_ALLOW_ORIGIN=${MINIO_API_CORS_ALLOW_ORIGIN}'
restart: always
command: >
server /etc/minio/data --address ":${MINIO_PORT}" --console-address ":9001"
networks:
- lobe-network
logto:
image: svhd/logto
container_name: lobe-logto
ports:
- '${LOGTO_PORT}:${LOGTO_PORT}' # Logto
- '3002:3002' # Logto Admin
depends_on:
postgresql:
condition: service_healthy
environment:
- 'TRUST_PROXY_HEADER=1'
- 'PORT=${LOGTO_PORT}'
- 'DB_URL=postgresql://postgres:${POSTGRES_PASSWORD}@postgresql:5432/logto'
- 'ENDPOINT=${LOGTO_ENDPOINT}'
- 'ADMIN_ENDPOINT=${LOGTO_ADMIN_ENDPOINT}'
entrypoint: ['sh', '-c', 'npm run cli db seed -- --swe && npm start']
networks:
- lobe-network
lobe:
image: lobehub/lobe-chat-database
container_name: lobe-database
ports:
- '${LOBE_PORT}:3210' # LobeChat
depends_on:
postgresql:
condition: service_healthy
minio:
condition: service_started
logto:
condition: service_started
env_file:
- .env
restart: always
networks:
- lobe-network
volumes:
data:
driver: local
s3_data:
driver: local
networks:
lobe-network: |
Beta Was this translation helpful? Give feedback.
-
|
More like related to this alpinelinux/docker-alpine#403 Could you run if yes, run the following code in container, then restart the container. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, container has a different one. Here you go: |
Beta Was this translation helpful? Give feedback.
-
|
then could you run the code to overwrite |
Beta Was this translation helpful? Give feedback.
-
|
found in docker/for-linux#755 , caused by |
Beta Was this translation helpful? Give feedback.
-
|
I tried it, it couldn't reach database via |
Beta Was this translation helpful? Give feedback.
-
|
nonono... I mean run this to replace, or using text-editor to modify |
Beta Was this translation helpful? Give feedback.
-
|
Oh, okay. |
Beta Was this translation helpful? Give feedback.
-
|
It worked! |
Beta Was this translation helpful? Give feedback.
-
|
Interesting... The thing I don't understand is how app can't reach but tools like nslookup, curl even nodejs in the container is able to reach. |
Beta Was this translation helpful? Give feedback.
-
|
I added this lines in docker-compose and now the solution is permanent! dns:
- 8.8.4.4
- 8.8.8.8Btw, I checked /etc/resolv.conf after adding dns option and interestingly it's the same but see the comment (ExtServers): |
Beta Was this translation helpful? Give feedback.
-
|
The --dns configuration will be overridden by the storage space mapping configuration file, so it is recommended that if you set the DNS configuration file on the storage space mapping host, you do not need to configure DNS in docker-compose anymore. And it is recommended to change the mapping method to read-only access like this: To prevent the container service from modifying this configuration file on the host after startup. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, okay thanks! I am re-marking the answer then. |
Beta Was this translation helpful? Give feedback.
-
|
This issue is closed, If you have any questions, you can comment and reply. |
Beta Was this translation helpful? Give feedback.
-
|
create a file to save dns configuration like |
Beta Was this translation helpful? Give feedback.
-
|
I am using Zeaber and dockerfile, but this problem also occurs |
Beta Was this translation helpful? Give feedback.
The --dns configuration will be overridden by the storage space mapping configuration file, so it is recommended that if you set the DNS configuration file on the storage space mapping host, you do not need to configure DNS in docker-compose anymore. And it is recommended to change the mapping method to read-only access like this:
To prevent the container service from modifying this configuration file on the host after startup.