search

LonamiWebs / Telethon

Pure Python 3 MTProto API Telegram client library, for bots too!
https://docs.telethon.dev
MIT License
9.95k stars 1.4k forks source link

account banned #824

Closed izzzzzi closed 6 years ago

izzzzzi commented 6 years ago

When using the library, the account is immediately banished How to avoid this?

(edit from @Lonami)

For everyone still coming here, see my comment:

Even official applications have these problems, not only libraries. Bans probably depend on a lot of factors, such as country, IP, use of the application, maybe even some random bans to accounts so people who care recover them and spambots won't bother with emails so those are gone, etc. For completeness sake:

Emails: login@stel.com, recover@telegram.org.

If those don't work, abuse@telegram.org, https://telegram.org/support and DM to https://twitter.com/smstelegram may be worth trying.

izzzzzi commented 6 years ago

Right now I'll try without Tkinter

Lonami commented 6 years ago

Oh, did you call self.client.connect?

izzzzzi commented 6 years ago

Yes 

class Telegram():
    def __init__(self,proxy,chat):
        if chat != '':
            self.chat = chat.split(',')
            if len(chat) < 1:
                self.chat = [chat]
        if proxy != '':
            proxy = proxy.split(':')
            self.proxy = (socks.HTTP, proxy[0], int(proxy[1]), True, proxy[2], proxy[3])
        self.client = TelegramClient('session.session', api_id, api_hash,proxy=self.proxy)
        self.client.connect()
        if not self.client.is_user_authorized():
            self.client.start()
            #self.client.disconnect()
            #number = app.textBox("Ручная регистрация", "Введите номер телефона", parent=None)
            #self.client.send_code_request(number)
            #code = app.textBox("Ручная регистрация", "Введите код", parent=None)
            #me = self.client.sign_up(code, 'parser', 'pars')
        if self.client.is_user_authorized():
            Log('Авторизовались')
            try:
                os.remove("db.sqlite")
            except Exception as e:
                print(str(e))
Lonami commented 6 years ago

@GoldenEagle66 okay the request needs to be moved, I couldn't test this before.

izzzzzi commented 6 years ago

@Lonami did not quite understand what you are talking about.

izzzzzi commented 6 years ago

@Lonami can I download updates?

izzzzzi commented 6 years ago

@Lonami v0.19.1.2

Please enter your phone: +77082269391
Please enter the code you received: 85690
By signing up you agree to Telegram's TOS:
By signing up for Telegram, you agree not to:

- Use our service to send spam or scam users.
- Promote violence on publicly viewable Telegram bots, groups or channels.
- Post pornographic content on publicly viewable Telegram bots, groups or channels.

We reserve the right to update these Terms of Service later.
Traceback (most recent call last):
  File "H:\Soft PC\JetBrains\PyCharm 2017.2\helpers\pydev\pydevd.py", line 1596, in <module>
    globals = debugger.run(setup['file'], None, None, is_module)
  File "H:\Soft PC\JetBrains\PyCharm 2017.2\helpers\pydev\pydevd.py", line 1023, in run
    pydev_imports.execfile(file, globals, locals)  # execute the script
  File "H:\Soft PC\JetBrains\PyCharm 2017.2\helpers\pydev\_pydev_imps\_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "C:/Users/Захар/PycharmProjects/testtelegram/test.py", line 13, in <module>
    client.start()
  File "C:\Python36-32\lib\site-packages\telethon\telegram_client.py", line 351, in start
    me = self.sign_up(code_callback(), first_name, last_name)
  File "C:\Python36-32\lib\site-packages\telethon\telegram_client.py", line 509, in sign_up
    self(AcceptTermsOfServiceRequest(self._tos.id))
  File "C:\Python36-32\lib\site-packages\telethon\telegram_bare_client.py", line 486, in __call__
    result = self._invoke(call_receive, request, ordered=ordered)
  File "C:\Python36-32\lib\site-packages\telethon\telegram_bare_client.py", line 583, in _invoke
    raise next(x.rpc_error for x in requests if x.rpc_error)
telethon.errors.rpc_error_list.AuthKeyUnregisteredError: The key is not registered in the system

