fake tls

[ZarinNegah]

hi
good time
please add fake-tls to your nodejs script

https://github.com/HirbodBehnam/MTProtoProxyInstaller
and
https://github.com/seriyps/mtproto_proxy

Also like the above scripts , is it possible to build an automatic installer and config port and secret or secrets and tag?

[MTProto]

Hi, the support was added. Some APIs have changed. I will try to add an automatic installer in future in other repositories. But currently this repository is aimed at only creating a module. This module is for programmers only.

[ZarinNegah]

Hello
Thanks for the update
I'm waiting for another repository for automatic installation

[MTProto]

I have added a fast set-up part. Could you please test it and tell me your opinion?

[ZarinNegah]

Hello
Yes,thanks you
Installed and enabled
But the installation needs to be more automated
And also select more and multi secret
You can use the example below to build more
https://git.io/fjo3u

[MTProto]

It supports multi secret. Just separate secrets with space.

[MTProto]

It does not need root access nor it requires to install any package. May be setting firewall requires root password.

[ZarinNegah]

Thankful
For you too, the number of connections increases, ping increases

[MTProto]

I have not tested it under severe conditions. Currently it uses inter-process communication to create reports of each process. num_cpus should always be less than or equal to your cpu cores. Please tell me your experience with this proxy. Also remember that you can access the report through web. Full report is enabled by default and you can access it by log1.txt in the current directory.

[ZarinNegah]

After a few minutes it will be disconnected and you will need to resubmit the following command to activate it
bash ./fastsetup.sh

[ZarinNegah]

ping increases

[MTProto]

After it terminated, just check the log file by typing "tail log.txt".

[MTProto]

عزیز اگر ایرادی داشت بهم بگو اصلاح کنم. چون برای من مشکلی پیش نمیاد. فقط یه مساله. اگر سرعت کامپیوترت خیلی کم باشه، سیستم عامل به برنامه سیگنال
SIGXCPU
میفرسته که البته این سیگنال نود رو میبنده چون من هندلش نکردم. فکر کنم ایراد از اون باشه که برنامه بسته میشه. این ایراد را خیلی راحت میتونم برطرف کنم. اگر بتونی فایل لاگ رو ببینی و بهم بگی چه خبره توش میتونم راحتتر عیب احتمالی کد رو تشخیص بدم.
در مورد زیاد شدن پینگ هم برای من مشکلی نداره. باید روش کار کنم ببینم دلیل چیه که برای شما پینگ زیاد میشه. این کد چند هسته ای رو قدیم دادم به یکی اونم همین ایراد رو گفت. شاید کلا چند هسته ای رو حذف کنم.

[ZarinNegah]

نمیدونستم ایرانی هستین
بی زحمت به تلگرامم پیام بدید
@MTProtoConfiger

[gost-serb]

Hi. Thanks for cool proxy!
For some reason, I'm facing error while trying to connect to my proxy via fake-tls.

Here is error message:

 Client left: {
  id: 262,
  bytesWritten: 0,
  bytesRead: 132,
  error: 'Error: Assertion failed: No matching secret\n' +
    '    at assertit (/mtproxy/node_modules/mtprotoproxy/index.js:110:9)\n' +
    '    at handleClient (/mtproxy/node_modules/mtprotoproxy/index.js:655:2)\n' +
    '    at runMicrotasks (<anonymous>)\n' +
    '    at processTicksAndRejections (internal/process/task_queues.js:93:5)'
} on core  2

I event tried with default secret: ee00000000000000000000000000000000 in server config, and ee00000000000000000000000000000000676f6f676c652e636f6d on client side. At the same dd secret works fine.

Any ideas?

[MTProto]

Everything seems OK. Have you updated your telegram client? Please install the most recent version of Telegram. Then double check the secret entered to your client. Remember there are 32 consecutive ('0')'s. Please note that this is not an error message, In fact this is the reason for disconnecting client. It's meaning is simple. A client is trying to connect, but it's secret does not match with any of the secrets provided to the proxy. In fact from the proxy point of view, the user was not legitimate to use the proxy.
If you solved the problem, please let us know the reason, even if you made the mistake.