Latest Announcemnent
New thread
Status
Not open for further replies.
wait, I sold two premium accounts today, for an hour upload without problems, with full speed, no broken files on my account, people are downloading my files, all my files uploaded before are online, payment is being processed.

Whats going on? :), Did I fall asleep before my pc?
 
@NewRapidGator

I'm still unable to access your website from my NL server.

Here are the tracetcp (tcptraceroute) and tracert (traceroute) info:
tracetcp.png

Because normal tracert is always unable to pass the node 87.226.133.21,
I also use tcptrace in order to confirm which node banned my server.
Here is the result of tracetcp from the same server to rapidgator.net when I can visit your website:
tracetcp5.png

The node 81.91.177.222 is strangely repeated 2 times.
After I uploaded 10GB files, the route would become the first picture.

Here is a working case after 87.226.133.21 from my home to RapidGator:
tracetcp2.png

Obviously, my server's packet cannot pass the node 10.221.98.2, which looks like a private IP because it's 10.0.0.0/8.
I don't know what's that; anyway, it's not important.

Here are other two working cases from my USA (Los Angeles) website servers to RapidGator:
tracetcp3.png


tracetcp4.png

Now the node before rapidgator.net becomes 81.91.177.37 instead of 81.91.177.222.

If I'm actually not banned by your server or your DC, maybe it's an internal routing issue of your DC.
Please do something.
 
Last edited:
gibalah said:
@NewRapidGator

I'm still unable to access your website from my NL server.

Here are the tracetcp (tcptraceroute) and tracert (traceroute) info:
tracetcp.png

Because normal tracert is always unable to pass the node 87.226.133.21,
I also use tcptrace in order to confirm which node banned my server.
Here is the result of tracetcp from the same server to rapidgator.net when I can visit your website:
tracetcp5.png

The node 81.91.177.222 is strangely repeated 2 times.
After I uploaded 10GB files, the route would become the first picture.

Here is a working case after 87.226.133.21 from my home to RapidGator:
tracetcp2.png

Obviously, my server's packet cannot pass the node 10.221.98.2, which looks like a private IP because it's 10.0.0.0/8.
I don't know what's that; anyway, it's not important.

Here are other two working cases from my USA (Los Angeles) website servers to RapidGator:
tracetcp3.png


tracetcp4.png

Now the node before rapidgator.net becomes 81.91.177.37 instead of 81.91.177.222.

If I'm actually not banned by your server or your DC, maybe it's an internal routing issue of your DC.
Please do something.
Click to expand...
try clearing ur cookie and cache...

By the way i think old rebills are gone... still today no old rebill...
 
Why you limit the downloads for premium users? 15 GB per day it's too low %)
Remove, please, this limit or increase it at least.
 
Status
Not open for further replies.
Back
Top