Process finished with exit code 1
Lonami commented 6 years ago

I haven't published a fix yet. More things are broken right now.

izzzzzi commented 6 years ago

my code that causes an error above

from telethon import TelegramClient
import socks

api_id = 13682
#api_id = 253798
api_hash = 'de37bcf00f4688de900510f4f87384bb'
#api_hash = 'd806c9ed3eb74a233d58cb4a072a68f0'

proxy = (socks.HTTP, "185.91.172.88", int("22862"), True, "0jUpbFCSro", "2PODoxlIcj")
client = TelegramClient('session.session', api_id, api_hash, proxy=proxy)
client.connect()
if not client.is_user_authorized():
    client.start()
    if client.is_user_authorized():
        print("good")
else:
    print("good")
izzzzzi commented 6 years ago

@Lonami tried different versions of the error one

Lonami commented 6 years ago

I'm telling you to first wait.

izzzzzi commented 6 years ago

@Lonami well expect, ready to test

Lonami commented 6 years ago

Alright. v0.19.1.3 is out, upgrade again and try…

izzzzzi commented 6 years ago

@Lonami image

Lonami commented 6 years ago

@GoldenEagle66 --no-cache

izzzzzi commented 6 years ago

excellent! all earned, registration - exactly, right now I'll check the rest

izzzzzi commented 6 years ago

@Lonami there is also no registration, but after the session is created and the second session is deleted, the session is deleted

I can register a session and throw you off

izzzzzi commented 6 years ago

@Lonami

