Open artemysss11 opened 2 years ago
reasons for bad dms: bad tokens bad captchas bad proxies
it could be any of these, or a combination of a few or all.
I am using bright data paid proxies, i tried ISP, Datacenter they work but tokens get banned after a few messages
I tried residential and mobile and they dont work at all
as for captcha i am using capmonster
for token, i create them myself, i use specific ips from a specific country, then the proxies i used are from the same country as well
i dont know where is the problem...
probably captchas, they are being weird currently
What do you suggest, using anti-captcha ?
i don't think any of the providers are doing well
What do you suggest, using anti-captcha ?
Anti-Captcha is not doing well. Right now 1 out of 10 tries works. Low results.
How can we solve this ? any suggestions?
anti-captcha is working pretty bad right now. There was a hcaptcha update following which most services started returning very low quality solutions. The only supported captcha services are https://capmonster.cloud https://anti-captcha.com https://2captcha.com https://rucaptcha.com http://capcat.xyz (3rd party, pretty inexpensive can try but no guarantees)
none of my captchas are being solved with capmonster, probably my ip
what do you suggest for proxies since all my https proxies which ive tested and work don't work on dmdgo although they are parsed fine:
[ERROR ][22:24:07] » error while getting cookie error while getting response from cookies request Get "https://discord.com": tls: first record does not look like a TLS handshake [ERROR ][22:24:07] » error while OTcxNDY5MzQzNjAwODM2NjE5.GE-DSB.GIiNo_6sNBL3VTpFBOJ-HQZYmEEiEEcHkFjSWA was sending message in 1071244236348989534, response code: -1 [ERROR ][22:24:07] » error while getting cookie error while getting response from cookies request Get "https://discord.com": tls: first record does not look like a TLS handshake [ERROR ][22:24:07] » error while getting cookie error while getting response from cookies request Get "https://discord.com": tls: first record does not look like a TLS handshake
can you help me with what i am doing wrong ?
here is my config
direct_message_settings: individual_delay: 800 rate_limit_delay: 600 offset: 20000 max_dms_per_token: 0 skip_completed: true call: false remove_dead_tokens: true remove_completed_members: true stop_dead_tokens: true check_mutual: false friend_before_DM: false online_tokens: false receive_messages: false skip_failed: false block_after_dm: false close_dm_after_message: false
proxy_settings: proxy_from_file: true proxy_for_captcha: true use_proxy_for_gateway: true proxy_protocol: "http" timeout: 60
scraper_settings: online_scraper_delay: 3000 scrape_usernames: false scrape_avatars: false
captcha_settings: captcha_api_key: "CAPCHA_KEY" captcha_api: "capmonster.cloud" max_captcha_wait: 600 max_captcha_retry_dm: 0 max_captcha_retry_invite: 3
other_settings: disable_keep_alives: false
suspicion_avoidance: random_individual_delay: 100 random_rate_limit_delay: 100 random_delay_before_dm: 30 typing: false typing_variation: 250 typing_speed: 450 typing_base: 200
dm_on_react: observer_token: "" change_name: true change_avatar: true invite: "" server_id: "" channel_id: "" message_id: "" emoji: "" skip_completed: true skip_failed: true leave_token_on_ratelimit: true rotate_tokens: true max_anti_raid_queue: 20 max_dms_per_token: 10
I am Using bright data proxies