But those are different interfaces, so no connection is made. When debugging locally, this can happen because Visual Studio is a 32-bit application, so it uses the 64-bit version of the remote debugger to debug 64-bit applications. 2? Hello, I trying to attach a debugger to a program in wsl2 (with the version of the IDE in the title). It might restrict or allow only certain TCP/IP addresses through, or it might allow or have open only specific ports. Try to: Check the connection Check the proxy and firewall ERR_CONNECTION_REFUSED The war file that I use locally is identical to the one I use on the Ubuntu VPS.
It appears that the benchmark code is trying to launch a process similar to the java debugger (presumably so that it can obtain the information it needs). Startup/Connection tab for a remote configuration This tab shows command-line options for starting the server JVM in the run and debug modes. It seems like the TC plugin login and poll threads use the proxy, generating logs like these: 16:08:41,993 DEBUG pool-2-thread-1 Open connection to :8080 ConnectException "Connection refused" This is my IntelliJ configuration: I also tried using -Xdebug but it still didn't work. It could be that you need to wait for your code to stop compiling before you attached the debugger. Hence, please run the debugger first and ensure that the chosen port is opened. Intellij unable to open debugger port connection refused Item.