keivan-sf / v2ray-switcher Goto Github PK

Testing servers shouldn't only be about having connection. We should consider speed, along side the status of the IP address (How much it's restricted)

Socks5 ports should be configurable by the user and not hard coded
Maybe we need a config file for all the configurations

We need utilities to log the error and exit the program gracefully

We should use vercel/pkg for our releases so they would be ready to use

The readme docs are outdated

The program stops here, the port is available and the connection is ok but testing does not continue

How to reproduce: Add multiple subscription urls

There should be a guide for development and building from source

If we execute pnpm release -v [someversion] and get an executable and run it, it will not function like pnpm start .
in both examples I'm using the config below:

{
  "subscription_urls": ["my_sub_url"],
  "logLevel": 1
}

(my_sub_uri will be an actual subscription url)

Output with pnpm start:

Updating subscriptions...

The process is started, connect to port 4080

Tester succeeded on port 4078
Tester succeeded on port 4077
Tester succeeded on port 4079
Main port is now available
Tester failed on port 4075
Tester failed on port 4076
Tester succeeded on port 4075
Tester succeeded on port 4076

And the socks proxy on 4080 port is alright

But when I release and use the executable with the same config:

Updating subscriptions...

The process is started, connect to port 4080

Tester failed on port 4075
Warning: Failed to start: main/commands: failed to create server > proxy/vmess/outbound: failed to parse server spec > proxy/vmess: failed to parse ID > invalid UUID: a-b-c-d
Tester failed on port 4076
Warning: Failed to start: main/commands: failed to create server > proxy/vmess/outbound: failed to parse server spec > proxy/vmess: failed to parse ID > invalid UUID: a-b-c-d

Tester failed on port 4076
Tester failed on port 4077
Tester failed on port 4078
Tester failed on port 4079
Tester failed on port 4075
Tester failed on port 4075
Tester failed on port 4078
Tester failed on port 4079

And the socks proxy on 4080 is not working

This is the reason we can't have a release of the latest version

We need a logging level for debugging, to show v2ray commands, uris and etc.