You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/spring-apps/troubleshooting-vnet.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,11 +42,11 @@ To set up the Azure Spring Apps service instance by using the Resource Manager t
42
42
43
43
## My application can't be registered or it can't get settings from the config server
44
44
45
-
The applications running inside the Azure Spring Apps user cluster need to access the Eurekar Server and the Config Server in system runtime cluster via the `<service-instance-name>.svc.private.azuremicroservices.io` domain.
45
+
The applications running inside the Azure Spring Apps user cluster need to access the Eureka Server and the Config Server in the system runtime cluster via the `<service-instance-name>.svc.private.azuremicroservices.io` domain.
46
46
47
47
This problem occurs if your virtual network is configured with custom DNS settings. In this case, the private DNS zone used by Azure Spring Apps is ineffective. Add the Azure DNS IP 168.63.129.16 as the upstream DNS server in the custom DNS server.
48
48
49
-
If your custom DNS server can't add Azure DNS IP `168.63.129.16` as the upstream DNS server, then add the DNS record `*.svc.private.azuremicroservices.io` to the IP of your application. For more information, see [Find the IP for your application](access-app-virtual-network.md#find-the-ip-for-your-application).
49
+
If your custom DNS server can't add the Azure DNS IP `168.63.129.16` as the upstream DNS server, then add the DNS record `*.svc.private.azuremicroservices.io` to the IP of your application. For more information, see the [Find the IP for your application](access-app-virtual-network.md#find-the-ip-for-your-application) section of [Access an app in Azure Spring Apps in a virtual network](access-app-virtual-network.md).
50
50
51
51
## I can't access my application's endpoint or test endpoint in a virtual network
52
52
@@ -67,15 +67,15 @@ For more information, see [Access your application in a private network](./acces
67
67
68
68
Azure Spring Apps supports exposing applications to the internet by using public endpoints. For more information, see [Expose applications on Azure Spring Apps to the internet from a public network](how-to-access-app-from-internet-virtual-network.md).
69
69
70
-
If you're using a user defined route feature, some features aren't supported because of asymmetric routing. For unsupported features, use the following list:
70
+
If you're using a user defined route feature, some features aren't supported because of asymmetric routing. For unsupported features, see the following list:
71
71
72
-
- Use public network to access the application through public endpoint.
73
-
- Use public network to access the log stream.
74
-
- Use public network to access the App console.
72
+
- Use the public network to access the application through the public endpoint.
73
+
- Use the public network to access the log stream.
74
+
- Use the public network to access the app console.
75
75
76
76
For more information, see [Control egress traffic for an Azure Spring Apps instance](how-to-create-user-defined-route-instance.md).
77
77
78
-
Similar limitations also apply to Azure Spring Apps when egress traffics are routed to a firewall. The problem occurs because both situations introduce asymmetric routing into the cluster. Packets arrive on the endpoint's public IP address but return to the firewall via the private IP address. So, the firewall must block such traffic. For more information, see [Bring your own route table](how-to-deploy-in-azure-virtual-network.md#bring-your-own-route-table).
78
+
Similar limitations also apply to Azure Spring Apps when egress traffics are routed to a firewall. The problem occurs because both situations introduce asymmetric routing into the cluster. Packets arrive on the endpoint's public IP address but return to the firewall via the private IP address. So, the firewall must block such traffic. For more information, see the [Bring your own route table](how-to-deploy-in-azure-virtual-network.md#bring-your-own-route-table) section of [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
79
79
80
80
If you're routing egress traffics to a firewall but also need to expose the application to internet, use the expose applications to the internet with TLS Termination feature. For more information, see [Expose applications to the internet with TLS Termination at Application Gateway](expose-apps-gateway-tls-termination.md).
0 commit comments