connects to server but fails to make a connection test

[IMIEEET]

Version number
1.2.3

Describe the bug
using --wgconf i specify my own .conf config, after about 30 seconds it gives me this error time=2024-07-04T20:22:26.881+03:30 level=ERROR msg="connection test failed" error="Get \"http://1.1.1.1:80/\": connect tcp 1.1.1.1:80: operation timed out" time=2024-07-04T20:22:26.881+03:30 level=ERROR msg="connection test failed" error="Get \"http://1.1.1.1:80/\": connect tcp 1.1.1.1:80: operation timed out"
so from the log i think its checking the connection first before giving me proxy, but from the tun local ip of my config after a few seconds that i run the warp-plus i can ping my client, meaning that it successfully connected to my wireguard server but cant make a correct test for that.

To Reproduce
Steps to reproduce the behavior:
setup a wireguard server and a client config file, connect to it via warp-plus --wgconf client.conf, just before it cant make a connection test ping the local ip of user, for example if wireguard server is listening on 10.8.0.1 ping the client with 10.8.0.2 on server, if you see a correct ping it means you have a connection to client but warp-plus cant make a connection test and exits

Expected behavior
in case of successful connection to wireguard server, it should bind to proxy after that
idea: make so it binds the proxy anyway if test fails but print that error to notify user, just like how connection tests works in v2ray/xray clients

Desktop (please complete the following information):

• OS: both server and client ubuntu 22 server