debug at registration :
[Thread-1/INFO, 2018-06-03 18:58:21,567] telethon.telegram_bare_client:202: Connecting to 149.154.167.51:443...
[Thread-1/INFO, 2018-06-03 18:58:21,707] telethon.telegram_bare_client:208: Connection success!
[Thread-1/DEBUG, 2018-06-03 18:58:21,707] telethon.telegram_bare_client:481: Invoking GetStateRequest
[Thread-1/INFO, 2018-06-03 18:58:21,707] telethon.telegram_bare_client:517: Need to generate new auth key before invoking
[Thread-1/INFO, 2018-06-03 18:58:22,789] telethon.telegram_bare_client:523: Initializing a new connection while invoking
[Thread-1/DEBUG, 2018-06-03 18:58:22,790] telethon.network.mtproto_sender:112: Sending requests with IDs: InvokeWithLayerRequest: 6562888281183930412
[Thread-1/DEBUG, 2018-06-03 18:58:22,874] telethon.network.mtproto_sender:248: Processing BadServerSalt result
[Thread-1/DEBUG, 2018-06-03 18:58:22,889] telethon.network.mtproto_sender:112: Sending requests with IDs: InvokeWithLayerRequest: 6562888281579142584
[Thread-1/DEBUG, 2018-06-03 18:58:22,987] telethon.network.mtproto_sender:233: Processing container result
[Thread-1/DEBUG, 2018-06-03 18:58:22,987] telethon.network.mtproto_sender:248: Processing NewSessionCreated result
[Thread-1/DEBUG, 2018-06-03 18:58:22,987] telethon.network.mtproto_sender:248: Processing MsgsAck result
[Thread-1/DEBUG, 2018-06-03 18:58:23,018] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[Thread-1/DEBUG, 2018-06-03 18:58:23,018] telethon.network.mtproto_sender:508: Received response for request with ID 6562888281579142584
[Thread-1/DEBUG, 2018-06-03 18:58:23,026] telethon.network.mtproto_sender:531: Confirmed InvokeWithLayerRequest through error The key is not registered in the system
[Thread-1/DEBUG, 2018-06-03 18:58:25,076] telethon.telegram_bare_client:481: Invoking SendCodeRequest
[Thread-1/DEBUG, 2018-06-03 18:58:25,076] telethon.network.mtproto_sender:112: Sending requests with IDs: SendCodeRequest: 6562888291213113688
[Thread-1/DEBUG, 2018-06-03 18:58:25,179] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[Thread-1/DEBUG, 2018-06-03 18:58:25,179] telethon.network.mtproto_sender:508: Received response for request with ID 6562888291213113688
[Thread-1/DEBUG, 2018-06-03 18:58:25,193] telethon.network.mtproto_sender:531: Confirmed SendCodeRequest through error The source IP address is associated with DC 5
[Thread-1/DEBUG, 2018-06-03 18:58:25,193] telethon.telegram_bare_client:481: Invoking GetConfigRequest
[Thread-1/DEBUG, 2018-06-03 18:58:25,193] telethon.network.mtproto_sender:112: Sending requests with IDs: GetConfigRequest: 6562888291681139848
[Thread-1/DEBUG, 2018-06-03 18:58:25,360] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[Thread-1/DEBUG, 2018-06-03 18:58:25,360] telethon.network.mtproto_sender:508: Received response for request with ID 6562888291681139848
[Thread-1/DEBUG, 2018-06-03 18:58:25,362] telethon.network.mtproto_sender:547: Confirmed GetConfigRequest through normal result Config
[Thread-1/INFO, 2018-06-03 18:58:25,362] telethon.telegram_bare_client:308: Reconnecting to new data center DcOption(id=5, ip_address='91.108.56.104', port=443, ipv6=False, media_only=False, tcpo_only=False, cdn=False, static=False, secret=None)
[Thread-1/INFO, 2018-06-03 18:58:25,382] telethon.telegram_bare_client:267: Disconnecting...
[Thread-1/DEBUG, 2018-06-03 18:58:25,382] telethon.telegram_bare_client:270: Stopping all workers...
[Thread-1/DEBUG, 2018-06-03 18:58:25,382] telethon.telegram_bare_client:275: Disconnecting the socket...
[Thread-1/INFO, 2018-06-03 18:58:25,382] telethon.network.mtproto_sender:80: Disconnecting MtProtoSender...
[Thread-1/INFO, 2018-06-03 18:58:25,397] telethon.telegram_bare_client:202: Connecting to 91.108.56.104:443...
[Thread-1/INFO, 2018-06-03 18:58:25,670] telethon.telegram_bare_client:208: Connection success!
[Thread-1/INFO, 2018-06-03 18:58:25,686] telethon.telegram_bare_client:517: Need to generate new auth key before invoking
[Thread-1/INFO, 2018-06-03 18:58:27,408] telethon.telegram_bare_client:523: Initializing a new connection while invoking
[Thread-1/DEBUG, 2018-06-03 18:58:27,408] telethon.network.mtproto_sender:112: Sending requests with IDs: InvokeWithLayerRequest: 6562888301128166344
[Thread-1/DEBUG, 2018-06-03 18:58:27,656] telethon.network.mtproto_sender:248: Processing BadServerSalt result
[Thread-1/DEBUG, 2018-06-03 18:58:27,672] telethon.network.mtproto_sender:112: Sending requests with IDs: InvokeWithLayerRequest: 6562888302185777812
[Thread-1/DEBUG, 2018-06-03 18:58:27,920] telethon.network.mtproto_sender:233: Processing container result
[Thread-1/DEBUG, 2018-06-03 18:58:27,920] telethon.network.mtproto_sender:248: Processing NewSessionCreated result
[Thread-1/DEBUG, 2018-06-03 18:58:27,920] telethon.network.mtproto_sender:248: Processing MsgsAck result
[Thread-1/DEBUG, 2018-06-03 18:58:27,951] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[Thread-1/DEBUG, 2018-06-03 18:58:27,951] telethon.network.mtproto_sender:508: Received response for request with ID 6562888302185777812
[Thread-1/DEBUG, 2018-06-03 18:58:27,951] telethon.network.mtproto_sender:547: Confirmed InvokeWithLayerRequest through normal result SentCode
[Thread-1/DEBUG, 2018-06-03 18:58:27,951] telethon.telegram_bare_client:481: Invoking ResendCodeRequest
[Thread-1/DEBUG, 2018-06-03 18:58:27,951] telethon.network.mtproto_sender:112: Sending requests with IDs: ResendCodeRequest: 6562888303300996928
[Thread-1/DEBUG, 2018-06-03 18:58:28,207] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[Thread-1/DEBUG, 2018-06-03 18:58:28,207] telethon.network.mtproto_sender:508: Received response for request with ID 6562888303300996928
[Thread-1/DEBUG, 2018-06-03 18:58:28,208] telethon.network.mtproto_sender:547: Confirmed ResendCodeRequest through normal result SentCode
By signing up for Telegram, you agree not to:

