New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maybe add feature for multiple digital ocean accounts? #21
Comments
Thanks for the feedback and glad you find it useful. DO raise the limit to 100 without much hassle I've found and not necessarily keen the introduce this as it probably circumvents DO's TOS. An alternative would be to run multiple instances of CloudProxy with Docker. Not terribly resource-efficient and you'd have to implement something within your application to hit the multiple APIs. I will leave the issue open for now in case there is a wider interest. |
Thank you, I didn't know it was that simple on a new account. I run a homelab so self host so haven't used DO before. May I ask what you said you used it for to get your account upgraded? Do you also have an etherium address? I'll buy you a beer. |
I can't exactly remember, I've had it for a while, I think DO just require a payment or two to be made on the account before they upgrade the limit. Topping up your account with credit or you can settle your bill early as well, then requesting for the limit upgrade. Though no guarantees. My etherium address is |
I'm sorry but the aws now doesnt seem to work, the VMs spin up but don't appear on the proxy list or in the UI even after 15 mins, with the console saying waiting for allication. |
Thanks for reporting. I've found the issue and released a fix now. Please use the image |
Hi, I now seem to get this error: ` File "/usr/local/lib/python3.8/threading.py", line 890, in _bootstrap
File "/app/cloudproxy/providers/manager.py", line 15, in aws_manager File "/app/cloudproxy/providers/aws/main.py", line 92, in aws_start File "/app/cloudproxy/providers/aws/main.py", line 77, in aws_check_delete KeyError: 'PublicIpAddress' |
If you just ignore that error, it should still deploy the AWS instances successfully. It's a known issue where AWS creates the instance but doesn't allocate the IP instantly so when CloudProxy reads the response from AWS it cannot find the IP and causes the key error. I will fix it in a future release but in the interim, it should still continue to work as once AWS allocates the IP, it stops raising the exception. Let me know if it doesn't. |
Hello, I'm sorry but for amazon it just says "Pending: AWS allocating" and does not work even though the VM has been allocated in my aws dashboard and is fully up and running (just the vm and docker inside it, didn't check the proxy). Also just as a little side note the -e DIGITALOCEAN_MIN_SCALING=0 -e DIGITALOCEAN_MAX_SCALING=0 commands do not work, it always starts at 2 but isnt important. |
Are you sure you're running the latest Docker image? Try with the tag Also, check your password or username set doesn't include any characters which may cause an issue such as semicolons. Your best to use alphanumeric characters as passwords or usernames to ensure it doesn't cause any issues. If none of those work, could you try running this command (assuming you're using Linux or Mac with CURL installed): Obviously, replace the USERNAME, PASSWORD with your username and password, and PROXYIP with an IP of one of your AWS VMs. Give your AWS VM 6 to 8 minutes to deploy before running. If the response is the IP of the AWS VM then we know the proxy is working fine so helps narrow down the issue. |
Yeah thanks, it ended up being that, I could've sworn I did a pull. Thanks! |
Great, glad it's resolved! |
I'm loving this, it's perfect for what I need. Maybe a feature to consider in the future is to be able to use multiple digital ocean accounts as there's a limit of 10 for new users?
Thanks for releasing this!
The text was updated successfully, but these errors were encountered: