Cannot connect to 127.0.0.1:58526 (Port shown under the Developer Mode of WSA)

Question

Cannot connect to 127.0.0.1:58526 (Port shown under the Developer Mode of WSA)

Haowen He 21

As shown in the title, I can't connect to 127.0.0.1:58526 via adb.

(cannot connect to 127.0.0.1:58526: No connection could be made because the target machine actively refused it. (10061))
I checked the netstat and the result showed that Port 58526 is not listening! ( And of course my Developer Mode is ON)

BTW, I can connect to WSA by the given IP in the WSA Setting panel( e.g.：172.22..).

How can I fix this? Thanks!

Lee Solway 6 Reputation points

2022-08-03T10:50:38.167+00:00

Any progress on this issue? I am seeing the same problem, even after a reboot.
Andrew Leader-MSFT 306 Reputation points Microsoft Employee Moderator

2022-08-03T21:32:00.697+00:00

Hey Lee, can you let me know what version of WSA you're running? In the Settings app, go to the About page, and let me know your version number!
kris 16 Reputation points

2022-08-20T19:37:08.94+00:00

Hey Andrew,

I think this problem appeared after WSA received the Android 11 update. I am facing the same issue with WSA V2206.40000.15.0.

Apparently, the developer settings has been moved to a different hamburger menu altogether, with the refresh option (to refresh the IP Address) missing. Sideloading APKs seem to be broken as of now. WSATools doesn't work due to ADB being disabled in WSA Android settings and adb connect doesn't work due to the error pointed out by OP.

Please refer to the imgur link to see what I see.

https://imgur.com/a/NJHfNbG
Eirik Corneliussen 1 Reputation point

2022-09-19T11:29:44.403+00:00
I'm having the exact same issue. WSA settings is saying ADB can be connected on 127.0.0.1:58526, but I can no longer connect with any of these:

127.0.0.1:58526

{IPV4 address}:58526

localhost:58526
AshutoshCl 6 Reputation points

2022-09-29T12:32:01.957+00:00

@kris @Slion your workaround not working. Any other way to connect through adb
josie Payton 0 Reputation points

2023-09-07T11:07:17.28+00:00
If you're still experiencing the issue of not being able to connect to 127.0.0.1 on port 58526 even after a reboot, here are some additional steps to consider:

Check Application Logs: Review the logs or error messages generated by the application or service running on port 58526. These logs may provide insights into what's causing the connection issue.

Check Port Availability: Confirm that the port (58526) is not being used by another process or application on your computer. You can use the following command in the Command Prompt or Terminal to check for port usage:

Copy code netstat -ano | findstr :58526

If it returns any results, it means another process is using that port.

Check Binding Configuration: If you have control over the application or service, double-check the binding configuration to ensure it's correctly set to listen on 127.0.0.1:58526.

Temporary Disable Security Software: As mentioned earlier, security software or firewalls can sometimes block connections. Temporarily disable your security software (if safe to do so) and see if the connection issue persists. Remember to re-enable it afterward.

Try a Different Port: If possible, consider configuring the application or service to use a different port (one that is not currently in use) to see if the problem persists.

Test with a Different Application: To isolate the issue, try connecting to a different service or application running on a different port (e.g., a local web server on port 80). If you can connect to other services but not this specific one on port 58526, it may indicate an issue with that particular service or application.

Check for System Updates: Ensure that your operating system and any relevant software are up to date, as updates can sometimes resolve compatibility or connectivity issues.

If you continue to encounter problems, it may be helpful to reach out to the support or documentation for the specific application or service you're trying to connect to on port 58526. They may be able to provide more targeted assistance based on the details of the application's setup and configuration.
Benny Code 0 Reputation points

2023-09-12T22:08:57.2933333+00:00

Have you tried using an IP that starts with 192.168? Additionally, go to the WSA settings to explore the "Experimental features" and make sure to enable "Local network access". I also made a video about it showing how to successfully connect: https://www.youtube.com/watch?v=XCKNH5ymBN0&t=198s
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

7 answers

Your answer

Lee Solway 6 Reputation points

2022-08-03T10:50:38.167+00:00

Any progress on this issue? I am seeing the same problem, even after a reboot.
Andrew Leader-MSFT 306 Reputation points Microsoft Employee Moderator

2022-08-03T21:32:00.697+00:00

Hey Lee, can you let me know what version of WSA you're running? In the Settings app, go to the About page, and let me know your version number!
kris 16 Reputation points

2022-08-20T19:37:08.94+00:00

Hey Andrew,

I think this problem appeared after WSA received the Android 11 update. I am facing the same issue with WSA V2206.40000.15.0.

Apparently, the developer settings has been moved to a different hamburger menu altogether, with the refresh option (to refresh the IP Address) missing. Sideloading APKs seem to be broken as of now. WSATools doesn't work due to ADB being disabled in WSA Android settings and adb connect doesn't work due to the error pointed out by OP.

Please refer to the imgur link to see what I see.

https://imgur.com/a/NJHfNbG
Eirik Corneliussen 1 Reputation point

