Rapidgator Discussion thread
- Thread starter ynj
- Start date
37,585 comments
F A S T E R
Active Member
no sales what heppen last april and may
checklinkr
Active Member
F A S T E R
Active Member
it effect by your traffic :
i think it still fine
i think fake image. give a video in stat refresh it in browser. after we accept
Skhrnykhsk
Active Member
Summer is coming guys ...
NightUploader
Active Member
may started very sad,
i have no sale yet
i had at least 2 sale almost every day last month
what change????
i have no sale yet
i had at least 2 sale almost every day last month
what change????
hello everyone i face issue litecoin payment i received payment but instant transfer another wallet without confirmation how is possible i use trust wallet since 2023 i never face any issue i never share key phase or any dapp connect please it's 75$
this is my wallet address ltc1q5h7d6xxj89kf9wgkjwvvkj7nhf03usshrkj7zp
and this is other wallet where my payment gone ltc1q9m27u7d698jtdvrx4ut0zrmq4cf4sr4krxpvr6
Post automatically merged:
Post automatically merged:
this is my wallet address ltc1q5h7d6xxj89kf9wgkjwvvkj7nhf03usshrkj7zp
and this is other wallet where my payment gone ltc1q9m27u7d698jtdvrx4ut0zrmq4cf4sr4krxpvr6
Last edited:
hi guys
what a difference between
Premium banners (eg https://rapidgator.net/article/premium/ref/*******)
and
Affilate banners (eg https://rapidgator.net/article/resource/ref/*******)
Is it worth publishing them or just links? Which one is better?
what a difference between
Premium banners (eg https://rapidgator.net/article/premium/ref/*******)
and
Affilate banners (eg https://rapidgator.net/article/resource/ref/*******)
Is it worth publishing them or just links? Which one is better?
wildword18
Active Member
hello everyone i face issue litecoin payment i received payment but instant transfer another wallet without confirmation how is possible i use trust wallet since 2023 i never face any issue i never share key phase or any dapp connect please it's 75$
Post automatically merged:
Post automatically merged:
this is my wallet address ltc1q5h7d6xxj89kf9wgkjwvvkj7nhf03usshrkj7zp
and this is other wallet where my payment gone ltc1q9m27u7d698jtdvrx4ut0zrmq4cf4sr4krxpvr6
someone hack your phone, or something stop using this device, and create another wallet if u using android the code is closed, not safe,
And if you have the extension in any browser, it's your fault if you get robbed.
Emperor2011
Active Member
Last edited:
Skhrnykhsk
Active Member
Wow, this week was just bad ... but next week will be good.
checklinkr
Active Member
this week google made big update bro
@RG_Support / @rapidgator — could you please escalate?
I represent coolspeeds.com, a third-party file upload automation service. Our customers configure their own file-hoster accounts (including rapidgator) and our service uploads files on their behalf. We have an unresolved authentication issue currently affecting 4 of our customers — they can no longer upload files to rapidgator through our service.
Since 2026-05-25, every login attempt to rapidgator from our service's server IP fails, regardless of which customer account is used:
The passwords ARE working. Verified by the customers themselves:
All 4 customers see this with all their accounts simultaneously.
The replies on ticket #578323 (agent Mark Jansen) so far have been:
The agent has not provided any technical confirmation of why valid, working credentials are deterministically rejected from our server IP while accepted from every other IP.
We are asking for:
Happy to provide the server IP and any other diagnostic data privately to a technical contact.
Thank you.
One more point: a 10-minute rate-limit lockout per failed attempt is a reasonable defense against brute-force attacks from human users, but it is not a workable policy for an automated service operating through the API. Even legitimate operations — re-authentication after token expiry, batch uploads, concurrent jobs from multiple customers — can hit this throttle and cascade the entire service into an unrecoverable state, because each subsequent attempt resets the 10-minute window. From an automation client's perspective there is no path to recovery short of stopping all requests for an extended period — and even that, as we are seeing now, is not enough.
It is entirely possible that this situation was triggered weeks or months ago by another customer of ours who misconfigured his rapidgator credentials in our service. A handful of failed logins from our service's IP would then accumulate and lock the IP out for everyone else — penalizing 4 unrelated customers (and counting) for a single misconfiguration they had nothing to do with.
For these reasons I am asking — please remove our service's IP from whatever rate-limit or block list it is currently on, and consider treating automated affiliate-upload services differently from human login attempts (per-account throttling rather than per-IP, longer cool-off windows that don't restart on retry, or a documented whitelisting procedure for legitimate services). The current behavior makes it impossible to provide a reliable upload pipeline for paying rapidgator users.
Thank you.
I represent coolspeeds.com, a third-party file upload automation service. Our customers configure their own file-hoster accounts (including rapidgator) and our service uploads files on their behalf. We have an unresolved authentication issue currently affecting 4 of our customers — they can no longer upload files to rapidgator through our service.
Since 2026-05-25, every login attempt to rapidgator from our service's server IP fails, regardless of which customer account is used:
- API endpoint
POST /api/v2/user/loginresponds with:
Code:{"response":null,"status":401,"details":"Error: Please wait 10 minutes"} - Web form
POST /auth/login(with Cloudflare Turnstile correctly solved) returns the page with:
"Please fix the following input errors: Invalid login. Please wait 10 minutes."
The passwords ARE working. Verified by the customers themselves:
- Each customer logged into rapidgator from his own home PC with the same credentials — successful login, no errors.
- One of them (account owner of rapidgator ticket #578323) tested it specifically: same password from his home → works, same password through our service's server IP → "Invalid login. Please wait 10 minutes."
All 4 customers see this with all their accounts simultaneously.
The replies on ticket #578323 (agent Mark Jansen) so far have been:
The agent has not provided any technical confirmation of why valid, working credentials are deterministically rejected from our server IP while accepted from every other IP.
We are asking for:
- Technical confirmation whether our service's server IP is on any rate-limit / fraud / abuse list on your side.
- If yes — what is the procedure to whitelist a legitimate upload-automation service?
- If no — a real technical explanation, because the current "your password is wrong" reply is provably incorrect (verified by direct user testing).
Happy to provide the server IP and any other diagnostic data privately to a technical contact.
Thank you.
Post automatically merged:
One more point: a 10-minute rate-limit lockout per failed attempt is a reasonable defense against brute-force attacks from human users, but it is not a workable policy for an automated service operating through the API. Even legitimate operations — re-authentication after token expiry, batch uploads, concurrent jobs from multiple customers — can hit this throttle and cascade the entire service into an unrecoverable state, because each subsequent attempt resets the 10-minute window. From an automation client's perspective there is no path to recovery short of stopping all requests for an extended period — and even that, as we are seeing now, is not enough.
It is entirely possible that this situation was triggered weeks or months ago by another customer of ours who misconfigured his rapidgator credentials in our service. A handful of failed logins from our service's IP would then accumulate and lock the IP out for everyone else — penalizing 4 unrelated customers (and counting) for a single misconfiguration they had nothing to do with.
For these reasons I am asking — please remove our service's IP from whatever rate-limit or block list it is currently on, and consider treating automated affiliate-upload services differently from human login attempts (per-account throttling rather than per-IP, longer cool-off windows that don't restart on retry, or a documented whitelisting procedure for legitimate services). The current behavior makes it impossible to provide a reliable upload pipeline for paying rapidgator users.
Thank you.
Last edited: