You’re welcome

That’s not the same.

Well, as you see they are registered under address 192.168.225.153, not `localhost`.

2020-07-24 17:20:57 ERROR [department-service,,,] Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is feign.RetryableException: connect timed out executing GET http://employee-service/department/1%5D with root cause
java.net.SocketTimeoutException: connect timed out

I am running in my local Mac book.

I have bit modified bootstrap.yml to work with docker.

employee
spring:
application:
name: employee-service
cloud:
config:
fail-fast: true
discovery:
enabled: true
service-id: config-service

department
spring:
application:
name: department-service
cloud:
config:
fail-fast: true
discovery:
enabled: true
service-id: config-service

I have searched over net and found that discovery.enabled should be false. Is that the case?

My laptop is connected to my office VPN network and when I start eureka server,conifg, 3 client services, 1 spring cloud gateway in local environment all are registered with Eureka with IP:PORT.

I can see registered services on eureka portal like this : 192.168.225.153:config-service:8081, 192.168.225.153:employee-service:8082, 192.168.225.153:gateway-service:8085

With this configuration my spring cloud gateway not able to connect to downstream services (other 2 client service) on 192.168.225.153 IP.

Call to http://localhost:8085/employee/1 is not working. However when I directly make call to employee service using http://localhost:8082/1, it is working.

There is some issue between how gateway service is locating and connecting to downstream services. (e.g. employee, department)

If I disconnect from internet and restart all the services, Eureka registered services with machine name/host name.

I can see registered services on eureka portal like this : :config-service:8081, :employee-service:8082, :gateway-service:8085

Call to http://localhost:8085/employee/1 is now working. In this case, gateway is able to locate and connect with downstream services.

Any idea why services are not located by gateway when I am connected to my office VPN?

You can remove the route declarations as well, and then you could access it using /employee-service path. For more details about Spring Cloud Gateway you may watch my online course: https://youtu.be/XIkSWHX38Tg

I’ve already tried that as well.
Setting the same path, filters, … with pure Java code works though.
But I feel like it’s a less good practice to do it this way. :/

Thanks 🙂 You should try to access it using just /employee path.

First of all, thank you for this amazing tutorial !
Altough, I’m having an issue with Spring Gateway.

I set up a route using the following parameters :
” id: employee-service
uri: lb://employee-service
predicates:
– Path=/employee/** ”
However, I can only access my employee-service using the “/employee-service/endpoint” URI, the Path predicate isn’t working. Do you have any idea of what would cause that? 🙂