2022-09-19T11:29:44.403+00:00

I'm having the exact same issue. WSA settings is saying ADB can be connected on 127.0.0.1:58526, but I can no longer connect with any of these:

127.0.0.1:58526

{IPV4 address}:58526

localhost:58526
AshutoshCl 6 Reputation points

2022-09-29T12:32:01.957+00:00

@kris @Slion your workaround not working. Any other way to connect through adb
Benny Code 0 Reputation points

2023-09-12T22:08:57.2933333+00:00

Have you tried using an IP that starts with 192.168? Additionally, go to the WSA settings to explore the "Experimental features" and make sure to enable "Local network access". I also made a video about it showing how to successfully connect: https://www.youtube.com/watch?v=XCKNH5ymBN0&t=198s
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

Slion 41

Go to WSA settings Developer tab. Click on Manage developer settings which opens the Android developer options. Find USB debugging. turn it on if it was not already. If it is already on, turn it off before turning it back on. Go back to your Windows command prompt adb connect should work again.

lzr0 1 Reputation point

2022-12-29T20:08:18.107+00:00

BlockquoteGo to WSA settings Developer tab. Click on Manage developer settings which opens the Android developer options. Find USB debugging. turn it on if it was not already. If it is already on, turn it off before turning it back on.
Blockquote

Slion, I don't see any Developer tab in WSA settings. Could you please clarify how to do this action (I have the same problem of missing adp)?

!
Jeff 0 Reputation points

2023-06-10T04:41:48.12+00:00

good idea
David Richmond 6 Reputation points

2023-10-06T23:33:29.8033333+00:00

This worked exactly for me. I believe the workflow is supposed to be connect adb > WSA prompts for dev enablement > dev enabled with USB debugging. However, I'd proactively enabled dev mode. So perhaps the checks performed by WSA during ADB connection thought the device was already authorized. Disabling USB debugging, turning it back on, and THEN doing adb connect <ip:port> popped the authorize prompt. After authorizing the device, adb connections now succeed.

Answer 2

Andrew Leader-MSFT 306 Microsoft Employee Moderator

Hi, have you tried the following...

Reboot your PC
Launch a WSA app (like Amazon Appstore)
Attempt connecting again

When you see the "target machine actively refused it" 10061 error, you'll often just have to reboot your PC and then relaunch WSA and try again.

Greg Kochaniak 0 Reputation points

2024-05-27T12:54:10.7766667+00:00

I tried just shutting down and restarting WSA, after disabling/re-enabling USB debugging etc. - nothing helped. Finally read the above post, rebooted, and as soon as I tried to connect ADB to WSA, got the authorization prompt to allow this machine. Works like a charm again, thanks! After reading the earlier replies, saying reboot did not work - I did try disabling/re-enabling developer options first, disabling and re-enabling USB debugging, and clicked and confirmed to remove ADB authorizations in Developer Options. By themselves, these operations did not help, but after subsequent reboot of the computer, it started to work.

Answer 3

kris 16

Hey, so I've been able to find a solution to the issue.

First, open a PowerShell window and run

ipconfig

You'll get a list containing lots of IP Addresses divided into categories. Look for a header with a Default tag.

Now copy the IPv4 Address that's written there.

Connect to the WSA using the following code:

adb connect <Your IPv4 Address>:58526

You'll get a prompt from WSA requesting you to allow debugging. Press Accept and you're done!

Source:
https://learn.microsoft.com/en-us/windows/android/wsa/

jr ljrproperties.com 0 Reputation points

2023-02-09T01:35:17.62+00:00

worked for me, thanks!!

Answer 4

yahgoo 1

Click Hamburger menu in WSA, select Developer
Enable Developer mode
Click Manage Developer Settings
Enable Use Developer option
Enable USB Debugging
Restart pc
In Terminal, type following commands
adb connect <Your IPv4 Address>:58526
adb install xxxx.apk

lzr0 1 Reputation point

2022-12-29T20:15:02.377+00:00

>Click Hamburger menu in WSA, select Developer

Enable Developer mode
Click Manage Developer Settings
Enable Use Developer option
Enable USB Debugging<<

Hi, yahgoo-9097, I may be missing it, but I don't see an option of enabling developer mode in WSA (and there is no hamburger menu). Could you please explain?

Answer 5

Jennifer Guzman 0

I don't know if Hyper-V is required to run WSA apps, but I was having this issue as well - unable to connect to the ADB port - and enabling Hyper-V solved this issue for me.

Benny Code 0 Reputation points

2023-09-07T10:39:43.64+00:00

I am trying to connect from Ubuntu (WSL2) to the Windows Subsystem for Android (WSA). Developer Mode is turned on but I am getting this error:

adb connect 127.0.0.1:58526

* daemon not running; starting now at tcp:5037

* daemon started successfully

failed to connect to '127.0.0.1:58526': Connection refused

What fixed it for me was using my local IPv4 address (192.168...). It had to be the one with 192 and not 172!

Share via

Cannot connect to 127.0.0.1:58526 (Port shown under the Developer Mode of WSA)

7 answers

Your answer