felixlu / jap Goto Github PK

What steps will reproduce the problem?
1.remote:JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3
2.local: JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT-2
3.run:   python2 JAP_WS_LOCAL.py

What is the expected output? What do you see instead?
At firest,the process takes up 14M memory.After watching Youtube for about 2 
hours,it eats 96M.

What version of the product are you using? On what operating system?
os: Archlinux + Xfce4.10 + Chromium
- python2 2.7.3-4
- twisted 12.3.0-1
- python2-pyopenssl 0.13-2
- autobahn  0.5.9

Please provide any additional information below.
Maybe memory leak,or bad garbage collection.

What steps will reproduce the problem?
1.deploy openshift node
2.run node JAP_WS_LOCAL.js

What is the expected output? What do you see instead?
$ node JAP_WS_LOCAL.js

module.js:340
    throw err;
          ^
Error: Cannot find module 'websocket'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (/home/billy/Downloads/jap-master/JAP_WS_LOCAL_NODE/JAP/JAP_WS_LOCAL.js:16:17)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)


What version of the product are you using? On what operating system?
JAP_WS_REMOTE_NODE_OPENSHIFT-2.0.0-SNAPSHOT.zip
JAP_WS_LOCAL_NODE-2.0.0-SNAPSHOT.zip
OS:Archlinux

Please provide any additional information below.
According to package.json, remote server dependencies include websocket 
downloaded from your github rep.So what about the local client?

[deleted issue]

Why Polipo (or Privoxy) can not use JAP as a parent SOCKS proxy?

What steps will reproduce the problem?
1.I deployed jap in openshift, everything is ok,i can use it,but after two 
days, chrome ERROR 120(net::ERR_SOCKS_CONNECTION_FAILED), I landed 
openshift.redhat.com to restart the app.Then Return to normal，how to solve 
this problem。
2.
3.

What is the expected output? What do you see instead?
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onOpen
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onOpen
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost

What version of the product are you using? On what operating system?

JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2
JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3
windows 7 64bit    chrome 24.0.1312.56 

Please provide any additional information below.

modulus.io is a new paas which has websocket support

I download the latest jap JAP_WS_REMOTE_NODE_DOTCLOUD-2.0.0-SNAPSHOT.zip and 
deploy it on modulus.io.

without lucky, I got the following log:
Application Logs

> [email protected] install /mnt/data/2/node_modules/websocket
> node install.js

[websocket v1.0.8] Attempting to compile native extensions.
[websocket v1.0.8] Native extension compilation successful!
[email protected] node_modules/websocket
path.existsSync is now called `fs.existsSync`.

jap on dotcloud,sometimes it shows error:

remoteConnection error: Error: CryptoStream is not writable

Bad news.Free service of dotcloud will be unavailable soon.
http://blog.dotcloud.com/new-sandbox

Date Change to Sandbox
April 8th (no changes)
April 22nd All Sandbox applications will be unreachable via HTTP. You can still 
access them via SSH to download your code and data.
April 25th All Sandbox applications will be destroyed.
Note that we've pushed-out the sunset dates, removing the April 8 "no push" 
week and extending the HTTP access by a week (now April 22).

I setup a server on openshift with 2.0.
I read throught the code(including openshift,dotcloud etc.),but there's no more 
code deals with the config ["CERTIFICATE"]["AUTHENTICATION"] like 
before(Ver.0.2.0).
Are you facing difficulties so that you've got to reduce supporting SSH?
May I have great expectation that new version will be brought out ASAP?
I wish you all the best.All thanks to you!

I have successfully deployed JAP on dotcloud, but failed to do it on Heroku. 
Already try to build Procfile.

What steps will reproduce the problem?
git init
git add .
git commit -m "XXX"
heroku create
git push heroku master

heroku ps:scale web=1
heroku ps

Attached is Procfile for your review.

What is the expected output? What do you see instead?
The server cannot start after deployment.

What version of the product are you using? On what operating system?
JAP_WS_REMOTE_PYTHON_DOTCLOUD-1.0.0. OS: win7

Please provide any additional information below.

But JAP_LOCAL_PYTHON_WINDOWS-0.2.0 works.

What steps will reproduce the problem?
1.deploy JAP on Openshift successfully and remove local certificate setting in 
Issues 27.
2.without any connection for some time,maybe tow days. 
3.use it again.

What is the expected output? What do you see instead?
famous 'connectionlost' again

What version of the product are you using? On what operating system?
1.Remote:JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3
2.Local:JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT-2-TEST
3.OS:Archlinux + Xfce4.10 + Chromium

Please provide any additional information below.
My correction method is first to open my https://YYY-ZZZ.rhcloud.com:8443 
without any proxy,and then run JAP.
It seems Openshift server is sleeping so have to open the project homepage to 
activate it.