- Use our service to send spam or scam users.
- Promote violence on publicly viewable Telegram bots, groups or channels.
- Post pornographic content on publicly viewable Telegram bots, groups or channels.

We reserve the right to update these Terms of Service later.
[Thread-1/DEBUG, 2018-06-03 18:59:59,969] telethon.telegram_bare_client:481: Invoking SignUpRequest
[Thread-1/DEBUG, 2018-06-03 18:59:59,970] telethon.network.mtproto_sender:112: Sending requests with IDs: SignUpRequest: 6562888698515059348
[Thread-1/DEBUG, 2018-06-03 19:00:00,431] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[Thread-1/DEBUG, 2018-06-03 19:00:00,431] telethon.network.mtproto_sender:508: Received response for request with ID 6562888698515059348
[Thread-1/DEBUG, 2018-06-03 19:00:00,431] telethon.network.mtproto_sender:547: Confirmed SignUpRequest through normal result Authorization
[Thread-1/DEBUG, 2018-06-03 19:00:00,431] telethon.telegram_bare_client:481: Invoking AcceptTermsOfServiceRequest
[Thread-1/DEBUG, 2018-06-03 19:00:00,432] telethon.network.mtproto_sender:112: Sending requests with IDs: AcceptTermsOfServiceRequest: 6562888700658133028
[Thread-1/DEBUG, 2018-06-03 19:00:00,674] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[Thread-1/DEBUG, 2018-06-03 19:00:00,674] telethon.network.mtproto_sender:508: Received response for request with ID 6562888700658133028
[Thread-1/DEBUG, 2018-06-03 19:00:00,675] telethon.network.mtproto_sender:547: Confirmed AcceptTermsOfServiceRequest through normal result bool
[ReadThread/INFO, 2018-06-03 19:00:00,675] telethon.telegram_bare_client:679: Starting to wait for items from the network
[Thread-1/DEBUG, 2018-06-03 19:00:00,676] telethon.telegram_bare_client:481: Invoking UpdateProfileRequest
[ReadThread/DEBUG, 2018-06-03 19:00:00,676] telethon.network.mtproto_sender:112: Sending requests with IDs: PingRequest: 6562888701634189128
[Thread-1/DEBUG, 2018-06-03 19:00:00,677] telethon.network.mtproto_sender:112: Sending requests with IDs: UpdateProfileRequest: 6562888701638188836
[ReadThread/DEBUG, 2018-06-03 19:00:00,680] telethon.telegram_bare_client:695: Receiving items from the network...
[ReadThread/DEBUG, 2018-06-03 19:00:00,909] telethon.network.mtproto_sender:248: Processing Pong result
[ReadThread/DEBUG, 2018-06-03 19:00:00,909] telethon.network.mtproto_sender:373: Confirmed PingRequest through pong
[ReadThread/DEBUG, 2018-06-03 19:00:00,910] telethon.telegram_bare_client:695: Receiving items from the network...
[ReadThread/DEBUG, 2018-06-03 19:00:00,947] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[ReadThread/DEBUG, 2018-06-03 19:00:00,947] telethon.network.mtproto_sender:508: Received response for request with ID 6562888701638188836
[ReadThread/DEBUG, 2018-06-03 19:00:00,947] telethon.network.mtproto_sender:547: Confirmed UpdateProfileRequest through normal result User
[ReadThread/DEBUG, 2018-06-03 19:00:00,948] telethon.telegram_bare_client:695: Receiving items from the network...
[Thread-1/DEBUG, 2018-06-03 19:00:01,035] telethon.telegram_bare_client:481: Invoking GetUsersRequest
[Thread-1/DEBUG, 2018-06-03 19:00:01,035] telethon.network.mtproto_sender:112: Sending requests with IDs: GetUsersRequest: 6562888703365237356
[ReadThread/DEBUG, 2018-06-03 19:00:01,319] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[ReadThread/DEBUG, 2018-06-03 19:00:01,319] telethon.network.mtproto_sender:508: Received response for request with ID 6562888703365237356
[ReadThread/DEBUG, 2018-06-03 19:00:01,339] telethon.network.mtproto_sender:547: Confirmed GetUsersRequest through normal result list
[ReadThread/DEBUG, 2018-06-03 19:00:01,339] telethon.telegram_bare_client:695: Receiving items from the network...
[Thread-1/DEBUG, 2018-06-03 19:00:01,340] telethon.telegram_bare_client:481: Invoking UpdateUsernameRequest
[Thread-1/DEBUG, 2018-06-03 19:00:01,340] telethon.network.mtproto_sender:112: Sending requests with IDs: UpdateUsernameRequest: 6562888704585308196
[ReadThread/DEBUG, 2018-06-03 19:00:01,771] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[ReadThread/DEBUG, 2018-06-03 19:00:01,771] telethon.network.mtproto_sender:508: Received response for request with ID 6562888704585308196
[ReadThread/DEBUG, 2018-06-03 19:00:01,771] telethon.network.mtproto_sender:547: Confirmed UpdateUsernameRequest through normal result User
[ReadThread/DEBUG, 2018-06-03 19:00:01,772] telethon.telegram_bare_client:695: Receiving items from the network...
[ReadThread/DEBUG, 2018-06-03 19:00:01,774] telethon.network.mtproto_sender:248: Processing UpdateShort result
[ReadThread/DEBUG, 2018-06-03 19:00:01,774] telethon.telegram_bare_client:695: Receiving items from the network...
[Thread-1/INFO, 2018-06-03 19:00:04,898] telethon.telegram_bare_client:267: Disconnecting...
[Thread-1/DEBUG, 2018-06-03 19:00:04,898] telethon.telegram_bare_client:270: Stopping all workers...
[Thread-1/DEBUG, 2018-06-03 19:00:04,898] telethon.telegram_bare_client:275: Disconnecting the socket...
[Thread-1/INFO, 2018-06-03 19:00:04,898] telethon.network.mtproto_sender:80: Disconnecting MtProtoSender...
[ReadThread/INFO, 2018-06-03 19:00:04,899] telethon.telegram_bare_client:720: Connection closed by the user, not reading anymore
debugg at work :
[Thread-1/INFO, 2018-06-03 19:04:08,361] telethon.telegram_bare_client:202: Connecting to 91.108.56.104:443...
[Thread-1/INFO, 2018-06-03 19:04:08,659] telethon.telegram_bare_client:208: Connection success!
[Thread-1/DEBUG, 2018-06-03 19:04:08,659] telethon.telegram_bare_client:481: Invoking GetStateRequest
[Thread-1/INFO, 2018-06-03 19:04:08,659] telethon.telegram_bare_client:523: Initializing a new connection while invoking
[Thread-1/DEBUG, 2018-06-03 19:04:08,659] telethon.network.mtproto_sender:112: Sending requests with IDs: InvokeWithLayerRequest: 6562889766715456092
[Thread-1/DEBUG, 2018-06-03 19:04:08,887] telethon.network.mtproto_sender:248: Processing BadServerSalt result
[Thread-1/DEBUG, 2018-06-03 19:04:08,887] telethon.network.mtproto_sender:112: Sending requests with IDs: InvokeWithLayerRequest: 6562889767629078948
[Thread-1/DEBUG, 2018-06-03 19:04:09,128] telethon.network.mtproto_sender:233: Processing container result
[Thread-1/DEBUG, 2018-06-03 19:04:09,128] telethon.network.mtproto_sender:248: Processing NewSessionCreated result
[Thread-1/DEBUG, 2018-06-03 19:04:09,128] telethon.network.mtproto_sender:248: Processing MsgsAck result
[Thread-1/DEBUG, 2018-06-03 19:04:09,159] telethon.network.mtproto_sender:229: Processing Remote Procedure Call result
[Thread-1/DEBUG, 2018-06-03 19:04:09,159] telethon.network.mtproto_sender:508: Received response for request with ID 6562889767629078948
[Thread-1/DEBUG, 2018-06-03 19:04:09,165] telethon.network.mtproto_sender:531: Confirmed InvokeWithLayerRequest through error The user has been deleted/deactivated
[Thread-1/INFO, 2018-06-03 19:04:09,166] telethon.telegram_bare_client:267: Disconnecting...
[Thread-1/DEBUG, 2018-06-03 19:04:09,166] telethon.telegram_bare_client:270: Stopping all workers...
[Thread-1/DEBUG, 2018-06-03 19:04:09,166] telethon.telegram_bare_client:275: Disconnecting the socket...
[Thread-1/INFO, 2018-06-03 19:04:09,166] telethon.network.mtproto_sender:80: Disconnecting MtProtoSender...
JMIdeaMaker commented 6 years ago

