Search the Community
Showing results for tags 'error 110'.
Found 2 results
-
Hello! I have a Win10 PC, with qBittorrent. I have been able to port forward successfully! However, I find that whenever I close qBittorent, and then open it back up later, the port is no longer open and says "Connection timed out (110)", so in the client I'm actually unable to download/upload/connect to peers. I did some research and found the fix for this on these forums (temporarily). Pretty much, I have to open my client, go to the advanced settings, Change it from "Eddie" for the Network Interface to "Any Interface". Then, close the client, open the client back up and then again change from "Any Interface" back to "Eddie", and it works again! I have to do this every time I close my qbit client/turn of PC. I do also confirm that the port on AirVPN's Client Area matches the one in qBitorrent. Then it works again, I'm connected/uploading/downloading and AirVPN's client area confirms that the port is Open. I would just rather not have to go to these steps everytime I close qbit. Could it be that I need to bind to an IP address/(an option I see in qbittorrent) IP address changing depending on the server that I join that makes this happen? Now, I'm not super knowledgeable in this area but I'm constantly trying to learn. So I don't know what I don't know.. If there is any additional information needed that I need to share to troubleshoot, please let me know. And thank you in advance for any help and suggestions.
-
My ports used to work about 2 days ago, and all of a sudden, they have stopped working. I never get the red button/icon, but I do get the grey one - with Errors 110 and 111. I downloaded the Port Forwarding Tester program, and don't really know how to use it. I put in the port of the IP and Port that the AirVPN site generated, and clicked send to both UDP and TCP. UDP just says "sended" when I click send, but when I send to TCP, I get the error "No connection could be made because the target machine actively refused it...". I am doing this while connected to a server. I have tried reconnecting to different servers, turning off my firewall, and/or allowing all of the AirVPN programs into Firewall. I have also tried different ports.