Resources
Everything you need to get the most out of SotaProxy.
Getting Started Guide
Learn how to set up and use SotaProxy in minutes.
Video Tutorials
Watch step-by-step tutorials for all features.
API Documentation
Complete API reference for developers.
Support answers faster when the first message already contains enough to reproduce the problem. Below is what to attach, what we can check on our side, and what is almost always faster to settle yourself.
What to attach
Four things cover most cases, and without them the first reply is a request for them.
- The connection string with the password removed. It shows which product, which country and which session lifetime are in use, and the mistake is usually visible in it.
- The status code and the target address. A 403, a 407, a 429 and a timeout are four different stories with four different fixes.
- The time to the minute, with its timezone. Without it we cannot find your session in the logs.
- What you already tried. If the request passes through curl but not from your code, that removes half the hypotheses immediately.
What we can check and what we cannot
The boundary is the same one drawn everywhere else on this site.
We see our side: whether the address is alive, what the geo database says about it, whether targeting applied, whether the session is holding, whether the balance is there and whether you hit a per-address limit. All of that is checkable and fixable.
We do not see the other side and do not control it. If a target decided not to serve you a page, that is its decision, and no proxy setting overrides it. We will help work out whether the address is the reason, but we will not promise access to a particular site.
Refunds on an unused balance are open to discussion; refunds on spent traffic are not, because it is spent and already paid for on our side.
What is faster to settle yourself
The four most common tickets have ready answers in the documentation, and reading them is quicker than waiting.
- A 403 on the first request is address class: the target filters hosting ranges and you need residential.
- A 407 is authentication: the login and password did not arrive in the form your tool expects.
- A 429 after a run of successful requests is pace: more addresses, or a sparser pass.
- A timeout with no status code is the network rather than a block. Retry later and do not change address type.
About tickets
Where do I write?
Telegram or email. Telegram is faster because the ticket is created there.
Why do you ask for the connection string?
Because it shows the product, the country and the session parameters. Half the tickets close at that step without any back and forth.
Will you help configure my scraper?
With the proxy part: the string, targeting, sessions and status codes. Debugging your code or getting past a target’s defences is not something we take on.
What about refunds?
An unused balance is open to discussion. Spent traffic is not refunded, because it has already been paid for on our side.