Cannot update or adjust instances - t1.micro in many regions | I need to keep my server in ap-south-1 AWS only

[thefoodiecoder]

Hello,

Expected Behavior

After copying the ami-c74d0db4 to ap-south-1 region in AWS when I am running the command scrapoxy start conf.json -d I am getting below error:

➜  ~ scrapoxy start conf.json -d
2021-06-04T11:05:17.492Z - info: [Main] The selected providers are awsec2/ap-south-1
2021-06-04T11:05:17.524Z - debug: [Main] listen
2021-06-04T11:05:17.526Z - info: [Commander] GUI is available at http://localhost:8889
2021-06-04T11:05:17.527Z - debug: [Manager] start
2021-06-04T11:05:17.527Z - info: Proxy is listening at http://localhost:8888
2021-06-04T11:05:27.528Z - debug: [Manager] checkInstances
(node:28397) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
2021-06-04T11:05:27.928Z - debug: [Manager] adjustInstances: required:1 / actual:0
2021-06-04T11:05:27.928Z - debug: [Manager] adjustInstances: add 1 instances
2021-06-04T11:05:27.928Z - debug: [ProviderAWSEC2] createInstances: count=1
2021-06-04T11:05:28.473Z - error: [Manager] Error: Cannot update or adjust instances: message=The requested configuration is currently not supported. Please check the documentation for supported configurations., stack=Unsupported: The requested configuration is currently not supported. Please check the documentation for supported configurations.
    at Request.extractError (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/services/ec2.js:50:35)
    at Request.callListeners (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
    at Request.emit (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/Users/vijay/.nvm/versions/node/v13.8.0/lib/node_modules/scrapoxy/node_modules/aws-sdk/lib/request.js:38:9), code=Unsupported, name=Unsupported, time=Fri Jun 04 2021 16:35:28 GMT+0530 (India Standard Time), requestId=7a42b294-1fde-4c5a-8a55-9d6274dd2784, statusCode=400, retryable=false, retryDelay=61.57367821266806

My config file looks something like this:

{
    "commander": {
        "password": "############"
    },
    "instance": {
        "port": 3128,
        "scaling": {
            "min": 1,
            "max": 2
        }
    },
    "providers": [
        {
            "type": "awsec2",
            "accessKeyId": "############",
            "secretAccessKey": "#######+####+##",
            "region": "ap-south-1",
            "instance": {
                "InstanceType": "t1.micro",
                "ImageId": "",
                "SecurityGroups": [
                    "forward-proxy"
                ]
            }
        }
    ]
}

AMI Details:

forward-proxy-node - ami-05192f114881b3f23 [Copied ami-c74d0db4 from eu-west-1] forward-proxy-node-2 Root device type: ebs Virtualization type: paravirtual Owner: 440355816459 ENA Enabled: No

I event tried creating an instance from AMI but it did not show any supported instance type.

So I believe AMI needs to be updated to support other instance types or new AMI for instances of type t2 and t3 might help. Else, a tutorial to work with other proxy types like TinyProxy can also be useful to bypass this blocked.

Actual Behavior

This should create proxy instances successfully.

Steps to Reproduce the Problem

• All details are shared above to reproduce the problem.

Specifications

• Version of Scrapoxy: 3.1.1

Thanks, VIJAY CHHUTTANI

[venkataramanab]

Hi,

For ap-south-1 you should use t2 family since t1 is not available. You can use below AMI's.

eu-west-1 / t1.micro: ami-c74d0db4 eu-west-1 / t2.micro: ami-485fbba5 eu-west-1 / t2.nano: ami-06220275

[fabienvauchelles]

will be corrected in 4.0.0 with easy installation

[fabienvauchelles]

Hey there! 🌟 Exciting news! Scrapoxy 4 is ready to rock 🚀. Check it out at Scrapoxy.io (explore the "get started" guide, deployment documentation, and more 📚). I can't wait to hear your feedback on this new version! Send me your coolest screenshots with as many proxies as possible! 📸💻 Join the Discord community if you have any questions or just want to chat. You can also open a GitHub issue for any bug or feature request 🐞✨. See you soon! 😎 Fabien