手把手教你使用GoAgent

2011年8月22日 | 分类: 翻墙相关 | 标签: , , , ,

因为本人是文科生,本来就不适合写程序和脚本,因此AutoGoAgent出现了种种问题,而且GoAgent中自带的上传工具比AutoGoAgent还简单-_- 。。。在此本人深表歉意。

如果您使用AutoGoAgent出现了问题,您可以跟着这篇文章做一遍。

本文将会为您讲解:

* 0.准备工作

* 1. 在Google APP Engine中申请帐号、上传GoAgent服务器端

* 2. 配置GoAgent客户端

* 3. 浏览器中设置自动代理

* 4. 一些问题及解决办法

0.准备工作

俗话说的好,工欲善其事,必先利其器,何况我们现在连器都没有-_- …

 

我们必须先准备一些东西来继续我们的操作:

* 一台电脑

* 一个GMail帐号

* 一台手机

* GoAgent,下载以后解压到任意一个文件夹即可http://nodeload.github.com/phus/goagent/zipball/1.0

 

如果一切准备完成,我们就继续:

1. 申请Google APP Engine

 

1.1 欢迎界面

首先,我们打开这个页面(如果需要登录,请用GMail帐号和密码登录):

https://appengine.google.com/start/createapp

这时我们应该会看到如下所示的页面。

 

点击”Create Application”,如果见到如图所示页面,请继续,如果之前验证了手机号,那么请跳到步骤1.3。

 

1.2 验证手机

如果您见到了这样的页面,没关系,您只是没有验证您的手机而已。您只要在图中填入您的手机号即可,手机号前要加入”+86″

 

举个例子,如果您的手机号码为13444444444,那么您就应该这么填:

+8613444444444

 

填入以后,您的手机应该会收到一个验证码的信息,例如:

Google App Engine Code: 4959632

 

那么,您把4959632填入Mobile Number框中即可。

 

填入以后点ok,我们即可见到如步骤1.3图中的页面,那么我们:

1.3 创建App

 

创建App是很简单的一件事情,像注册论坛用户一样。我们首先需要一个App ID(图1.3中的1),这个要求必须是英文,但可以有短横线“-”。

比如我选了“frog-in-301”。

 

接着是Application Title,这个无关紧要,随意填一个即可,我就很懒地填了一个“test”了事(图1.3中的2)。

如果您刚刚验证了手机,您还得确认使用条款,把图1.3中的3打勾即可。

 

点击“Create Application”,如果提示您喜欢的AppID被抢注了,那么换一个即可。

 

如果一切顺利,我们就进行下一步:

1.4 GoAgent服务器端的上传

上传GoAgent服务器端的方法很简单,我们先打开解压出来的GoAgent文件夹,一路点进server文件夹,然后点uploader.bat。

 

然后会提示你输入AppID,这就是刚才你注册时得到的AppID。然后会要求你输入GMail帐号密码,按提示输入即可。

注意:输入密码时不会显示星号或者其他东西。

 

 

如果一切顺利,那么我们就可以进入第二步:

2. 配置客户端

GoAgent的客户端配置忒简单了,只需如此设置:

开解压出来的GoAgent文件夹,进入local文件夹,编辑proxy.ini,找到[gae]下面的“appid=”,后面填入你的appid即可,比如这样:

appid = frog-in-301

 

保存,ok。运行GoAgent.exe即可。

我们还可以设置GoAgent开机自启动,运行addto-startup.vbs即可。

 

如果搞定了,我们就可以:

3. 配置浏览器

目前本文只有Chrome和Firefox的设置方法。

 

3.1 Chrome

 

首先,我们先下载Proxy Switchy软件,下面是汉化版的地址:

https://chrome.google.com/webstore/detail/bgfkhjmcnkmegdmagboackgipbdpomke?hl=en&hc=search&hcp=main#

接着,我们如图设置:

 

附:GFWList地址:

http://autoproxy-gfwlist.googlecode.com/svn/trunk/gfwlist.txt

这样我们就可以访问YouTube等被墙掉的网站了。

 

3.2 Firefox

在附加组件管理器中安装“autoproxy”,接着我们重启firefox,重启后在autoproxy欢迎界面中默认代理栏里选择“自定义”。

 

接下来点左下角的“添加代理”,名字GoAgent,地址127.0.0.1,端口8087,http方式,这样就可以搞定了。

 

这样我们就可以访问YouTube等被墙掉的网站了。

 

4.常见问题

4.1 我收不到App Engine的短信?

您可以等一段时间重试一些,您也可以尝试填入您的Google Voice号码。填入您的手机号码时记得在前面加上国家代码”+86″。

 

来源https://docs.google.com/document/pub?id=1b5rdedtB0aSE5-KTuy2d9ieAgKC_YDCY7HI5EpjtdOM&pli=1

GoAgent项目地址:http://code.google.com/p/goagent/

详细教程参考http://igfw.net/archives/2348

  • 为什么goagent第一次运行需要管理员权限?
  • 因为goagent会尝试调用certmgr.exe向系统导入IE/Chrome的证书,这需要管理员权限。
  • Firefox怎么不能登陆twitter/facebook等网站?
  • 打开FireFox->选项->高级->加密->查看证书->导入证书, 选择local\ca.cer, 勾选所有项,导入。
  • 如何防止代理被匿名使用(盗用)?
  • 目前goagent最新版是支持的,先在server\fetch.py中开头修改__password__ = '123456',重新上传fetch.py,然后在proxy.ini中的gae项目下这样配置即可password = 123456,即可。注意:本功能不会影响网速,请放心使用。
  • 怎样设置不显示气泡提示?
  • 用reshack/exescope等资源编辑工具把气泡提示字符串清空即可。
  1. z235689785
    2011年9月3日10:29

    博主,我最近收到google的一封邮件,标题为“Google App Engine Leaving Preview”,这是不是意味着以后google App engine就不能随便申请或使用了呀?要是没了GoAgent或wallproxy-plugins,可让咱们兲朝P民怎么活呀

    我英文不行,看不明白这封信的意思,故附上信件原文,希望英文好的朋友解说一下:

    ————————————————————————-

    Dear Google App Engine Application Administrator,

    In May at Google I/O we announced that Google App Engine would be leaving Preview status later this year. As part of Google’s long-term commitment to App Engine, we are also updating our policies, pricing and support model to reflect its status as a fully supported Google product. We plan to roll this out in the second half of September but we wanted to let you know what this will mean for you and your App Engine applications. Please be aware that the timeline may change, but you can keep up to date on our progress on the App Engine blog. We plan to send a second email once the new pricing is in effect.

    For all paid applications using the High Replication Datastore (HRD), we will be introducing a new 99.95% uptime SLA. The current draft form of the SLA can be found at http://code.google.com/appengine/sla.html. For apps not using HRD, we will also soon release a tool that will assist with the migration from Master/Slave (M/S) to HRD (you can sign up to be in the Trusted Tester for the tool here: http://goo.gl/3jrXu). We would like to emphasize that the SLA only applies to applications that have both signed up to be a paid App and use the HRD Datastore.

    App Engine has a 3 year deprecation policy. This policy applies to the entire App Engine platform with the exception of “trusted tester” and “experimental” APIs. This is intended to allow you to develop your app with confidence knowing that you will have sufficient notice if we plan to make any backward-incompatible API changes that will impact your application.

    We will be updating the Terms of Service with language more geared towards businesses. A draft of the new ToS can be found at http://code.google.com/appengine/updated_terms.html.

    We are introducing new Premier Accounts that will have access to Operational Support, invoice-based billing, and allow companies to create as many applications as they need for $500 per account per month (plus usage fees). If you are interested in a Premier Account, please contact us at appengine_premier_requests(at)google.com.

    We will be moving to a new pricing structure that ensures ongoing support of App Engine. Details of the new structure can be found at http://www.google.com/enterprise/cloud/appengine/pricing.html. This includes lowering the free quotas for all Apps. Almost all applications will be billed more under the new pricing. Once App Engine leaves preview this pricing will immediately go into effect, but we’ve done a few things to ease the transition:

    If you sign up for billing or update your budget between now and October 31st we will give you a $50 credit.

    In order to help you understand your future costs we are now providing a side by side comparison of your old bill to what your new bill would be. You can find these in your Admin Console under “Billing history” by clicking on any of your “Usage Reports”. Please review this information. It’s important that you study this projected billing and begin any application tuning that you want to be in effect prior to the new bill taking effect.

    We have created an Optimization Article to help you determine how you could optimize your application to reduce your costs under the new model.

    We have created a Billing FAQ based on the questions many of our customers have had about the new pricing model.
    The new pricing model charges are based on the number of instances you have running. This is largely dictated by the App Engine Scheduler, but for Python we will not be supporting concurrent requests until Python 2.7 is live. Because of this, and to allow all developers to adjust to concurrent requests, we have reduced the price of all Frontend Instance Hours by 50% until November 20th.

    Finally, if you have any additional questions or concerns please contact us at appengine_updated_pricing(at)google.com.

    In order to graduate from Preview status, we’ve made and continue to make large investments in platform features, scalability, and stability that your applications will benefit from. Thank you for your support, commitment, and feedback on App Engine as it has developed. We look forward to working with you for years to come!

    ————————————————————————-

    (因为我在GAE上有七八个App,所以我很担心这个,希望贴这个能引来高手指点。博主要是认为粘这种东西在回复里面不合适的话,就删掉这篇回复吧~)

  2. s
    2011年8月31日11:03

    问下,配置之后为什么不能访问google的服务了

    • iGFW
      2011年8月31日12:21

      有什么错误的提示吗?

  3. thinker
    2011年8月27日12:04

    请问这个东西能不能支持加密呢? 我查了一些资料 似乎不能…
    加密太弱的话 还是不安全

  4. 2011年8月24日12:44

    投稿:【VPN】免费VPN介绍:ShellfireVPN(赠送三个月专业帐号一个,价值180人民币)
    http://wuxiao.info/667
    欢迎采纳,谢谢

    • iGFW
      2011年8月24日12:49

      感谢支持,
      由于我想把这个月的博文数量控制在90以内,所以就不再另发了。
      我在 http://igfw.net/archives/4084 里更新加了你的那个教程,在推特上帮你rt啦。