Ошибка no connection could be made because the target machine actively refused it

    Несколько недель тому назад я заметил, что у одного из наших заказчиков NGINX спамит в error.log ошибки начинающиеся с «connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream…»:

2020/11/20 19:47:24 [error] 8560#14660: *1247 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: 111.111.111.111, server: , request: «GET /favicon.ico HTTP/1.1», upstream: «https://XYZ.XYZ.XYZ.XYZ:3000/favicon.ico», host: «domain», referrer: «https://domain/»
2020/11/20 19:47:59 [error] 8560#14660: *1247 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: 111.111.111.111, server: , request: «GET /ru/search?cs=N4I…

где XYZ.XYZ.XYZ.XYZ – это IP адрес их сайта, а domain – его доменное имя.
    Я где-то читал, что иногда программы могут избавляться от глюков если у них в настройках вместо «localhost» указать «127.0.0.1». Так и получилось. В одной из строк nginx.conf я сделал подобную замену:

...
server {
...
	location / {
		proxy_http_version 1.1;
		proxy_redirect off;
   			proxy_set_header Host $host;
   			proxy_set_header Upgrade $http_upgrade;
   			proxy_set_header Connection "upgrade";
		proxy_pass https://127.0.0.1:3000;
	}

	location /api/ {
		proxy_http_version 1.1;
		proxy_redirect off;
   			proxy_set_header Host $proxy_host;
   			proxy_set_header Upgrade $http_upgrade;
   			proxy_set_header Connection "upgrade";
		proxy_pass https://XYZ.XYZ.XYZ.XYZ:4443;
	}
}
...

и ошибка больше не появляется.

Multiple users have been facing an error when using certain online services and applications. Every time they try to login or run the program a statement appears, saying, No connection could be made because the target machine actively refused it. Users have been facing this issue while logging in or connecting to the Mysql server, while logging into the azure AD, using Vmware and send HTTPS request. Furthermore, the error also appears while using the Autodesk application. In this troubleshooting guide, we will be giving you some methods along with some important information regarding the error.

Causes of No Connection Could Be Made Because The Target Machine Actively Refused it Error

Talking of the causes behind No connection could be made because the target machine actively refused it an error. Multiple users have reported that the error appears because of active firewall and antivirus, furthermore, the error also appears because of network issues. However, if you are facing this error while browsing any website it may be because of an SSL certificate. If you are using any application and getting the error, maybe the software files have been corrupted.

• Active firewall and antivirus
• Network issues
• SSL certificate
• Software files have been corrupted

Similar Types No Connection Could Be Made Because The Target Machine Actively Refused it Error

• Error while connecting to host No Connection Could Be Made Because The Target Machine Actively Refused it
• Qlik sense
• Town of Salem no connection could be made
• Xerxes no connection could be made
• 74.125 130.109 587
• 13.107 136.9 443
• 127.0.0.1:443 + SSRS
• Sqlstate[hy000] [2002]

Now let’s go through all the possible ways by which you can fix No Connection Could Be Made Because The Target Machine Actively Refused it Error. We have managed to gather some methods. The following are the methods.

1. Disable Windows Firewall

The first and the foremost thing that you must do is to disable your windows firewall. Windows firewall prevents certain services from running and executing and thus the [winerror 10061] No Connection Could Be Made Because The Target Machine Actively Refused it error appears. Follow the steps to disable the firewall.

• STEP 1. Open the Run window, press Win + R
• STEP 2. In the Run window now type control panel and Hit Enter
• STEP 3. Once the Control Panel window is opened, change the view to small
• STEP 4. Locate and click on Windows Defender Firewall
• STEP 5. In this new window, On the left-hand side, click on Turn Windows Defender Firewall On or Off link

• STEP 6. A new window will open, now from the options select Turn Windows Defender Firewall OFF (not recommended)

• STEP 7. Make sure to set this for both public and private network settings
• STEP 8. Finally, Click on Apply and then OK
• STEP 9. Restart your system and check if the error appears

2. Fixing the Error when using VMware