Do you mean there is no ban at registration? And why are you deleting sessions?

izzzzzi commented 6 years ago

@mike-johnson-jr seems to have solved the problem, the problem was in api_id

izzzzzi commented 6 years ago

need good apps image

JMIdeaMaker commented 6 years ago

So 0.19.1.3 is confirmed not to cause bans now?

izzzzzi commented 6 years ago

@mike-johnson-jr no unconfirmed

JMIdeaMaker commented 6 years ago

0.19.1.3 did not cause a ban for me

unconditional commented 6 years ago

Wow, this actually is quite a known issue. I wish I saw this thread two days ago, when I got my number banned.

So ATM can we consider 0.19.1.3 stable in the sense of bans? Please share your results. I will do as soon as my login timeout expires.

unconditional commented 6 years ago

Btw, just FYI, I didn't have any issues on my main long-used number whatsoever. On the other hand I got instabanned upon connecting via telethon on a new virtual number which was never used for communication. Thus I think, the use time might also be the ban criteria - if the number was just registered and you immediately use API on it, their algos might consider that the spamming software usage pattern.

Lonami commented 6 years ago

By the way, everyone affected can try sending a message to recover@telegram.org to get the phone numbers back.

unconditional commented 6 years ago

Thanks for the info. Did you have any success with it?