What steps will reproduce the problem?
1.remote: JAP_WS_REMOTE_NODE_MODULUS-2.0.0-SNAPSHOT
2.local: JAP_WS_LOCAL_NODE-2.0.0-SNAPSHOT.zip
3.OS: archlinux + lxde (updated to latest)

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.
1) it seems memory leaks that eat 153.8M for an hour downloading videos.
2) as Openshift, it use Amazon service and the servers local in U.S. East Coast 
too. so the network response speed from Mainland China is slower than to Google 
servers localed in West Coast. And the downloading speed is limited especially 
for my small ISP that sets the speed to 1/3 or 1/4 at night.
3) it will frequently and suddenly stop loading youtube videos just lasting for 
a few minutes or even few seconds.
4) do not need to import local CA.pem. no certificate problem to browse https 
websites.
5) due to Modulus pricing policy, one email account can use one month for free 
without network traffic quota.
for me, it does not worth to pay.

@jeroen
diff README.txt
- - open CONSOLE
+ - open CONSOLE and cd to the father dir of 
JAP_WS_REMOTE_PYTHON_OPENSHIFT-X.X.X  ## for cp cmd below
- cp -r ../JAP_WS_REMOTE_PYTHON_OPENSHIFT-X.X.X/* .  ## will not copy hidden 
dir ".openshift"
+ cp -r ../JAP_WS_REMOTE_PYTHON_OPENSHIFT-X.X.X/. .
- - chmod -R +x ./.openshift/action_hooks
+ - chmod -R +x ./.openshift/action_hooks ./JAP  ## be sure remote scripts can 
be run

What steps will reproduce the problem?
install JAP_WS_REMOTE_OPENSHIFT step by step in wiki 
and try 6 combination configs of:
1.remote files in path app_id/ or app_id/diy
2.have username/password or have no
3.remote json:type HTTP and local json:type HTTP port 8000 
or remote json:type HTTPS and local json:type HTTPS port 8443
all have the same debug output below:

What is the expected output? What do you see instead?
$ python2 JAP_WS_LOCAL.py
DEBUG:JAP.JAP_LOCAL:InputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: www.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 80
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: www.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 80
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onOpen
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: www.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 80
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onOpen
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: www.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 80
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onOpen
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onOpen
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost


What version of the product are you using? On what operating system?
I directly clone your codes from github.
My OS is Archlinux with
- installed PYTHON >= 2.7.0
- installed TWISTED
- installed PYOPENSSL
- installed AUTOBAHN

Please provide any additional information below.

What steps will reproduce the problem?
1. push the code into DOTCLOUD 
2. run JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2
3. use Proxy Checker to check 127.0.0.1:1080(socks5)

What is the expected output? What do you see instead?

D:\Ksda\JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2>JAP_WS_LOCAL.exe
DEBUG:JAP.JAP_LOCAL:InputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: www.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 80
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.onClose
DEBUG:JAP.JAP_LOCAL:InputProtocol.outputProtocol_connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocol.inputProtocol_connectionLost

[29:27] Testing Started.
    Proxy Server
    Address:    127.0.0.1:1080
    Protocol:   SOCKS 5
    Authentication: NO

[29:27] Starting: Test 1: Connection to the Proxy Server
[29:27] IP Address: 127.0.0.1
[29:27] Connection established
[29:27] Test passed.
[29:27] Starting: Test 2: Connection through the Proxy Server
[29:27] Authentication was successful.
[29:28] Error : the proxy server cannot establish connection to 
www.google.com:80
    Error = 0x05 (Connection refused).
    Please confirm that the target host address is correct.
    The error may also indicate that the proxy server is not operating properly.
[29:28] Test failed.
[29:28] Testing Finished.

What version of the product are you using? On what operating system?
JAP_WS_REMOTE_PYTHON_DOTCLOUD-2.0.0-SNAPSHOT-2
&
JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2

Please provide any additional information below.

What steps will reproduce the problem?
1. openshift account been created 
2. i have created my domain and app with rhc app create -a my-application-id -t 
diy-0.1 command
3. i did configure the JAP_WS_REMOTE.json according to example 5
4. i did "gem install rhc" & "gem update rhc" successfully 
What is the expected output? What do you see instead?
can not deploy to openshift

What version of the product are you using? On what operating system?
win7, Git-1.8.1.2-preview20130201, rubyinstaller-1.9.2-p290

Please provide any additional information below.
actually i am stocked in steps after
cd application-id
xcopy ..\JAP_WS_REMOTE_PYTHON_OPENSHIFT-X.X.X\*.* /s /y ### only for Windows
cp -r ../JAP_WS_REMOTE_PYTHON_OPENSHIFT-X.X.X/. . ### only for Linux
chmod -R +x ./.openshift/action_hooks ./JAP ### only for Linux
git add -A
git commit -m "JAP"
git push 

in command prompt i go to JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3 
Directory but the xcopy does not work?! as far as i know xcopy is cmd command 
not for git or rhc ??
what exactly should i do from this point?

Hi, JAP_REMOTE_WS_NODE_OPENSHIFT-2.0.0 does not work right now.

I tried to install a new one, but nothing changed.

Log:
D:\Program Files (Portable)\JAP\OPENSHIFT JAP>node JAP_LOCAL_WS.js
Warning: Native modules not compiled.  XOR performance will be degraded.
Warning: Native modules not compiled.  UTF-8 validation disabled.
server.connect
connections property is deprecated. Use getConnections() method
server.connections: 1
server.connect
server.connections: 2
server.connect
server.connections: 3
server.connect
server.connections: 4
server.connect
server.connections: 5
server.connect
server.connections: 6
server.connect
server.connections: 7
server.connect
server.connections: 8
server.connect
server.connections: 9
server.connect
server.connections: 10
server.connect
server.connections: 11
server.connect
server.connections: 12
server.connect
server.connections: 13
server.connect
server.connections: 14
server.connect
server.connections: 15
server.connect
server.connections: 16
server.connect
server.connections: 17
server.connect
server.connections: 18
server.connect
server.connections: 19
server.connect
server.connections: 20
server.connect
server.connections: 21
server.connect
server.connections: 22
server.connect
server.connections: 23
server.connect
server.connections: 24
server.connect
server.connections: 25
server.connect
server.connections: 26
localConnection.remoteAddress: s3.feedly.com
localConnection.remotePort: 80
localConnection.remoteAddress: s3.feedly.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.freehao123.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.feedly.com
localConnection.remotePort: 80
localConnection.remoteAddress: ecx.images-amazon.com
localConnection.remotePort: 80
localConnection.remoteAddress: ecx.images-amazon.com
localConnection.remotePort: 80
localConnection.remoteAddress: ecx.images-amazon.com
localConnection.remotePort: 80
localConnection.remoteAddress: g-ecx.images-amazon.com
localConnection.remotePort: 80
localConnection.remoteAddress: g-ecx.images-amazon.com
localConnection.remotePort: 80
localConnection.remoteAddress: note1day.com
localConnection.remotePort: 80
localConnection.remoteAddress: note1day.com
localConnection.remotePort: 80
localConnection.remoteAddress: s3.feedly.com
localConnection.remotePort: 80
localConnection.remoteAddress: s3.feedly.com
localConnection.remotePort: 80
localConnection.remoteAddress: s3.feedly.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.freehao123.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.freehao123.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.freehostia.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.freehostia.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.zhujiceping.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.zhujiceping.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.zhujiceping.com
localConnection.remotePort: 80
localConnection.remoteAddress: www.zrblog.net
localConnection.remotePort: 80
localConnection.remoteAddress: www.zrblog.net
localConnection.remotePort: 80
localConnection.remoteAddress: www.zrblog.net
localConnection.remotePort: 80
localConnection.remoteAddress: plus.google.com
localConnection.remotePort: 443
localConnection.remoteAddress: www.google.com
localConnection.remotePort: 443
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 25
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 24
localConnection.end
server.connections: 23
localConnection.end
server.connections: 22
localConnection.end
server.connections: 21
server.connect
server.connections: 22
localConnection.remoteAddress: productforums.google.com
localConnection.remotePort: 443
server.connect
server.connections: 23
localConnection.remoteAddress: clients4.google.com
localConnection.remotePort: 443
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 22
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 21
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 20
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 19
localConnection.end
server.connections: 18
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 17
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 16
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 15
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 14
localConnection.end
server.connections: 13
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 12
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 11
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 10
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 9
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 8
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 7
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 6
localConnection.end
server.connections: 5
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 4
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 3
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 2
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 1
client.connectFailed
error: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
localConnection.end
server.connections: 0

What's the difference between JAP_SSH_LOCAL and SSH-D?

New problem. Can't connect to any URL.
Traceback (most recent call last):
Debug:Jap.Jap_ws_local:wsInputProtocol.__init__
Debug:Jap.Jap_LocaL:inputProtocol.__init__
Debug:Jap.Jap_LocaL:inputProtocol.connectionMade
Debug:Jap.Jap_LocaL:inputProtocol.dataReceived
Debug:Jap.Jap_LocaL:inputProtocol.processDataState0
Debug:Jap.Jap_LocaL:inputProtocol.dataReceived
Debug:Jap.Jap_LocaL:inputProtocol.processDataState1
Debug:Jap.Jap_LocaL:inputProtocol.remoteAddressType:3
Debug:Jap.Jap_LocaL:inputProtocol.remoteAddress:wpad
Debug:Jap.Jap_LocaL:inputProtocol.remotePort:80
Debug:Jap.Jap_ws_local:wsInputProtocol.do_connect
Debug:Jap.Jap_ws_local:wsoutputProtocolFactory.__init__
Debug:Jap.Jap_ws_local:clientcontextfactory.__init__
Debug:Jap.Jap_LocaL:inputProtocol.connectionlost
.....

Any Proposal?

I follow the steps in README,download the certificate 
"ex-std-nodeXX.prod.rhcloud.com"
then configure CERTIFICATE/AUTHENTICATION/FILE in JAP_WS_LOCAL.json.The commond 
line shows "certificate not ok".
If I do not configure it,there's nothing wrong.
p.s. TYPE,ADDRESS,PORT and AUTHENTICATION have been configured correctly.

What steps will reproduce the problem?
1.remote: JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-4 
2.local: JAP_PYTHON-2.0.0-SNAPSHOT 
3.os: archlinux + lxde + python2

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

It works ok.
In my system I have to change this setting:
- chmod +w JAP_LOCAL_WS.json  # can not change the mode
+ chmod 766 JAP_LOCAL_WS.json

There are two useful functions in wallproxy-plugins 
(http://code.google.com/p/wallproxy-plugins/),not say the new wallproxy.
1.Find the config file and relate files at the same path of the main 
application file. So do not need to cd to the path then run the app. It's 
useful for Linux system to use one command in the terminal to run.
python2 /path/to/wallproxy-plugins/startup.py
Moreover, it's easy to set a autostart application that just use the same 
command, e.g. in Xfce.
For JAP, I have to make a sh file to autostart.
e.g. JAP_WS_LOCAL.sh
  cd /path/to/jap/
  python2 JAP_WS_LOCAL.py
If just run 'python2 /path/to/jap/JAP_WS_LOCAL.py', it will stop because the 
config file is not found.
2.Reinitialize the application immediately once the config file changed.So do 
not need to stop the app then change the config file. It's useful to change GAE 
appid or Google domain/IP.
Hope to add this two fuctions to JAP and APPP.
Thanks.

Hi

I deployed "JAP_REMOTE_WS_NODE_MODULUS-2.0.0" and configured 
"JAP_REMOTE_WS.json" as:
{
    "LOGGER":
    {
        "LEVEL": "DEBUG"
    },
    "REMOTE_PROXY_SERVER":
    {
        "TYPE": "HTTP",
        "PORT": 8080,
        "AUTHENTICATION":
        [
            {
                "USERNAME": "",
                "PASSWORD": ""
            }
        ]
    }
}


and " JAP_LOCAL_WS.json" as:

{
    "LOGGER":
    {
        "LEVEL": "DEBUG"
    },
    "LOCAL_PROXY_SERVER":
    {
        "ADDRESS": "127.0.0.1",
        "PORT": 1080
    },
    "REMOTE_PROXY_SERVERS":
    [
        {
            "TYPE": "HTTP",
            "ADDRESS": "xxx-yyy.onmodulus.net",
            "PORT": 8080,
            "AUTHENTICATION":
            {
                "USERNAME": "",
                "PASSWORD": ""
            },
            "CERTIFICATE":
            {
                "AUTHENTICATION":
                {
                    "FILE": ""
                }
            }
        }
    ],

but when i run "JAP_LOCAL_WS.bat" and enter address of a site in my browser, 
nothing happens (no data transfer). 
I have attached screenshots of the cmd window.

What steps will reproduce the problem?
1.A few days ago,followed the README.txt steps to deploy JAP on Openshift,and 
opened https://YYY-ZZZ.rhcloud.com:8443 to download certificate then configured 
JAP_WS_LOCAL.json correctly.Everything worked. 
2.This days the famous 'connectionlost' problem appears again.Open 
https://YYY-ZZZ.rhcloud.com:8443 without any proxy,and there is no longer 
certificate risk with the certificate information that Common Name is 
*.rhcloud.com.

What is the expected output? What do you see instead?
Terminal output 'connectionlost'
Chromium output 'Error 120'

What version of the product are you using? On what operating system?
1.Remote:JAP_WS_REMOTE_PYTHON_OPENSHIFT-2.0.0-SNAPSHOT-3
2.Local:JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT-2-TEST
3.OS:Archlinux + Xfce4.10 + Chromium

Please provide any additional information below.
My correction method is to delete the content of 
REMOTE_PROXY_SERVERS/CERTIFICATE/AUTHENTICATION/FILE,just "FILE": "".
Everything works again.
I think there is some improvement of Openshift certificate,no longer need to 
download local certificate.  

Hi! Can I install JAP_WS_REMOTE_NODE on VPS (Debian 6)?
I downloaded JAP_WS_REMOTE_NODE-2.0.0-SNAPSHOT.zip and tried to install it, but 
I was not sure how to configure JAP_WS_REMOTE.json and what to do next.

=========================INSTALLATION LOG=========================

# Install Node.js 0.8.21
#-----------------------------------
apt-get install python g++ -y
mkdir ~/nodejs && cd $_
wget -N http://nodejs.org/dist/node-latest.tar.gz
tar xzvf node-latest.tar.gz && cd `ls -rd node-v*`
./configure
make && make install

# Install JAP_WS_REMOTE_NODE-2.0.0-SNAPSHOT
#-----------------------------------
apt-get install unzip -y
mkdir ~/JAP && cd $_
wget https://jap.googlecode.com/files/JAP_WS_REMOTE_NODE-2.0.0-SNAPSHOT.zip

unzip JAP_WS_REMOTE_NODE*

cd JAP_WS_REMOTE_NODE*

#execute NM.bat
npm install git+https://github.com/jvansteirteghem/WebSocket-Node.git

#configure JAP_WS_REMOTE.json
nano JAP_WS_REMOTE.json

???BREAK!!!

#execute JAP_WS_REMOTE.bat

amazing jap！

i prefer the py version because i wanna run jap with wallproxy！

http://code.google.com/p/wallproxy/wiki/ThirdRun

wallproxy can run other py application now and i want to mix them in just one 
process

could you give me a hand？

What steps will reproduce the problem?
1.remote:JAP_WS_REMOTE_NODE_OPENSHIFT-2.0.0-SNAPSHOT
2.local:JAP_WS_LOCAL_NODE-2.0.0-SNAPSHOT
3.run:node JAP_WS_LOCAL.js

What is the expected output? What do you see instead?
At firest,the process takes up 9M memory.After surfriding
 and watching Youtube for about 3 hours,it eats 210M.

What version of the product are you using? On what operating system?
os: Archlinux + Xfce4.10 + Chromium
$ node --version
v0.8.21

Please provide any additional information below.
Maybe memory leak,or bad garbage collection.Worse then JAP_WS_LOCAL.py

Jap on Dotcloud with HTTPS.
Email clint (Thunderbird, balsa) use this proxy to login gmail. Google refuse 
and send a warning email.
Warning:Google prevented a suspicious attempt to sign in to your account.Was it 
you?

I'm not sure what happened, but I guess this is caused my own computer. 

Everything was OK yesterday, but today, this error appears in a sudden. 

By the way, it seems goagent also suffers a similar error, but when I reload 
it, it becomes all right.

OS: WIN8 PRO X64

Log:

D:\Program Files (Portable)\JAP\OPENSHIFT JAP PYTHON WINDOWS>JAP_LOCAL_WS.exe
Error loading Python DLL: C:/Users/Dekun/AppData/Local/Temp/_MEI94602/python27.d
ll (error code 5)

D:\Program Files (Portable)\JAP\OPENSHIFT JAP PYTHON WINDOWS>pause

I have deployed jap at dotcloud（JAP_REMOTE_PYTHON_DOTCLOUD-0.2.0）.When I 
use JAP_LOCAL_PYTHON_WINDOWS-0.2.0+firefox，I can visit AES256 encrypted 
website（for example www.torproject.org）.But when I use 
JAP_LOCAL_PYTHON_WINDOWS-0.2.0+chrome,it occurs error:
Invalid Server Certificate
You attempted to reach www.torproject.org, but the server presented an invalid 
certificate.
You cannot proceed because the website operator has requested heightened 
security for this domain.

when I visit RC128 encrypted website,both firefox and chrome is OK.

Expecting jap can run in appfog.Because in china,linking dotcloud or openshift 
is too slowly.

Can you reinstall JAP_WS_REMOTE_PYTHON_OPENSHIFT and attach your installation 
logs?
Can you also attach your OPENSHIFT logs (rhc tail <application-id>)?

Why?

1. I want to play minecraft with my family (<5 people, live in different 
places) on my own server. So to setup minecraft server on Openshift and have to 
setup ssh port-forwoding.
2. GFW block ssh to Openshift (in some areas?), or maybe make the connection 
worse like it fu*ks Google service. Have to connect via proxy.
3. Why can only JAP on Openshift help to do that? Because of certificate 
problem on GAE, ssh can not connect successfully via GAE based proxies. Or 
maybe I do not know the correct ssh configure. Hope someone can help.

Setup?

1. Full Data Chain
a) Directly
minecraft_client--ssh--minecraft_openshift_server
b) Via Some HTTP Proxy
minecraft_client--ssh--corkscrew--http_proxy--minecraft_openshift_server
c) Via JAP Socks Proxy
minecraft_client--ssh--corkscrew--privoxy--jap--minecraft_openshift_server

2. Environment
a) Client Deployment OS: Archlinux + LXDE
b) Client Deployment Tools: git + openssh + ruby (gem install rhc)

3. Server
Setup Free Minecraft Server Hosting on Openshift (good for family survival 
island mode)
Tutorial: https://www.openshift.com/blogs/paas-free-minecraft-server-hosting
Tips:
1) Follow exactly the steps.
2) DO NOT download the attachment. It's just the original files. Delete all the 
original content of "start" and "stop" and then copy the scripts into them and 
save. After that, better to run:
$ chmod -R +x .openshift/action_hooks  # notice the working path
3) If your 'tail minecraft.log' does not show the similar words, try to restart 
the app some times:
$ rhc app restart minecaft

4. Proxy
Deploy JAP on Openshfit (better with another account)
Wiki: https://code.google.com/p/jap/wiki/JAP_WS_REMOTE#JAP_WS_REMOTE_OPENSHIFT
Tips:
1) Depend packages (Archlinux): python2 + python2-pyopenssl + python2-crypto + 
twisted + python2-pip (pip2 install autobahn)
2) Follow EXACTLY the wiki

3. Tools
a) ssh
Openshift CLI needs ssh and need it to port-forward.
ssh can only use other tools to setup proxy (see 'man ssh_config'), so edit ssh 
config:
$ nano .ssh/config
Host *
ProxyCommand corkscrew 127.0.0.1 8118 %h %p
(it means ssh use corkscrew to proxy, and corkscrew tunnels data to the http 
proxy of privoxy 127.0.0.1:8118)

b) corkscrew
Corkscrew is a tool for tunneling SSH through HTTP proxies.
http://www.agroman.net/corkscrew/
Just install it, do not need to config. (Some tutorial says netcat can work 
too, but I can not setup successfully.)
But it turn out a problem: JAP is a socks proxy! so we need privoxy.

c) privoxy
Privoxy is a good tool to block ads and unify proxies setup.
http://www.privoxy.org/
Setup privoxy to forward JAP:
$ sudo nano /etc/privoxy/config
forward-socks5 / 127.0.0.1:1080 . # be aware of the '.'

Run?

1. Make sure your server is running properly.
ssh into your app machine to check 'tail diy-0.1/logs/minecraft.log'
2. Run JAP (see wiki above).
3. Run privoxy
$ sudo systemctl start privoxy # archlinux
4. Run rhc port-forward
$ rhc port-forward minecraft
Or run ssh directly such as
ssh -N -L 127.8.231.129:8080:127.8.231.129:8080 
a133b23e3f2644b8a2121eaf6801xxxx@minecraft-spminecraft.rhcloud.com
5. Run minecraft client
http://minecraft.net/

(If you and family do not want to or have not yet pay for minecraft, set 
minecraft server.properties 'online-mode' to false.)

JAP WS on OpenShift fail to work since yesterday.

logs here:
prompt: Is this ok?:  (yes) yes
yes
info:    Analyzing application dependencies in node server.js
info:    Checking app availability JAP_REMOTE_WS_NODE_NODEJITSU
info:    Creating app JAP_REMOTE_WS_NODE_NODEJITSU
info:    Creating snapshot 2.0.0
info     Uploading: [=============================] 100%
info:    Updating app JAP_REMOTE_WS_NODE_NODEJITSU
info:    Activating snapshot 2.0.0 for JAP_REMOTE_WS_NODE_NODEJITSU
info:    Starting app JAP_REMOTE_WS_NODE_NODEJITSU
error:   Error running command deploy
error:   Nodejitsu Error (400): Bad Request
warn:    Error returned from Nodejitsu
error:   Error: No active subscriptions available.
error:       at Object.module.exports.billing.findAvailable (/root/nodejitsu/lib
/nodejitsu/billing/billing.js:296:23)
error:       at fn (/root/nodejitsu/lib/nodejitsu/billing/billing.js:200:24)
error:       at Resource._request (/root/nodejitsu/node_modules/resourceful/lib/
resourceful/resource.js:184:13)
error:       at loop (/root/nodejitsu/node_modules/resourceful/lib/resourceful/r
esource.js:90:9)
error:       at /root/nodejitsu/node_modules/resourceful/lib/resourceful/resourc
e.js:78:20
error:       at exports.resource.app.resources.User.app.define.after.method (/ro
ot/nodejitsu/node_modules/flatiron-http-users/lib/http-users/user/core.js:82:9)
error:       at loop (/root/nodejitsu/node_modules/resourceful/lib/resourceful/r
esource.js:76:9)
error:       at Function.Resource.runAfterHooks (/root/nodejitsu/node_modules/re
sourceful/lib/resourceful/resource.js:92:7)
error:       at Resource._request (/root/nodejitsu/node_modules/resourceful/lib/
resourceful/resource.js:179:14)
error:       at Object.Couchdb.get [as callback] (/root/nodejitsu/node_modules/r
esourceful/lib/resourceful/engines/couchdb/index.js:61:9)
help:    For help with this error contact Nodejitsu Support:
help:      webchat: <http://webchat.nodejitsu.com/>
help:          irc: <irc://chat.freenode.net/#nodejitsu>
help:        email: <[email protected]>
help:
help:      Copy and paste this output to a gist (http://gist.github.com/)
info:    Nodejitsu not ok

the speed is slow on openshift and dotcloud,have there a new version on gae or 
cloudfroundry？

What steps will reproduce the problem?
1. server :JAP_WS_REMOTE_PYTHON_DOTCLOUD-2.0.0-SNAPSHOT-3
2. local : JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2
3.execute JAP_WS_LOCAL.bat

What is the expected output? What do you see instead?
D:\Documents\Downloads\JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2\JAP_WS_LOCAL
_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2>JAP_WS_LOCAL.exe
DEBUG:JAP.JAP_LOCAL:InputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost

It stucks here.
What version of the product are you using? On what operating system?
JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2
&
JAP_WS_REMOTE_PYTHON_DOTCLOUD-2.0.0-SNAPSHOT-3
Please provide any additional information below.
{
    "LOGGER":
    {
        "LEVEL": 10
    },
    "LOCAL_PROXY_SERVER":
    {
        "ADDRESS": "127.0.0.1",
        "PORT": 1080
    },
    "REMOTE_PROXY_SERVERS":
    [
        {
            "TYPE": "HTTPS",
            "ADDRESS": "xiao-xilou.dotcloud.com",
            "PORT": 443,
            "AUTHENTICATION":
            {
                "USERNAME": "1",
                "PASSWORD": "1"
            },
            "CERTIFICATE":
            {
                "AUTHENTICATION":
                {
                    "FILE": ""
                }
            }
        }
    ],
    "PROXY_SERVER":
    {
        "ADDRESS": "",
        "PORT": 0,
        "AUTHENTICATION":
        {
            "USERNAME": "",
            "PASSWORD": ""
        }
    }
}

 JAP_WS_REMOTE.json 

{
    "LOGGER":
    {
        "LEVEL": 10
    },
    "REMOTE_PROXY_SERVER":
    {
        "TYPE": "HTTPS",
        "AUTHENTICATION":
        [
            {
                "USERNAME": "1",
                "PASSWORD": "1"
            }
        ]
    }
}
The user name and password is just an example

thanks !

when i run JAP_WS_LOCAL.bat there is an error that says:




C:\Users\BIG_BUG\Desktop\JAP_WS_LOCAL_NODE-2.0.0-SNAPSHOT>node JAP_WS_LOCAL.js
Warning: Native modules not compiled.  XOR performance will be degraded.
Warning: Native modules not compiled.  UTF-8 validation disabled.

module.js:485
    throw err;
          ^
SyntaxError: C:\Users\BIG_BUG\Desktop\JAP_WS_LOCAL_NODE-2.0.0-SNAPSHOT\JAP_WS_LO
CAL.json: Unexpected token m
    at Object.parse (native)
    at Object.Module._extensions..json (module.js:482:27)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (C:\Users\BIG_BUG\Desktop\JAP_WS_LOCAL_NODE-2.0.0-SNAP
SHOT\JAP_WS_LOCAL.js:14:21)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)

C:\Users\BIG_BUG\Desktop\JAP_WS_LOCAL_NODE-2.0.0-SNAPSHOT>pause
Press any key to continue . . .




i installed node,websockets-node

plz help

1) when i use HTTP in the TYPE field of my server configuration 
file(JAP_REMOTE_WS_xxxx), i can open web page without any problem (actually 5 
error in 100 try, errors almost is in the beginning of usage), but when i use 
HTTPS in the TYPE field of server configuration file, most of time i got this 
error ""Error 120 (net::ERR_SOCKS_CONNECTION_FAILED): Unknown error."" (with 
chrome browser)(5 success in 100 try).
as you said with HTTP the transfer will be unencrypted, so i want to use HTTPS, 
but how i can solve this problem?

i tested with openshift, modulus, nodejitsu, result was the same.

2) there is also a little response problem, when i type an address in the 
address bar, it toke a while to begin loading page.

again thanks alot for your effort. 

it's my first time installing jap, so
1)i install 'JAP_REMOTE_WS_NODE_MODULUS-2.0.0.zip' in modulus site (i have 2 
app, one with username ans password, and second without)
2)i have extracted 'JAP_LOCAL_WS_PYTHON_WINDOWS-2.0.0' and config it.

when i execute 'JAP_LOCAL_WS.bat' the debug window give me below messeges:

C:\APJP\JAP_LOCAL_WS_PYTHON_WINDOWS-2.0.0>JAP_LOCAL_WS.exe
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocolFactory.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.LOCAL_WS.JAP_LOCAL_WS:WSInputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.LOCAL_WS.JAP_LOCAL:InputProtocol.connectionLost


as result my browser cannot open any page.

so what's wrong with it?
tnx

Hi Guys!
  My PC connects to Internet via http proxy！The DNS server(http proxy) can not resolve the address(such as xxx.rhcloud.com).I had tried to changed the hosts file,but it's no use.Can you help me? Thanks!

I notice @Jeroen you had updated your github JAP rep these days.
Can you make a changelog file to record the changing?
So that users will know to update server/client or not.
Thanks for your more and more perfect work of art!

Jap on dotcloud.
I had installed JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT and all software 
needed. Win7. Firefox v17.01. But no website can open.

Traceback (most recent call last):
file "<string>", line 17, in <module>
file 
"c:\projects\repository\jap_autobahn\jap_ws_local_python\make\pyinstaller\build\
pyi.win32\jap_ws_local\out00-pyz.pyz\json", line 278, in load
file 
"c:\projects\repository\jap_autobahn\jap_ws_local_python\make\pyinstaller\build\
pyi.win32\jap_ws_local\out00-pyz.pyz\json", line 326, in load
file 
"c:\projects\repository\jap_autobahn\jap_ws_local_python\make\pyinstaller\build\
pyi.win32\jap_ws_local\out00-pyz.pyz\json.decoder", line 366,in decode
file 
"c:\projects\repository\jap_autobahn\jap_ws_local_python\make\pyinstaller\build\
pyi.win32\jap_ws_local\out00-pyz.pyz\json.decoder", line 384,in raw_decode
ValueError: no json object could be decoded
pause

what to do next?

What steps will reproduce the problem?
1.run JAP_WS_LOCAL.bat

What is the expected output? What do you see instead?
it shows 

D:\Ksda\JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2>JAP_WS_LOCAL.exe
Traceback (most recent call last):
  File "<string>", line 17, in <module>
  File "C:\PROJECTS\REPOSITORY\jap\JAP_WS_LOCAL_PYTHON\MAKE\PYINSTALLER\build\py
i.win32\JAP_WS_LOCAL\out00-PYZ.pyz\json", line 278, in load
  File "C:\PROJECTS\REPOSITORY\jap\JAP_WS_LOCAL_PYTHON\MAKE\PYINSTALLER\build\py
i.win32\JAP_WS_LOCAL\out00-PYZ.pyz\json", line 326, in loads
  File "C:\PROJECTS\REPOSITORY\jap\JAP_WS_LOCAL_PYTHON\MAKE\PYINSTALLER\build\py
i.win32\JAP_WS_LOCAL\out00-PYZ.pyz\json.decoder", line 366, in decode
  File "C:\PROJECTS\REPOSITORY\jap\JAP_WS_LOCAL_PYTHON\MAKE\PYINSTALLER\build\py
i.win32\JAP_WS_LOCAL\out00-PYZ.pyz\json.decoder", line 384, in raw_decode
ValueError: No JSON object could be decoded

D:\Ksda\JAP_WS_LOCAL_PYTHON_WINDOWS-2.0.0-SNAPSHOT-2>pause


What version of the product are you using? On what operating system?
Win7 32bit with full pre-installation

Please provide any additional information below.

QQ is the most popular IM service software in China.

I try to config JAP as socks5 proxy in QQ's setting just in the login panel.

But as soon as I hit the "test" button, I got the message "cannot connect to 
the proxy server".

On the other hand, when I try the same process as above in VMware environment,

JAP works for QQ. That's strange...

Performance of previous app:
1. It works well at the begining. The version is 2.0.0-SNAPSHOT-2.

2. It does not work after a few days, i.e. "connectionLost" appears all the 
time.

3. After "dotcloud restart www.0 -A ksda" (I restart the service manually), it 
works well now.

Failure Installation of 2.0.0-SNAPSHOT-3:
1. I use Debian 6 x64 (on VMWare) to install JAP on DOTCLOUD Ver. 
2.0.0-SNAPSHOT-3.
2. Everything goes smoothly, until:

18:55:13.072578: [www] Successfully installed twisted pyopenssl autobahn 
zope.interface
18:55:13.073000: [www] Cleaning up...
18:55:17.602678: [www] Build completed successfully. Compiled image size is 9MB
18:55:18.683362: [www] Build successful for service (www)
18:55:18.780119: --> Application (app01) build is done
18:55:19.116938: --> Provisioning services' instances... (This may take a few 
minutes)
18:55:20.268328: [www] Using default scaling for service www (1 instance(s)).
18:55:30.076509: [www.0] Provisioning service (www) instance #0

It stucks here.

3. I tried it for three times, and it stucked at the same position.

The snapshot of the web page of new app and the dashboard status on dotcloud is 
following:

think@TANK:~/japlocal$ python JAP_WS_LOCAL.py
Traceback (most recent call last):
  File "JAP_WS_LOCAL.py", line 15, in <module>
    import JAP.JAP_WS_LOCAL
  File "/home/think/japlocal/JAP/JAP_WS_LOCAL.py", line 20, in <module>
    import autobahn.websocket
ImportError: No module named autobahn.websocket



any help?

I do not speak chinese, but I can help you in english?

You have to use JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT (OPENSHIFT does not work 
with JAP_WS_LOCAL_PYTHON-1.0.0).

If you have any other problems, let me know.