-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
代理网络下的软件运行问题 #66
Comments
代理“按理”说是支持的,通过标准的方法(设置HTTP_PROXY和HTTPS_PROXY变量)就应该可以支持。问题是,我以前试过,有的代理可以,有的好像就不行,原因不详。代理的支持是Request库/Python本身支持的。 On Thu, Jul 17, 2014 at 8:33 AM, linux0ne notifications@github.com wrote:
|
你贴出的日志应该是网络没通(代理隔断了)。 2014-07-17 11:43 GMT+08:00 Tianze Hou houtianze@gmail.com:
|
隔断了? 有没有更进一步的方法可以知道原因?可以提示我如何操作,我对python不是很熟悉,有些技术障碍。 |
难道是https的原因? 在我的网络类型下有的https网址可以被访问,比如github,有的就不行,不过一般都是国外的服务器不通的多,如百度这样的按理不应该。那个授权网址有http可以访问操作吗? 我现在没在电脑前,故此一问。 |
I think you are WALLed, trying OpenShift server to auth... =======是说网络被墙了。 |
作者: /apps/bypy ($t $f $s $m $d):按提示讲,应该是完全成功了,但是我留意了一下,上面竟然还有一句"I think you are WALLed,......" 这里再补充问一个问题,就不再开楼了: |
嗯,是的,授权已经成功了。 On Sun, Jul 20, 2014 at 7:26 PM, linux0ne notifications@github.com wrote:
|
我的网络环境是公司局域网,平时上大网的话,需要用代理。
bypy软件对代理软件的支持是怎么样的?
目前我遇到的问题是:
在终端里进行授权时,出现下面的提示
Authorizing, please be patient, it may take upto 60.0 seconds...
[08:26:34] Maximum number (1) of tries failed.
I think you are WALLed, trying OpenShift server to auth... =======这句话的意图是什么??
[08:26:49] Waiting 10 seconds before retrying...
[08:26:59] Request Try #2 / 5
[08:27:59] Waiting 20 seconds before retrying...
[08:28:19] Request Try #3 / 5
[08:29:19] Waiting 30 seconds before retrying...
[08:29:49] Request Try #4 / 5
[08:29:50] Waiting 40 seconds before retrying...
[08:30:30] Request Try #5 / 5
[08:31:30] Maximum number (5) of tries failed.
[08:31:30] Fatal: Both GAE & OpenShift server authorizations failed.
[08:31:30] Program authorization FAILED.
You need to authorize this program before using any PCS functions.
Quitting...
注:虽然是代理网络,但是我整个ubuntu 14.04系统的代理网络配置都是标准的、正确的,可以通过代理正常上网的。
The text was updated successfully, but these errors were encountered: