easy-proxy
easy-proxy copied to clipboard
dzt
no centOS 7 servers available error
I was getting this too, seems to get the CentOS 7.x images, you need to specify type=distribution when calling the DO API to get all images. I submitted a fix: #28
@jd20 I am sorry, but i have that problem as well. Where do I put type=distribution? I am eager to fix, I just don't know here to go to fix it.
The changes you need to make are in the pull request I referenced in my comment above. Take a look here: https://github.com/dzt/easy-proxy/pull/28/files
So should I make those changes, or download your version of Easy Proxy?
When I changed the git command in the setup to the one you suggested, and got to the Digital Ocean API key part, it said there was a problem with Java.
Thank you so much for your help.
Harry
On 20 Dec 2018, at 21:53, Jason [email protected] wrote:
The changes you need to make are in the pull request I referenced in my comment above. Take a look here: https://github.com/dzt/easy-proxy/pull/28/files https://github.com/dzt/easy-proxy/pull/28/files — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dzt/easy-proxy/issues/26#issuecomment-449264063, or mute the thread https://github.com/notifications/unsubscribe-auth/Aq4chVf-9va1P6aI3G9wtC1DtaLQ6P9aks5u7HdQgaJpZM4VgPSy.
Maybe better to make the changes manually, because my fork could be out-of-date by now. Which git command are you changing? git clone?
In #28 you put to use git clone https://github.com/jd20/easy-proxy.git instead of the $ git clone https://github.com/dzt/easy-proxy.git in the script. So I have Easy Proxy downloaded, but where exactly do I go to make the changes? I am not super experienced with editing code to stuff. Is it in terminal or in the actual application?
I just checked, actually my fork is still up-to-date, last commit on this project was back in January. So, manually making the changes won't help actually. What's the Java error you were getting?
When I add an API key, this happens.
On 20 Dec 2018, at 22:02, Jason [email protected] wrote:
Maybe better to make the changes manually, because my fork could be out-of-date by now. Which git command are you changing? git clone?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dzt/easy-proxy/issues/26#issuecomment-449266379, or mute the thread https://github.com/notifications/unsubscribe-auth/Aq4chZRpkuQItQ0wcklUKyB2RbLT_4OFks5u7HlsgaJpZM4VgPSy.
From the error message, it doesn't sound like you're using my fork, it sounds like you're using dzt's master branch (since the error is about the constructor, which is what my change fixed). Can you run the following command from terminal: grep require /Users/harrymcadam/easy-proxy/index.js and post the output, to confirm?
“No such file or directory”
Let me try with yours. I might have switched back to troubleshoot.
On Thu, Dec 20, 2018 at 10:27 PM Jason [email protected] wrote:
From the error message, it doesn't sound like you're using my fork, it sounds like you're using dzt's master branch (since the error is about the constructor, which is what my change fixed). Can you run the following command from terminal: grep require /Users/harrymcadam/easy-proxy.index.js and post the output, to confirm?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dzt/easy-proxy/issues/26#issuecomment-449273499, or mute the thread https://github.com/notifications/unsubscribe-auth/Aq4chWW2clj-a2Rjx5_NQEX_0YNoXktTks5u7H87gaJpZM4VgPSy .
Okay essentially, here is what I did, step by step.
I opened up Terminal, and put:
git clone https://github.com/jd20/easy-proxy.git https://github.com/jd20/easy-proxy.git
I then put: cd easy-proxy
Then: sudo npm install
And last: npm run dev
At this, it opened up Easy-Proxy through Electron, and this happened:
On 20 Dec 2018, at 22:29, Jason [email protected] wrote:
Sorry, had a typo in my command, just fixed.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dzt/easy-proxy/issues/26#issuecomment-449274131, or mute the thread https://github.com/notifications/unsubscribe-auth/Aq4chdAzYxat2LykGAc9VRTjEz0LyzJNks5u7H-9gaJpZM4VgPSy.
It's working for me, when I just tried your steps. Your git clone looks a bit weird though, what directory are you cloning to? Are you sure you're not cloning to somewhere else, and then cd'ing into the old version? Because based on your error, I'm 99% sure you're running the original version, not the modified one.
Okay, I made a video with exactly what I did. Will send it over in a second if that is okay.
On Thu, Dec 20, 2018 at 10:41 PM Jason [email protected] wrote:
It's working for me, when I just tried your steps. Your git clone looks a bit weird though, what directory are you cloning to? Are you sure you're not cloning to somewhere else, and then cd'ing into the old version? Because based on your error, I'm 99% sure you're running the original version, not the modified one.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dzt/easy-proxy/issues/26#issuecomment-449276573, or mute the thread https://github.com/notifications/unsubscribe-auth/Aq4chdtV2IGkYUzHuLV-9JSKwvnIRwjiks5u7IKLgaJpZM4VgPSy .
Ok, I see what's missing, you're still on the master branch of my fork, not the branch which has the changes. After you run cd easy-proxy, run git checkout fix_do_api, then you can run npm run dev.
PS: Be sure to delete the video afterwards, it has your API token key which can be used to gain write access to your account.
Wow. I cannot thank you enough. That really worked! I appreciate it, and will get back to you if I need more help.
It is rare nowadays to find someone who will put that much time aside to help someone they don’t even know.
For that, I say thank you.
By the way, saw you lived in Cupertino. I live in Portola Valley (near Menlo Park).
Harry
On 20 Dec 2018, at 23:02, Jason [email protected] wrote:
Ok, I see what's missing, you're still on the master branch of my fork, not the branch which has the changes. After you run cd easy-proxy, run git checkout fix_do_api, then you can run npm run dev.
PS: Be sure to delete the video afterwards, it has your API token key which can be used to gain write access to your account.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dzt/easy-proxy/issues/26#issuecomment-449282182, or mute the thread https://github.com/notifications/unsubscribe-auth/Aq4chU5q5cBBllaiQnoqxeJk1b7_Ccyhks5u7Id0gaJpZM4VgPSy.
