Scrapoxy is a super proxy aggregator, allowing you to manage all proxies in one place π―, rather than spreading it across multiple scrapers πΈοΈ. It also smartly handles traffic routing π to minimize bans and increase success rates π.
When installing a new connector I get the following error:
The resource 'projects/xxx/zones/europe-west1-c/instances/scrapoxy-template-instance' was not found
I can see in gcp that the instance is trying to create. I can see no errors in the gcp console. After a few seconds the instance is gone and the error is thrown.
Expected Behavior
Connector is installed correctly
Steps to Reproduce
For me it occured after uninstalling a connector and then trying to install it again
Install connector with fresh scrapoxy deployment (typically works)
Uninstall the connector (works)
Install another connector (does not work with error0
Failure Logs
I cannot see that there are any usable logs besides the error in my deployment. I use the helm chart on Kubernetes (which is awesome in general btw)
Scrapoxy Version
latest (4)
Custom Version
[X] No
[ ] Yes
Deployment
[ ] Docker
[ ] Docker Compose
[X] Kubernetes
[ ] NPM
[ ] Other (Specify in Additional Information)
Operating System
[X] Linux
[ ] Windows
[ ] macOS
[ ] Other (Specify in Additional Information)
Storage
[ ] File (default)
[ ] MongoDB & RabbitMQ
[ ] Other (Specify in Additional Information)
Additional Information
I changed the commander to LoadBalancer to have an accessible external IP. But that should have no impact afaik.
Current Behavior
When installing a new connector I get the following error: The resource 'projects/xxx/zones/europe-west1-c/instances/scrapoxy-template-instance' was not found
I can see in gcp that the instance is trying to create. I can see no errors in the gcp console. After a few seconds the instance is gone and the error is thrown.
Expected Behavior
Connector is installed correctly
Steps to Reproduce
For me it occured after uninstalling a connector and then trying to install it again
Failure Logs
Scrapoxy Version
latest (4)
Custom Version
Deployment
Operating System
Storage
Additional Information
I changed the commander to LoadBalancer to have an accessible external IP. But that should have no impact afaik.
It also does not work with docker Anymore :(