One of the major scenarios in which the error seems to appear is when using the VMware. Below are some ways you can use to eliminate the No Connection Could Be Made Because The Target Machine Actively Refused it http://127.0.0.1/ issue.

A). Starting the VMware vCenter Workflow Manager Service

• STEP 1. Open the Run window, press Win + R
• STEP 2. In the Run window now type services.MSC and Hit Enter

• STEP 3. Once the services window opens up, locate VMware vCenter Workflow Manager Service

• STEP 4. Once you have found the service, right-click on the service and go to Properties
• STEP 5. Now firstly Start the service, by clicking on the Start button at the bottom, of the service is already running, restart it
• STEP 6. Now put the Startup type to Automatic
• STEP 7. Once done restart your system and check if the error still occurs

B). Connecting the vCenter Server Appliance (VCSA) as Root

• STEP 1. Make sure to follow all the steps from Method A.
• STEP 2. Now Open the command window with admin privileges
• STEP 3. Execute the below commands

service --stop vmware-vpx-workflow

• STEP 4. Now enter the below command

service --start vmware-vpx-workflow

• STEP 5. Now restart your system and use VMware without errors

3. Fixing the Error when using Autodesk Maya Application

A lot of users have been facing this sqlstate[hy000] [2002] No Connection Could Be Made Because The Target Machine Actively Refused it connection failed issue when using the Maya application. Below are some methods that will fix the issue.

A). Error when Submitting Jobs from 3ds Max & Maya

• To resolve the issue when connecting to the render node kindly use a dedicated/static IP/ physically based IP address or machine name.
• Also, you have to make sure that all the ports important and recommended ports are accessible to the backburner
• Cross-check whether the Backburner Manager is set to either the IP Address or Host Name
• Before you submit any job, open Maya Script Editor and check any errors

Window > General Editors > Script Editor 

B). Error when Submitting Jobs from Maya

The error can be resolved by resetting the Maya.

• STEP 1. In the Start menu, click on My computer, then navigate to the below path

C:Users<username>My DocumentsMaya<version>

• STEP 2. Once you reach at the directory locate the prefs folder

• STEP 3. Now rename it to prefsOldl
• STEP 4. Now Restart Maya
• STEP 5. If you have been prompted select Create Default Preferences

4. Fixing the Error when Browsing Websites

Users have been facing veeam No Connection Could Be Made Because The Target Machine Actively Refused It Error while browsing the website. It occurs because of SSL is not trusted by the browser. To fix that follow steps.

A). Enable SSL in Chrome

• STEP 1. Open Google Chrome > Press Alt + f
• STEP 2. From the menu click on settings
• STEP 3. On the left click on Privacy and Security
• STEP 4. Now on the right scroll a little and click on Manage certificates

• STEP 5. In this new window click on Advanced button
• STEP 6. Now scroll and tick all version of Use SSL

B). Enable SSL in Firefox

• STEP 1. Open up Firefox and enter the below command in the address bar

about:config

• STEP 2. Now in the search bar type the below command

tls.version

• STEP 3. Enable them to fix the issue

Conclusion:

With this being the end of the troubleshooting guide on No Connection Could Be Made Because The Target Machine Actively Refused It Error. We have given you all the methods to fix the issue.

We hope by following this No Connection Could Be Made Because The Target Machine Actively Refused it guide your issue is fixed. For more troubleshooting, guides and tips follow us. Thank you!

1С Ошибка при выполнении операции с информационной базой

• Question

• I hosted a wcf service application using windows services. When my client (ASP.NET) tries to call the service class hosted by the windows service, I get this error «TCP error code 10061: No connection could be made because the target machine actively refused it. «. Is there a fix for this? The same code works fine if I host it using a console application.

Android Studio’s ADB (Android Debug Bridge) is a command-line tool to communicate with an Android device (either through a USB or by using TCP protocol). Many users, when issuing an ADB command e.g., adb connect, they encounter the ADB error 10061 with the following type of message:

The ADB error 10061 means that the remote device is refusing the client’s TCP connection request (either the IP or port). This error can occur due to many reasons but the following can be categorized as the main:

Update the PC’s OS to the Latest Build

The ADB error 10061 could be a result of the incompatibility between the outdated PC’s OS and other system modules (especially, related to ADB). In such a case, updating the PC’s OS to the latest build may solve the problem. For elucidation, we will discuss the process of updating a Windows PC.

1. Click Windows, search and open Check for Updates.
2. Now, in the right pane of the resulting window, click on Check for Updates, and if some updates are available, download and install the updates (optional updates as well).
3. Once the PC’s OS is updated, restart the system and check if the ADB error 10061 is cleared.

Update the Android Studio and SDK Platform Tools

‘No connection could be made ADB error 10061’ can be a result of an outdated Android Studio or SDK Platform-tools as it may lead to incompatibility with the OS/host device. Here, updating the Android Studio and SDK Platform Tools may solve the problem.

1. Launch the Android Studio and expand its File menu.
2. Now select Settings and in the left half of the resulting menu, expand Appearance and Behavior.
3. Then expand System Settings and head to the Updates tab.
4. Now, in the right half of the window, click on Check Now and if an update is available, download and install the update.
5. Then relaunch the Android Studio and check if the ADB error 10061 is cleared.
6. If not, again head to the System Settings tab of the Android Studio Settings and in the left pane, select Android SDK.
7. Now, in the right pane, check if an update of the relevant packages is available. If so, download and install the update.
8. Afterward, relaunch the Android Studio and check if the no connection could be made issue is resolved.

Update the Android Device Driver or Use an OEM-Provided Driver

If the driver of the Android device is outdated or improper in the system’s Device Manager, then you may encounter the ADB error 10061 in the Android Studio as it can cause incompatibility between the system and target machine. In this context, updating the Android device drive to the latest build or using an OEM-provided driver may solve the problem.

1. Right-click on Windows and select Device Manager.
2. Now, try to find the Android device in the options shown. You may find it under any of the different categories like Android devices, Android phones, portable devices, other devices, or USB controllers.
3. Once found, right-click on the Android device and select Update Driver.
4. Then click on Search Automatically for Drivers and if no update is available, then click on Search for Updated Drivers on Windows Update.
5. If an updated driver is available, download and install the update.
6. Once installed, restart your system, and upon restart, check if the ADB issue is resolved.
7. If not, steer to the OEM website (like Huawei) and download the latest drivers as per the phone’s model.
8. Now, right-click on the downloaded driver and select Run as Administrator.
9. Then follow the prompts on the screen to install the driver and afterward, restart your system.
10. Upon restart, check if the ADB error 10061 is cleared.
11. If this doesn’t work, right-click on the Android device in the Device Manager and select Update Driver.
12. Now, select Browse My Computer for Drivers and click on Let Me Pick from a List of Available Drivers on My Computer.
13. Then select another driver and apply the changes made.
14. Now restart your system and upon restart, check if the ADB issue is cleared.
15. If this didn’t do the trick, then you may try all the other Android device drivers in the Device Manager one by one and check if any of the drivers solve the problem.

Disconnect the VPN on the System and Android Device

The Android Studio requires that both devices should be on the same network and if any of these devices have a VPN enabled on them, then the Android Studio may fail to find the other device on the same network, resulting in the ADB error 10061. In this context, disconnecting the VPN on both devices may solve the problem.

1. Expand the hidden icon of the system tray and double-click on the VPN icon (e.g., AnyConnect).
2. Then select Disconnect and then, on the Android device, swipe up (or down) to show the Notifications tray of the device.
3. Now, tap on VPN (if shown) and then tap on Disconnect.
4. Once both devices are disconnected from the VPN, re-launch Android Studio, and while keeping the Troubleshoot device connection issues tab opened on the Studio, check if the target machine actively refused connection error 10061 is resolved.
5. If that did not work, then check if disabling/enabling the Wi-Fi of the Android device solves the ADB problem.

Disable Other Network Adapters on the System

