Tor

[tet-vivi]

@site_master можно например использовать пакет для node.js port-to-kill вместо стандартного.

[GaG]

@site_master

There is an error in source of this module. There is easy workarround, but it will be better if OP would fix that error so it works as intended. As a result of that error in source code this module works in 90% of cases, and rest 10% is what causing trouble and cause that error you mentioned.

The error is in create new tor connection JS file. Very first line chooses port number between 1 and 999, and later in the script adds 9000 so port number is between 9000 and 9999. But unfortunately OP didnt solve it good in later code, so ports from 9000 to 9100 are not making good connection and cause that error afterwards, when they need to close. Cause of that error is because those first 100 numbers for ports are false and they are actually opened on wrong port numbers.

So easy workaround would be to replace that formula (first line of code) with code that produces 3 digit numbers - 100-999, and avoid first 100 ports (9000-9100) which are not opening correctly due to error in later code.

It would be best if OP would make all necessary corrections in the code so all ports work as intended. But in meantime you can apply workaround by replacing that first line of code.

[GaG]

@Katant

TOR_PORT = Math.floor(Math.random() * 999);

and

native("filesystem", "writefile", JSON.stringify({path: RANDOM_FILE,value: "chcp 65001\n" + (("".length>0) ? ("cd " + "" + "\n") : "" ) + ("cd custom/Tor/files/Tor\ntor.exe -f torrc -SocksPort 9" + TOR_PORT + " -ControlPort 8" + TOR_PORT + " -DataDirectory %TEMP%/torf" + TOR_PORT + TOR_CUSTOM),base64:false,append:false}))

do not match.

9" + TOR_PORT + " is loosing leading 0 and opens wrong port for ports 9000-9100

[danko]

У кого ошибка формата "..PROCESS_STANDART_OUTPUT.split.." используйте npm модуль port-to-kill как помог @tet-vivi выше.

const portToKill = require('port-to-kill');
const port = [[TOR_PORT]];
portToKill(port)

[tet-vivi]

вот несколько действий для вырубания процесса(тор) по порту без node.js
сгенерированный в модуль не работает

скопировать и вставить в бас. почти не тестил.

обновлено

spoiler

[Katant]

@GaG Implemented your fix. You can always open pull request if you want (or issue, I don't check this forum everyday)

[ShoSupport]

@Fox извиняюсь за беспокоиство) не подскажешь модуль акктуален на текущей версии BAS?

[tet-vivi]

@vovaknyazev217 said in Tor:

@Fox извиняюсь за беспокоиство) не подскажешь модуль акктуален на текущей версии BAS?

на текущей версии BAS модуль работает.
tor прокси - не актуальны.

[Fox]

@vovaknyazev217 said in Tor:

@Fox извиняюсь за беспокоиство) не подскажешь модуль акктуален на текущей версии BAS?

А причём здесь я?

[Ryder]

After around 1k success executions the script starts giving failed to get proxy ip. Anyone else facing this issue? If yes did you find a fix for it? If no please help me out to figure a way..

[Alex84]

This post is deleted!

[Alex84]

This post is deleted!

[booldozer]

@Katant Это просто велеколепно. Мужик, спасибо тебе, у меня был целый шаблон написан для этой процедуры. А тут просто модулем. Долгих лет жизни.

[Abby]

I "Start Tor" and the following error occurs, someone help me. Thanks.

[badkat]

у меня часто вылазит ошибка "tor.exe - application error", особенно в многопотоке. Из-за чего такое может быть?

[g-shock]

This post is deleted!

[battleground]

http тунель? или socks

[Katant]

@battleground просто socks5 прокси

[g-shock]

This post is deleted!

[Katant]

Выпустил обновление 1.9, как всегда обновление Tor. Но ещё замена netcat на ncat (не будет антивирус ругаться и в целом меньше проблем). А так же замена ошибки ...PROCESS_STANDART_OUTPUT.split... на читаемую.