What I tried was writing to abuse@telegram.org, https://telegram.org/support and DM to https://twitter.com/smstelegram And guess what? Right, nothing.

mrzxy commented 6 years ago

I am also

Lonami commented 6 years ago

Another email you could try: login@stel.com. It's the address you get after tapping "Help" on DrKLO's Android client. For example:

I'm trying to use my mobile phone number: phone But Telegram says it's banned. Please help.

App version: 4.8.9 (12617) OS version: SDK version number Device Name: model Locale: en

mike0sv commented 6 years ago

Just got banned on 0.19.1.4 after registering via official app on real number =/ So @unconditional version might be the case (I also have my main long-used account connected without any problems)

overjoy commented 6 years ago

Same to me. Got banned 3 hours after upgrading to master branch 

In [4]: telethon.__version__
Out[4]: '0.19.1'

I needed upgrade because of DraftMessageEmpty problem

deeepv commented 6 years ago

import telethon telethon.__version__ '0.19.1.6' Same to me. Got banned i use proxy,ipv4,and loggin,nothing todo,then banned.what haapend to me? by the way,i use interactive_telegram_client.py from example

Lonami commented 6 years ago

I have no idea what phones or activities everyone getting banned is doing but I have never had this issue. While I really doubt high versions are an issue, it's very improbable. Everyone having this issue can:

git clone https://github.com/LonamiWebs/Telethon
cd Telethon
git checkout v0.17  # or any other version

And then just edit telethon/tl/custom/draft.py with this change. Use whatever version worked for you with the draft fix.

overjoy commented 6 years ago

We're trying to get big tiddy gf obviously. Will check your advice, thanks

THROFHR commented 6 years ago

I used the 0.19.1.4 version, I tried to register for 1000+, I switched proxy every time I registered, used 14 api_id, but I was gradually sealed, I can not find the reason。

overjoy commented 6 years ago

I wrote to recover@telegram.org, they replied after two days and my numbers were unbanned. Seems like ban was by mistake. Now I'm on 0.19.1.6, all works good.