For proper functioning of the ADB, Android Studio requires both devices to be on the same network but the ADB debug bridge is not good at handling multiple networks. So, the usage of multiple networks (Ethernet or Wi-Fi) on a system may trigger the ADB behavior under discussion. In this scenario, disabling other network adapters on the system may solve the problem.

1. Right-click on Windows and select Network Connections.
2. Now, select Change Adapter Options and right-click on any of the network adapters.
3. Then select Disable and repeat the same on all the network adapters except the Wi-Fi adapter.
4. Now restart the Android Studio and check if the ADB error 10061 is cleared.
5. If that did not work, expand the hidden icon of the system tray and click on the Wi-Fi icon.
6. Now select Airplane Mode and on the Android Device, swipe up (or down) to expand the Notifications tray of the device.
7. Then tap on the Airplane icon and afterward, enable the Wi-Fi on both devices (without disabling the Airplane mode).
8. Now re-launch the Android Studio and check if the ADB error 10061 is cleared.
9. If the issue persists, check if disabling Wi-Fi in the router (not restarting the router) and then enabling it back solves the problem.

If that did not work, check if using Microsoft’s Your Phone app to connect the system/device and then executing the ADB commands solve the problem.

Edit the USB Debugging Settings of the Android Device

The USB debugging is an essential component of the ADB mechanism and if its settings are misconfigured, then ADB may show the warning of no connection could be made because the target machine actively refused it (10061). In this scenario, properly configuring the USB debugging of the Android device may solve the problem.

Enable USB Debugging in the Android Device Settings

1. Firstly, enable the Developer Options of the Android device and then open the Android Settings.
2. Now open Developer Options and enable USB Debugging (if disabled), otherwise disable/enable the USB Debugging. Keep in mind that for some Android models (like MXQ Pro), you may find the USB Debugging option in Apps > Settings (not in Android Settings).
3. Then execute the following in the elevated Command Prompt on the system:

   adb connect <DeviceIP:Port>.

   

4. Then confirm the connection on the Android phone’s screen and check if the ADB error 10061 is cleared.
5. If not, Revoke USB Debugging Authorizations and enable the Allow ADB Debugging in Charge Only Mode (some Android models might show the Allow ADB Debugging in Load Only Mode option) to check if that solves the problem.
6. If that did not work, check if disabling the Aggressive Wi-Fi to Cellular Handover in the Developer’s Options solves the problem.

Enable Wireless, Network, or Bluetooth Debugging

1. Launch Settings of Android 11 (or above) and open its Developer Options.
2. Now enable Wireless Debugging and then click on Allow in the Allow Wireless Debugging on This Network. If you trust and want to regularly use the wireless debugging feature on the current network, then checkmark Always Allow on This Network.
3. Now, on the system’s elevated Command Prompt, execute the following:

   adb pair [Phone_IPAddress]:[PORT] [PAIRING CODE]

   

4. Once successful, execute the following and check if the ADB error 10061 is cleared:

   adb connect [Phone_IPAddress]:[PORT]

Keep in mind that some Android TV devices may show a Network ADB option. Also, if you are trying to connect to a smart Android device (like a watch), then you may enable Bluetooth Debugging in the device settings.

Change the USB Connection Mode to the File Transfer

1. Launch the Android device settings and open Developer Options.
2. Now tap on Revoke USB Debugging Authorizations and connect the device with the PC via a USB cable.
3. Once connected, swipe up (or down) to open Notifications Tray and tap on USB Usage Mode.
4. Then select File Transfer and execute the following in the elevated Command Prompt to check if the error 10061 is cleared:

   adb connect <DeviceIP:5555>

   

5. If that did not work, check if changing the USB Connection Mode to Camera solves the problem.
6. If the issue persists, check if disabling Stay Awake in the Developers Options solves the problem.

Execute the Different ADB Commands with Different Parameters

The ADB connection may get refused by the target machine if a wrong parameter is used in the ADB command e.g., if the device’s IP was changed after a restart and the previous IP was used in the ADB command, then a user may encounter the error 10061. In this context, executing the ADB command with different parameters may solve the connection refused error. But before going to that route, check if restarting everything involved in the process like Android Studio, computer, router, phone, etc. solves the problem.

Check the IP of the Target Device

1. Open the Android phone settings and tap on Wi-Fi.
2. Now, click on the hamburger icon and select Advanced Settings.
3. Then check the IP address of the Android device and make sure you are executing the following in the elevated Command Prompt on the system with the correct IP:

   adb connect <DeviceIP>

   

4. Afterward, check if the connection actively refused issue is resolved. 

Disconnect ADB from the Other Devices

If multiple devices are being used with the Android Studio or the same Android device is connected after some time, then a connection with the other device or previous connection to the current device might cause the target machine to actively refuse the connection. In such a case, disconnecting ADB from the other device may solve the problem.

1. Right-click on Windows and search for Command Prompt.
2. Now right-click on Command Prompt and in the mini-menu, choose, Run as Administrator.
3. Then, execute the following:

   adb disconnect

   

4. Now relaunch the Android Studio and execute the following to check if the ADB connection is successful:

   adb tcpip 5555
   
   adb connect <the_device_ip>

5. If that did not work, then execute the following command in the elevated Command Prompt:

   adb devices

6. If there are multiple devices shown like the following:

   List of devices attached
   
   dfdcdc9c device
   
   emulator-5554   device

7. Then you may execute the TCPIP and connect commands as the device ID but add -s to them like the following:

   adb -s dfdcdc9c tcpip 5555
   
   adb -s dfdcdc9c connect <ip addr>

8. Now check if the ADB error 10061 is cleared.

Use a Continual Ping on the System with Other ADB Commands

If that did not work,  you may set up a continual Ping on the system to check if the system can connect to the device IP and then execute the ADB commands afterward.

1. Launch the elevated Command Prompt on the system and execute the following (whenever you have to stop the Ping command, use the Ctrl+C shortcut):

   ping -t (DeviceIP)

   

2. If the connection is successfully made, connect the device and system through a USB cable.
3. Now try the following ADB commands to check if the issue is resolved.

   adb disconnect
   
   adb kill-server
   
   adb start-server
   
   adb usb
   
   adb devices
   
   adb tcpip 5555

4. Then unplug the USB cable from the system and execute the following command in the system’s elevated Command Prompt:

   adb connect <DeviceIP:Port>

5. After a successful connection, you may expand Studio>>Run and then select Device to check if the ADB error is cleared.

If the ping command failed at step 2, then try to find out the networking issue causing the ADB error.

Use a Different Port in the ADB Commands

If the above ADB commands did not work, then the issue could be due to the wrong port number used in the commands. Here, trying different port numbers might solve the problem.

1. Repeat the steps mentioned above but at the TCPIP command execute the following:

   adb tcpip 5557
   
   adb connect (DeviceIP)

2. And then execute the following:

   adb tcpip 5555
   
   adb connect (DeviceIP)

Keep in mind some devices have port 5555 closed by default (like a Mi Box) and to open the required port, you may have to connect the device with a USB to the system and execute the following:

adb tcpip 5555

Also, do note that the port will be closed if the device restarts and you may have to repeat the above step to open the required port.

Use the IP Address of the Local Host in the Command if Using an Android Emulator

If the issue is occurring with an Android emulator, then it could be a result of the ADB attempts to connect to the localhost over IPv6 (that will be “::1”, not, 127.0.0.1). In this context, using the IPv4 address of the local host may solve the problem.

1. Execute the following in the elevated Command Prompt on the system:

   adb forward tcp:4444 localabstract:/adb-hub
   
   adb connect 127.0.0.1:4444

2. Then check if the ADB connection issue is resolved.
3. If that did not work, then check if using the ADB connect command without specifying a port number solves the problem.

   adb connect 127.0.0.1

If none of the above did the trick for you, then you may try an ADB plugin (like Wi-Fi ADB Ultimate or scrcpy) to solve the issue. If that did not work, then you may reset the system or phone to the factory defaults. For some advanced techies, adding the device’s IP to the ARP table of the system may solve the problem.