MemeFiBot
MemeFiBot copied to clipboard
Invalid protocol detected in upgrade_boost
2024-09-13 18:20:55 | ERROR | 707 - khondoker | ⚠ Warning! Invalid protocol detected in upgrade_boost msg: You have no spins left
2024-09-13 18:21:01 | ERROR | 707 - khondoker | ⚠ Warning! Invalid protocol detected in upgrade_boost msg: You have no spins left
2024-09-13 18:21:09 | ERROR | 707 - khondoker | ⚠ Warning! Invalid protocol detected in upgrade_boost msg: You have no spins left
frequently showing this error.
This problem occured due to multiple account, plz add delay option between every account.
I think this can bypass Rate limit,
After changing useragent and adding those x-headers ->
'X-Forwarded-For':'127.0.0.1',
'X-Forwarded-Host' : '127.0.0.1',
'X-Client-IP' : '127.0.0.1',
'X-Remote-IP' : '127.0.0.1',
'X-Remote-Addr' : '127.0.0.1',
'X-Host' : '127.0.0.1',
Now going smoothly 🥵
Where do I add the x headers
@hasan1818666891 Where do I add the x headers
I think this can bypass Rate limit,
After changing useragent and adding those x-headers ->
'X-Forwarded-For':'127.0.0.1', 'X-Forwarded-Host' : '127.0.0.1', 'X-Client-IP' : '127.0.0.1', 'X-Remote-IP' : '127.0.0.1', 'X-Remote-Addr' : '127.0.0.1', 'X-Host' : '127.0.0.1',
which useragent you have used