ab4242 commented 6 years ago

I just started using Telethon a few days ago, along with telegram-export and I cannot get a full extraction to run once without getting banned. Tried several versions from 0.17 to current all with the same results. Burning through $1.99 Hushed app phone numbers right now. All I need is my list of users from two channels I am an admin of.

Lonami commented 6 years ago

Pretty sure if you use an account that has existed for some weeks and you don't abuse it, it will be fine… There are even success stories of accounts being recovered like @overjoy said, in the worst case of getting your main account banned (which has never happened to me). Like I stated the version is very unlikely. It's probably how new the account is, maybe the location, and what you use it for. Perhaps even Telegram has a blacklist of proxies or IPs to disallow.

EricKotato commented 6 years ago

Yesterday I got banned too. Because I'm from Russia, I need to use proxy, so I used Tor as proxy, because I got tired of blocked or dead proxies. Wrote script to upload screenshots to group chat, and got banned on one of launches. Wrote to both recover@telegram.org and login@stel.com. First one responded in ~5 hours, saying that issue was solved, and my account was unbanned. For some reason they didn't tell me about ban reasons. Used Telethon 0.18.3 with, guess I should update.

yangtao097 commented 6 years ago

I have tried to sign up telegram account with telethon(0.18.3 ->0.19.16) by proxy because the Chinese outer internet access bans for many times using inland phone number in the last and current months. But the result is DELETED ACCOUNT every single time, which get me puzzled and annoied enough to write to recover@telegram.org for the reason. They confidently replied the factor is that the number I used is of the purpose to spam stranger.

Hehe, in their logics, whichever person I contact to is not a stranger for a new one registered, and in their Database Server, the only survivor is the first one registered, for the reason that to the second what he do is only spam to the first member and should be banned logically at any time when he send message to any one. So he is isolated with wasting time registering the account in vain.

My question is after I registered with telethon, please tell me which behavior is the right action to use the new account, and when I want to send information normally to an account I'm familiar how can I send a single message that will not be punished to be banned by telethon?

Lonami commented 6 years ago

I believe you should just register applications through official clients, and wait for a bit before doing anything suspicious…

Jihante commented 6 years ago

I correctly understood that need to use api_id and api_hash from the official client (for example android)?

DiederickJacobs commented 6 years ago

Api seems to be quite useless now days - since all my accounts get instant banned. Doesn't matter what numbers i do use; USA/CHINA/RUSSIA - it doesn't affect the banrate at all..

Any help would be great.

Lonami commented 6 years ago

Api seems to be quite useless now days

Always sorry to hear, but bear in mind it's Api as you said and not library. My account still has never received a ban. Telegram Server is deciding these bans. Just email their address if you really are making a legit use of their API.

JMIdeaMaker commented 6 years ago

Using an earlier version may help you. It helped me. Try 0.18.3

DiederickJacobs commented 6 years ago

Hi. I was wondering, is it the recovery departement of telegram ( recover@telegram.org ) an official channel & official email? Since the way they respond, is literally like a twelve year old. There is not even a glance of professionality - their response on my emails are a big joke. Sorry if any of you do handle these emails, but step up your game and atleast be a bit polite and act like you really wanna help instead of being a big douche bag. Oh and the structure of sentences are terrible - sentences do end all of a sudden or there is a random ' , '.

So is it worth to email the recovery section, probably it is not. The employee literally told me that i was lazy since i didn't what (s)he told me to do, makes false conclusions based on thin air and basically acts like a big douche.

Btw @Lonami thanks for your help, though. You are heaven on earth if i do compare you with these telegram 'employees'.

Good luck with getting ur accounts back , everyone.

Jihante commented 6 years ago

Is this shit on clients of other languages?

fakkoweb commented 6 years ago

I used 1.2 and got banned yesterday for no reason, except downloading messages from a private channel I am in. Can it be because I logged in from both phone and server (which is not in my same location). Have been using Telethon for two weeks (my account is 2 years old of personal usage). No idea what happened, no answer so far from support.

fakkoweb commented 6 years ago

Answered from recover@telegram.org, ban removed but no explanation