You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "giangnh13579 (via GitHub)" <gi...@apache.org> on 2024/12/30 09:38:02 UTC

Re: [I] help request: Failed to parse domain [apisix]

giangnh13579 commented on issue #10505:
URL: https://github.com/apache/apisix/issues/10505#issuecomment-2565243572

   > @shreemaan-abhishek, it seems like issue is not connected with `apisix.yaml` config changing (as described in #10530), we are facing same issue at initial startup (without chaning apisix.yaml) in docker environment. We have the following apisix.yaml configuration:
   > 
   > ```yaml
   > upstreams:
   >   -
   >     id: some_service_upstream
   >     nodes:
   >       "${{SOME_SERVICE_UPSTREAM_ADDRESS}}": 1
   >     type: roundrobin
   > ```
   > 
   > and docker-compose file:
   > 
   > ```yaml
   > version: "3"
   > 
   > services:
   >   apisix:
   >     build:
   >       context: ../../gateway
   >       dockerfile: ../docker/Dockerfile.public-api-gateway
   >     container_name: apisix_api_gateway
   >     restart: always
   >     environment:
   >       # Upstream Addresses Envs Start
   >       LOS_SERVICE_UPSTREAM_ADDRESS: ${LOS_SERVICE_UPSTREAM_ADDRESS}
   >     ports:
   >       - "9180:9180/tcp"
   >       - "9080:9080/tcp"
   >       - "9091:9091/tcp"
   >       - "9444:9443/tcp"
   >       - "9092:9092/tcp"
   >     networks:
   >       apisix:
   > 
   > networks:
   >   apisix:
   >     driver: bridge
   > ```
   > 
   > while doing requests to LOS service we are seeing this in console:
   > 
   > ![image](https://private-user-images.githubusercontent.com/67690609/335691771-462a0f81-5a6d-4449-9546-13e7cdb88f92.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzU1NTA4MDUsIm5iZiI6MTczNTU1MDUwNSwicGF0aCI6Ii82NzY5MDYwOS8zMzU2OTE3NzEtNDYyYTBmODEtNWE2ZC00NDQ5LTk1NDYtMTNlN2NkYjg4ZjkyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEyMzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMjMwVDA5MjE0NVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ5OWU3N2RlOThhNmQyYjI5MjcyZWNjYTllYTlkN2YyZmNhNTBkNjc0MTMyYTliYTVkNjY5NjIxMTgwZDllNWUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.K5LqYYxzOA2xjqn_LdqOYPBHeBJ9IRoFxpO1BzFqwiE)
   > 
   > but request is hitting upstream service.
   
   I'm using APISIX `3.11` in the docker environment and got the same error. Does this issue have any solution?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org