Open st1ne opened 1 year ago
Tokens and proxies are fine, but some accounts just can't access the server
st1ne Im having a lot of issues like you but yours seems way better. I keep getting captcha's after captcha's. Does using a proxy help this.
I tried to join with 3 tokens and got the same error on all of them, even tho they are email + phone verified.
same here
st1ne Im having a lot of issues like you but yours seems way better. I keep getting captcha's after captcha's. Does using a proxy help this.
yes obv
same, anyone have an idea why? Is it related to JA3 fingerprint?
joiner gets patched slowly
fingerprint wouldnt help forsure
is there already a fix? didnt find it and i thought its my tokens and now i have over 500 but they cant join server dayum
no fix yet :(
do u think it will get fixed?
not sure, i hope so
so if i get code 403 failed to join guild {''message" : "unknown message code 10008} there is nothing I can do its not my tokens its not proxies and its not my finger prints what else can it be ? feeling very unmotivated by this code
The only thing you can do is fixing the code by yourself or, waiting for a fix.
word thanks guess im assed out
I bypassed the new "measures" you just have to use the discord-client ja3, user agent and x_super_properties, seems like they blacklisted bunch of known ja3 and useragents
I bypassed the new "measures" you just have to use the discord-client ja3, user agent and x_super_properties, seems like they blacklisted bunch of known ja3 and useragents
Could you be a little more specific?) Where can I touch discord-client ja3?
@Coun1er no cap im lost idek how to fuck with the config file
@forelli13 what?) I don't understand you
@Coun1er sorry just dont know how to fix it
@raulmonge Did I understand you correctly? I just need to replace the fingerprint "Client Hello" with the correct one?
You need to buy custom fingerpints that would fix it. Discord blacklistes the dmdgo one so you need to buy new ones
You need to buy custom fingerpints that would fix it. Discord blacklistes the dmdgo one so you need to buy new ones
What do you mean by a fingerprint? X-Super-Properties? Replacing them doesn't affect anything.
ja3, useragent, X-Super-Properties
ja3, useragent, X-Super-Properties do you have an example? on python cannot be replaced ja3
tf why works for u i changed it in fingerprints file and still dont work then i changed in config file too also dont work... idk why i get this and also why anti-captcha.com not working?
i can help you dm me KADIUM#7571
i need some help too lol
@KADIUMX @raulmonge I used cycleTLS to modify the ja3 fingerprint user-agent and X-Super-Properties, but I still get errors, is there anything else I haven't noticed?
@MapleAzure If you replace on white ja3, you get the error "uTlsConn.Handshake() error: remote error: tls: handshake failure".
this module doesn't work(
i added u xesul
i can help you dm me KADIUM#7571
I sent you a friend request, im subzero
i am unpatching this tool every time, using it for over 1 year now. i have the fix for all patches untill now, if anyone is interested could reward me for my work and get the latest updates. contact me per email if interested ivnbbkr@proton.me and i`ll share with you my telegram. I am charging a One-time fee as a license in order to always receive latest working update of mass dm go.
P.S : problem is not only the flagged fingerprints ( well first of all all older fingerprints needs to be changed not just because they got flagget but also because the discord x-super-properties has now one extra parameter ) . (second of all only by fixing the fingerprint won`t fix unknown error message, you will have to do a join loop in case of unknown error message and renew the cookies aswell ) .
what do u mean by join loop ?
same problem, did someone solve it ?
any update on this ?
any update on this ?
adding this to the headers fixed it for me (i am not so sure if it will work for others but its worth a try):
"X-Super-Properties": "ewogICJvcyI6ICJXaW5kb3dzIiwKICAiYnJvd3NlciI6ICJEaXNjb3JkIENsaWVudCIsCiAgInJlbGVhc2VfY2hhbm5lbCI6ICJjYW5hcnkiLAogICJjbGllbnRfdmVyc2lvbiI6ICIxLjAuNDkiLAogICJvc192ZXJzaW9uIjogIjEwLjAuMjI2MjEiLAogICJvc19hcmNoIjogIng2NCIsCiAgInN5c3RlbV9sb2NhbGUiOiAiZW4tVVMiLAogICJjbGllbnRfYnVpbGRfbnVtYmVyIjogIjE1MjQ1MCIsCiAgImNsaWVudF9ldmVudF9zb3VyY2UiOiBudWxsCn0="
basically the base64 encoding stuff translates to this, its pretty general and not user specific so i am pretty sure it will work with yall as well like it did for me:
{
"os": "Windows",
"browser": "Discord Client",
"release_channel": "canary",
"client_version": "1.0.49",
"os_version": "10.0.22621",
"os_arch": "x64",
"system_locale": "en-US",
"client_build_number": "152450",
"client_event_source": null
}
any update on this ?
adding this to the headers fixed it for me (i am not so sure if it will work for others but its worth a try):
"X-Super-Properties": "ewogICJvcyI6ICJXaW5kb3dzIiwKICAiYnJvd3NlciI6ICJEaXNjb3JkIENsaWVudCIsCiAgInJlbGVhc2VfY2hhbm5lbCI6ICJjYW5hcnkiLAogICJjbGllbnRfdmVyc2lvbiI6ICIxLjAuNDkiLAogICJvc192ZXJzaW9uIjogIjEwLjAuMjI2MjEiLAogICJvc19hcmNoIjogIng2NCIsCiAgInN5c3RlbV9sb2NhbGUiOiAiZW4tVVMiLAogICJjbGllbnRfYnVpbGRfbnVtYmVyIjogIjE1MjQ1MCIsCiAgImNsaWVudF9ldmVudF9zb3VyY2UiOiBudWxsCn0="
basically the base64 encoding stuff translates to this, its pretty general and not user specific so i am pretty sure it will work with yall as well like it did for me:
{ "os": "Windows", "browser": "Discord Client", "release_channel": "canary", "client_version": "1.0.49", "os_version": "10.0.22621", "os_arch": "x64", "system_locale": "en-US", "client_build_number": "152450", "client_event_source": null }
it's not working now, any update ?
any update on this ?
adding this to the headers fixed it for me (i am not so sure if it will work for others but its worth a try):
"X-Super-Properties": "ewogICJvcyI6ICJXaW5kb3dzIiwKICAiYnJvd3NlciI6ICJEaXNjb3JkIENsaWVudCIsCiAgInJlbGVhc2VfY2hhbm5lbCI6ICJjYW5hcnkiLAogICJjbGllbnRfdmVyc2lvbiI6ICIxLjAuNDkiLAogICJvc192ZXJzaW9uIjogIjEwLjAuMjI2MjEiLAogICJvc19hcmNoIjogIng2NCIsCiAgInN5c3RlbV9sb2NhbGUiOiAiZW4tVVMiLAogICJjbGllbnRfYnVpbGRfbnVtYmVyIjogIjE1MjQ1MCIsCiAgImNsaWVudF9ldmVudF9zb3VyY2UiOiBudWxsCn0="
basically the base64 encoding stuff translates to this, its pretty general and not user specific so i am pretty sure it will work with yall as well like it did for me:
{ "os": "Windows", "browser": "Discord Client", "release_channel": "canary", "client_version": "1.0.49", "os_version": "10.0.22621", "os_arch": "x64", "system_locale": "en-US", "client_build_number": "152450", "client_event_source": null }
it's not working now, any update ?
dude that's a year old xsp. get a new one
eyJvcyI6IldpbmRvd3MiLCJicm93c2VyIjoiRGlzY29yZCBDbGllbnQiLCJyZWxlYXNlX2NoYW5uZWwiOiJzdGFibGUiLCJjbGllbnRfdmVyc2lvbiI6IjEuMC45MTQ4Iiwib3NfdmVyc2lvbiI6IjEwLjAuMTkwNDUiLCJvc19hcmNoIjoieDY0IiwiYXBwX2FyY2giOiJ4NjQiLCJzeXN0ZW1fbG9jYWxlIjoiZW4tVVMiLCJicm93c2VyX3VzZXJfYWdlbnQiOiJNb3ppbGxhLzUuMCAoV2luZG93cyBOVCAxMC4wOyBXaW42NDsgeDY0KSBBcHBsZVdlYktpdC81MzcuMzYgKEtIVE1MLCBsaWtlIEdlY2tvKSBkaXNjb3JkLzEuMC45MTQ4IENocm9tZS8xMjAuMC42MDk5LjI5MSBFbGVjdHJvbi8yOC4yLjEwIFNhZmFyaS81MzcuMzYiLCJicm93c2VyX3ZlcnNpb24iOiIyOC4yLjEwIiwiY2xpZW50X2J1aWxkX251bWJlciI6Mjk5ODk5LCJuYXRpdmVfYnVpbGRfbnVtYmVyIjo0ODQ2OCwiY2xpZW50X2V2ZW50X3NvdXJjZSI6bnVsbCwiZGVzaWduX2lkIjowfQ==