We have tried pinging Support.anydesk.com using our servers in diverse locations and the website returned the above results.
If Support.anydesk.com is down for us too there is nothing you can do except waiting. Probably the server is overloaded, down or unreachable because of a network problem, outage or website maintenance is in progress.
If the site is UP for us but you however cannot access it, try one of our following solutions:
1. It might be Browser Related:
Error 502 Bad Gateway Anydesk
Posted by 1 year ago. Got excited for the new Linux install on the laptop and need Teamviewer to integrate with Ninja, but upon going to teamviewer.com I get a sad face:/ Just me? This thread is archived. AnyDesk can run an unlimited amount of sessions from a device as long as resources allow. AnyDesk also can run several instances on a device. Based on your license, your AnyDesk client can have multiple sessions simultaneously. The Free and Lite license will only allow one simultaneous session. The Professional license allows for as many. Anydesk's support website is also down. 502 Bad Gateway nginx/1.10.3 I sent anydesk a message on Twitter.
To solve Browser related issues that might make the site/server down for you, do a full Browser refresh of this site. You can do this by holding down CTRL + F5 keys at the same time on your browser.
This trick works perfectly on Chrome, Firefox, Brave, Opera, Safari and whatever default browser comes with your Windows nowadays lol.
2. Clear Your Cookies and Cache.
The contents of all modern sites and apps today are usually cached. This means a copy is stored in your browser as long as you have visited that page before. This is to make it easier to access when next you visit that page. This might be a problem especially if the page was down last time you checked.
You might need to clear that out of your browser memory for the site to load properly.
3. Fix DNS Problems
Domain Name System (DNS) is what allows a site IP address (192.168.x.x) to be identified with words ( e.g .com, .us) in order to be remembered easily. This is usually provided by your Internet Service Provider.
To fix this, clear your local DNS cache to make sure that you grab the most recent cache that your ISP has.
Still having issues? Try sending your complaints or troubleshooting issues to the channels below:
- Twitter Support Account - https://twitter.com/Support.anydesk
Facebook Page - https://www.facebook.com/Support.anydesk
Learn how to troubleshoot bad gateway (502) errors received when using Azure Application Gateway.
Note
This article has been updated to use the Azure Az PowerShell module. The Az PowerShell module isthe recommended PowerShell module for interacting with Azure. To get started with the AzPowerShell module, see Install Azure PowerShell. To learn howto migrate to the Az PowerShell module, seeMigrate Azure PowerShell from AzureRM to Az.
Overview
After configuring an application gateway, one of the errors that you may see is 'Server Error: 502 - Web server received an invalid response while acting as a gateway or proxy server'. This error may happen for the following main reasons:
- NSG, UDR, or Custom DNS is blocking access to backend pool members.
- Back-end VMs or instances of virtual machine scale set aren't responding to the default health probe.
- Invalid or improper configuration of custom health probes.
- Azure Application Gateway's back-end pool isn't configured or empty.
- None of the VMs or instances in virtual machine scale set are healthy.
- Request time-out or connectivity issues with user requests.
Network Security Group, User Defined Route, or Custom DNS issue
Cause
If access to the backend is blocked because of an NSG, UDR, or custom DNS, application gateway instances can't reach the backend pool. This causes probe failures, resulting in 502 errors.
The NSG/UDR could be present either in the application gateway subnet or the subnet where the application VMs are deployed.
Similarly, the presence of a custom DNS in the VNet could also cause issues. A FQDN used for backend pool members might not resolve correctly by the user configured DNS server for the VNet.
Solution
Validate NSG, UDR, and DNS configuration by going through the following steps:
- Check NSGs associated with the application gateway subnet. Ensure that communication to backend isn't blocked.
- Check UDR associated with the application gateway subnet. Ensure that the UDR isn't directing traffic away from the backend subnet. For example, check for routing to network virtual appliances or default routes being advertised to the application gateway subnet via ExpressRoute/VPN.
- Check effective NSG and route with the backend VM
- Check presence of custom DNS in the VNet. DNS can be checked by looking at details of the VNet properties in the output.
If present, ensure that the DNS server can resolve the backend pool member's FQDN correctly.
Problems with default health probe
Cause
502 errors can also be frequent indicators that the default health probe can't reach back-end VMs.
When an application gateway instance is provisioned, it automatically configures a default health probe to each BackendAddressPool using properties of the BackendHttpSetting. No user input is required to set this probe. Specifically, when a load-balancing rule is configured, an association is made between a BackendHttpSetting and a BackendAddressPool. A default probe is configured for each of these associations and the application gateway starts a periodic health check connection to each instance in the BackendAddressPool at the port specified in the BackendHttpSetting element.
The following table lists the values associated with the default health probe:
| Probe property | Value | Description |
|---|---|---|
| Probe URL | http://127.0.0.1/ | URL path |
| Interval | 30 | Probe interval in seconds |
| Time-out | 30 | Probe time-out in seconds |
| Unhealthy threshold | 3 | Probe retry count. The back-end server is marked down after the consecutive probe failure count reaches the unhealthy threshold. |
Solution
- Ensure that a default site is configured and is listening at 127.0.0.1.
- If BackendHttpSetting specifies a port other than 80, the default site should be configured to listen at that port.
- The call to
http://127.0.0.1:portshould return an HTTP result code of 200. This should be returned within the 30-second timeout period. - Ensure that the port configured is open and that there are no firewall rules or Azure Network Security Groups, which block incoming or outgoing traffic on the port configured.
- If Azure classic VMs or Cloud Service is used with a FQDN or a public IP, ensure that the corresponding endpoint is opened.
- If the VM is configured via Azure Resource Manager and is outside the VNet where the application gateway is deployed, a Network Security Group must be configured to allow access on the desired port.
Problems with custom health probe
Cause
Custom health probes allow additional flexibility to the default probing behavior. When you use custom probes, you can configure the probe interval, the URL, the path to test, and how many failed responses to accept before marking the back-end pool instance as unhealthy.
The following additional properties are added:
| Probe property | Description |
|---|---|
| Name | Name of the probe. This name is used to refer to the probe in back-end HTTP settings. |
| Protocol | Protocol used to send the probe. The probe uses the protocol defined in the back-end HTTP settings |
| Host | Host name to send the probe. Applicable only when multi-site is configured on the application gateway. This is different from VM host name. |
| Path | Relative path of the probe. The valid path starts from '/'. The probe is sent to <protocol>://<host>:<port><path> |
| Interval | Probe interval in seconds. This is the time interval between two consecutive probes. |
| Time-out | Probe time-out in seconds. If a valid response isn't received within this time-out period, the probe is marked as failed. |
| Unhealthy threshold | Probe retry count. The back-end server is marked down after the consecutive probe failure count reaches the unhealthy threshold. |
Solution
Validate that the Custom Health Probe is configured correctly as the preceding table. In addition to the preceding troubleshooting steps, also ensure the following:
- Ensure that the probe is correctly specified as per the guide.
- If the application gateway is configured for a single site, by default the Host name should be specified as
127.0.0.1, unless otherwise configured in custom probe. - Ensure that a call to http://<host>:<port><path> returns an HTTP result code of 200.
- Ensure that Interval, Timeout, and UnhealtyThreshold are within the acceptable ranges.
- If using an HTTPS probe, make sure that the backend server doesn't require SNI by configuring a fallback certificate on the backend server itself.
Request time-out
Cause
When a user request is received, the application gateway applies the configured rules to the request and routes it to a back-end pool instance. It waits for a configurable interval of time for a response from the back-end instance. By default, this interval is 20 seconds. If the application gateway does not receive a response from back-end application in this interval, the user request gets a 502 error.
Solution
Application Gateway allows you to configure this setting via the BackendHttpSetting, which can be then applied to different pools. Different back-end pools can have different BackendHttpSetting, and a different request time-out configured.
/502-bad-gateway-error-explained-2622939-6fe4489451f04fbf9ed021f328defc4a.png "Anydesk 502 Bad Gateway")
Empty BackendAddressPool
Cause
If the application gateway has no VMs or virtual machine scale set configured in the back-end address pool, it can't route any customer request and sends a bad gateway error.
Anydesk 502 Bad Gateway Free
Solution
Ensure that the back-end address pool isn't empty. This can be done either via PowerShell, CLI, or portal.
The output from the preceding cmdlet should contain non-empty back-end address pool. The following example shows two pools returned which are configured with a FQDN or an IP addresses for the backend VMs. The provisioning state of the BackendAddressPool must be 'Succeeded'.
BackendAddressPoolsText:
Unhealthy instances in BackendAddressPool
Cause
If all the instances of BackendAddressPool are unhealthy, then the application gateway doesn't have any back-end to route user request to. This can also be the case when back-end instances are healthy but don't have the required application deployed.
Solution
Ensure that the instances are healthy and the application is properly configured. Check if the back-end instances can respond to a ping from another VM in the same VNet. If configured with a public end point, ensure a browser request to the web application is serviceable.
Next steps
If the preceding steps don't resolve the issue, open a support ticket.