how can i run jap-ws on win7 without installing py2.7

GoogleCodeExporter commented 8 years ago

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？

Original issue reported on code.google.com by ablmdr...@gmail.com on 22 Jan 2013 at 3:00

GoogleCodeExporter commented 8 years ago

Ofcourse :)

After translating the wiki with google translate, I think you need to configure 
JAP like APPP.
- copy to misc:
  - JAP_WS_LOCAL.py
  - JAP_WS_LOCAL.json
  - JAP/__init__.py
  - JAP/JAP_LOCAL.py
  - JAP/JAP_WS_LOCAL.py
  - JAP/TUNNEL.py
- configure JAP_WS_LOCAL.json
- configure config.py
from plugins import third
third=install('third', third)
third.run('JAP_WS_LOCAL.py', wait=5)

Original comment by jeroen.v...@gmail.com on 22 Jan 2013 at 7:01

GoogleCodeExporter commented 8 years ago

JAP needs PYTHON, TWISTED, PYOPENSSL and AUTOBAHN.

Original comment by jeroen.v...@gmail.com on 22 Jan 2013 at 7:10

GoogleCodeExporter commented 8 years ago

I know how to configure APPP，but APPP doesn't support https.
If you can develop a python version for apjp that supports https， it would be 
perfect.

Now my problem is how to add PYTHON, TWISTED, PYOPENSSL and AUTOBAHN to 
wallproxy and make it a protable one. Wallproxy has python and pyopenssl 
itself. I would appreciate that if you can tell me how to deal with the others?

Original comment by ablmdr...@gmail.com on 23 Jan 2013 at 4:34

GoogleCodeExporter commented 8 years ago

I could add HTTPS support for APPP.

You have to create WALLPROXY/local/python.exe with support for TWISTED and 
AUTOBAHN. I do not know how to do that (there is no build script in the 
WALLPROXY source).
Or you can use PORTABLE PYTHON (http://www.portablepython.com/) and install all 
modules for JAP and WALLPROXY.

Original comment by jeroen.v...@gmail.com on 23 Jan 2013 at 8:42

GoogleCodeExporter commented 8 years ago

It seems that twisted is the problem.

Cause after I copy the folders twisted, zope and autobahn to the same place as 
python.exe, the prints "No module name zope.interface" never come again but the 
prints "No module name twisted.internet" still shows!

Could you please upload the right-needed twisted folder here and I will try 
again?

Original comment by ablmdr...@gmail.com on 23 Jan 2013 at 9:07

GoogleCodeExporter commented 8 years ago

so glad to hear such exciting news!

i will dig it further myself and i am waiting for ur good news about https for 
appp!

Original comment by ablmdr...@gmail.com on 23 Jan 2013 at 9:11

GoogleCodeExporter commented 8 years ago

Maybe you need to copy twisted/zope/autobahn in misc?

Original comment by jeroen.v...@gmail.com on 23 Jan 2013 at 9:13

GoogleCodeExporter commented 8 years ago

ok, i will try it tonight 
it's supper time here in China
thanks!

Original comment by ablmdr...@gmail.com on 23 Jan 2013 at 9:16

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

unfortunately， i had try my best！
now i have to use the win version

looking forward to the new appp that supports https
thanks anyway

Original comment by ablmdr...@gmail.com on 23 Jan 2013 at 1:02

GoogleCodeExporter commented 8 years ago

Wallproxy is already compiled with pyopenssl and gevent. Maybe you can ask the 
author of wallproxy to compile wallproxy with twisted, zope.interface, autobahn 
and pycrypto support (then you can add JAP_SSH_LOCAL_PYTHON and 
JAP_WS_LOCAL_PYTHON as plugins)?

Installing Python Portable is not an option?

Original comment by jeroen.v...@gmail.com on 23 Jan 2013 at 7:48

GoogleCodeExporter commented 8 years ago

APPP with HTTPS supported can rescue APPP to connect to GAE remote.Now it's 
reset in the first handshake.
GAE is the fastest and best platform to f*ck GFW.

Original comment by westmin...@gmail.com on 24 Jan 2013 at 1:49

GoogleCodeExporter commented 8 years ago

@12 
The Portable Python have not twisted, zope.interface and autobahn either. I 
konw that Wallproxy is already compiled with pyopenssl and gevent and the 
author have told me the way to compile wallproxy with twisted, zope.interface 
and autobahn. But the problem is that I have failed to compile wallproxy with 
twisted. I have no idea why twisted is so hard to succeed while the others are 
easy.

Owning to some reasons the author of Wallproxy will not compile Wallproxy in 
this way and now I don't know how to do next so I can only hope that appp with 
https will works!

Original comment by ablmdr...@gmail.com on 24 Jan 2013 at 4:23

GoogleCodeExporter commented 8 years ago

@13
everybody knows GAE is the fastest and best platform to fuck GFW but maybe 
someone is not just wanna fuck GFW for GFW. they still have a lot to do with 
such excellent tools!

Original comment by ablmdr...@gmail.com on 24 Jan 2013 at 4:27

GoogleCodeExporter commented 8 years ago

You can download
Portable Python 2.7.3.2
+ autobahn 0.5.9
+ gevent 0.13.8
+ pyasn1 0.1.6
+ pycrypto 2.6
+ pyopenssl 0.13
+ twisted 12.3.0
+ zope.interface 4.0.3
here: http://code.google.com/p/jap/downloads/list

I have attached wallproxy with JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT-2 and 
JAP_SSH_LOCAL_PYTHON-2.0.0-SNAPSHOT-2.
I updated JAP_WS_LOCAL_PYTHON.py and JAP_SSH_LOCAL_PYTHON.py:

- reactor.run()
+ if not reactor.running:
+    reactor.run(installSignalHandlers=False)

You have to configure JAP_WS_LOCAL.json and JAP_SSH_LOCAL.json.

Can you test?

Original comment by jeroen.v...@gmail.com on 24 Jan 2013 at 8:29

Attachments:

wallproxy.zip

GoogleCodeExporter commented 8 years ago

I 've tested you patch and it works perfectly!

But when i put the folders twisted, autobahn and zope from 
..\Portable_Python_2.7.3.2\App\Lib\site-packages to python.zip, the same 
situation happens again!

The author of wallproxy said that it will work!
I doubt whether if I put the folders in the right dir!
Maybe it's did it in a wrong way!
I will ask the author of wallproxy and dig it deeper!

Original comment by ablmdr...@gmail.com on 24 Jan 2013 at 10:50

GoogleCodeExporter commented 8 years ago

Have you tested Portable Python 2.7.3.2 + wallproxy with 
JAP_WS_LOCAL_PYTHON-2.0.0-SNAPSHOT-2 and JAP_SSH_LOCAL_PYTHON-2.0.0-SNAPSHOT-2?
That works?

Original comment by jeroen.v...@gmail.com on 24 Jan 2013 at 10:56

GoogleCodeExporter commented 8 years ago

yeah, it works without any problem!
now i want to patch them to the origin wallproxy because in this way it is much 
more portable and the gui mode is so charming to me!

Original comment by ablmdr...@gmail.com on 24 Jan 2013 at 11:21

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

now twisted is ok and here are the new problems

Original comment by ablmdr...@gmail.com on 24 Jan 2013 at 2:06

Attachments:

QQ截图20130124220112.png

GoogleCodeExporter commented 8 years ago

First, the new Wallproxy is not as safe as original Wallproxy-plugins, 
unencrypted, using pac file or autuproxy, using direct IP to watch Youtube 
Live. JAP focuses on safety with SSH/WS and HTTPS. I don't agree to use JAP as 
a plugin of it.JAP should be independence from other JaaS based proxy tools.
Second, the f*cking GFW is smarter then ever that can analyze flow to block 
selectively.JAP should be used in a small group not to attract the GFW's dogs.

Original comment by westmin...@gmail.com on 24 Jan 2013 at 2:35

GoogleCodeExporter commented 8 years ago

mostly, i don't use these tools to f*uck gfw, but i feel grateful that we have 
such tools so i want to mix them up and i can take good advantage of them in 
the same time without opening serveral applications!

Anyway, thank you very much and sorry for troubling your time!

Original comment by ablmdr...@gmail.com on 24 Jan 2013 at 3:08

GoogleCodeExporter commented 8 years ago

omg, i mistook you as jeroen

Original comment by ablmdr...@gmail.com on 24 Jan 2013 at 3:30

GoogleCodeExporter commented 8 years ago

@westminboy, @ablmdream 
The JAP project is not a part of the WALLPROXY project, but you can use JAP 
however you want (JAP has a GNU GPL v2 license).
You can also contribute to the JAP project: code, wiki, issues, ..

Original comment by jeroen.v...@gmail.com on 24 Jan 2013 at 6:45

GoogleCodeExporter commented 8 years ago

ok，thanks

Original comment by ablmdr...@gmail.com on 25 Jan 2013 at 2:56

GoogleCodeExporter commented 8 years ago

I have added HTTPS support to APPP: https://github.com/jvansteirteghem/appp

Original comment by jeroen.v...@gmail.com on 30 Jan 2013 at 3:07

GoogleCodeExporter commented 8 years ago

@jaroen #27
Thanks,but still can't connect to GAE,no matter use domain or IP.
[gae]
CUSTOM_HEADER1=Host: myappid.appspot.com
HTTP_URL=https://google_domain_or_IP/HTTP
HTTPS_URL=https://gmail_domain_or_IP/HTTPS

Original comment by westmin...@gmail.com on 31 Jan 2013 at 1:30

GoogleCodeExporter commented 8 years ago

I have tested APPP with

[EXAMPLE]
CUSTOM_HEADER1=Host: XXX.appspot.com
HTTP_URL=https://www.gmail.com/HTTP
HTTPS_URL=https://www.gmail.com/HTTPS

and I have no problems.
Maybe GFW blocks by User-Agent (APPP_UA)?

Original comment by jeroen.v...@gmail.com on 31 Jan 2013 at 1:50

GoogleCodeExporter commented 8 years ago

TO west...
1. Jeroen just added the support of HTTPS for proxy, which maybe not be fully 
able to cheat GFW.
2. You are supposed to think APPP as the Python version of APJP, no more or no 
less. If APJP works and APPP not, then we should spend some time figuring out 
what's wrong.
3. APPP works with GAE, only if you could figure out the usable domains or IPs. 
So does APJP.
4. I have tested APPP with GAE, it works, however, not stable because of the 
disturbing of GFW.
5. http://www.google.com/supported_domains and 
http://www.google.com/intl/en_ALL/ipv6/statistics/data/no_aaaa.txt would be 
useful to figure out the stable domains or IPs without the disturbing of GFW.
6. Or you get them from GoAgent like Tintin... said 
"我找到goagent的ini文件里的google https 的ip，在apjp gae里request 
url 填上https://203.208.46.131/2/.../9就可以用了。问题已解决" ( 
http://code.google.com/p/apjp/issues/detail?id=147#c2 )
7. A little more explanations about stable things ( 
http://code.google.com/p/apjp/issues/detail?id=147#c4 ).

Original comment by goknmuse on 1 Feb 2013 at 11:17

Changed state: Started

GoogleCodeExporter commented 8 years ago

it works fine with https support！
however，it still can't attach to https://www.google.com, 
https://mail.google.com ...

Original comment by ablmdr...@gmail.com on 2 Feb 2013 at 6:47

GoogleCodeExporter commented 8 years ago

the output is:

Original comment by ablmdr...@gmail.com on 2 Feb 2013 at 10:18

Attachments:

QQ截图20130202181724.png

GoogleCodeExporter commented 8 years ago

it don`t work in wallproxy.
the output is :
------------------------------------------------------------------------------
Welcome to use wallproxy, Copyright (C) 2009-2012 HustMoon Studio
Version: wallproxy/2.1.14 (python/2.7.3, gevent/1.0rc2)
Listen : 127.0.0.1:8086
------------------------------------------------------------------------------
Initializing fake CA for https2http:
  Please make sure you have imported "C:\Program Files (x86)\WallProxy-Plus\loca
l\local\cert\CA.crt" to the Trusted root CA list for your browser.
  CA Information: WallProxy CA (2013-01-31 23:12:57 - 2033-01-31 23:12:57)
  Wildcard Certificate: YES
Initializing UrlFetch for url fetch:
  Debug level: 0
  Global timeout: 60.0
  Use keep alive: YES
Initializing Utility for proxy-auth, hosts, forward.
  Forward timeout: 60.0
  Remote DNS: 8.8.8.8 (TCP,3,L)
Initializing PAAS for proxy based on cloud service.
  Init GAE with appids: XXXXXXXXXXX
  max_threads when range fetch: 4
  GAE listen on: 127.0.0.1:8087
Initializing PAC for proxy auto-config.
  RuleList: k0|0|0+h0:0|4:5|4:5+r0|0|0=10 rules from string.
  RuleList: k0|0|0+h0:0|0:0|8:9+r0|0|1=10 rules from string.
  RuleList: k0|0|0+h0:0|0:0|1:1+r0|0|0=1 rules from string.
  RuleList: k0|0|0+h0:0|0:0|3:5+r0|0|0=5 rules from string.
  RuleList: k0|0|0+h0:0|0:0|1:3+r0|0|0=3 rules from string.
  RuleList: k0|0|0+h0:0|0:0|6:8+r0|0|0=8 rules from string.
  RuleList: schedule to load rules from "https://autoproxy-gfwlist.googlecode.co
m/svn/trunk/gfwlist.txt, userlist.ini".
------------------------------------------------------------------------------
Initializing third for other python applications.
18:41:03 APPP[Dummy-2] INFO: Attempting to run all APPP servers defined in APPP.
ini
02-02 18:41:03  __main__ INFO  Attempting to run all APPP servers defined in APP
P.ini
18:41:03 APPP[Dummy-2] INFO: Processing [EXAMPLE] configurations
02-02 18:41:03  __main__ INFO  Processing [EXAMPLE] configurations
18:41:03 APPP[Dummy-2] INFO: Processing [EXAMPLE-PROXY] configurations
02-02 18:41:03  __main__ INFO  Processing [EXAMPLE-PROXY] configurations
18:41:03 APPP[Dummy-2] INFO: Checking APPP certificates...
02-02 18:41:03  __main__ INFO  Checking APPP certificates...
18:41:03 APPP[Dummy-2] INFO: APPP certificates OK.
02-02 18:41:03  __main__ INFO  APPP certificates OK.
18:41:03 APPP[EXAMPLE-PROXY] INFO: Listening on 127.0.0.1:10001.
02-02 18:41:03  __main__ INFO  Listening on 127.0.0.1:10001.
18:41:03 APPP[EXAMPLE] INFO: Listening on 127.0.0.1:10000.
02-02 18:41:03  __main__ INFO  Listening on 127.0.0.1:10000.
18:41:03 APPP[EXAMPLE-PROXY-TEST] INFO: Testing APPP connectivity to http://mail
.google.com
02-02 18:41:03  __main__ INFO  Testing APPP connectivity to http://mail.google.c
om
18:41:03 APPP[EXAMPLE-PROXY-TEST] INFO: Testing APPP connectivity to https://mai
l.google.com
02-02 18:41:03  __main__ INFO  Testing APPP connectivity to https://mail.google.
com
18:41:03 APPP[EXAMPLE-PROXY-55452976] INFO: Received connection from 127.0.0.1:5
3912
02-02 18:41:03  __main__ INFO  Received connection from 127.0.0.1:53912
18:41:03 APPP[EXAMPLE-PROXY-55453056] INFO: Received connection from 127.0.0.1:5
3913
02-02 18:41:03  __main__ INFO  Received connection from 127.0.0.1:53913
18:41:03 APPP[EXAMPLE-TEST] INFO: Testing APPP connectivity to https://mail.goog
le.com
02-02 18:41:03  __main__ INFO  Testing APPP connectivity to https://mail.google.
com
18:41:03 APPP[EXAMPLE-TEST] INFO: Testing APPP connectivity to http://mail.googl
e.com
02-02 18:41:03  __main__ INFO  Testing APPP connectivity to http://mail.google.c
om
18:41:03 APPP[EXAMPLE-55453136] INFO: Received connection from 127.0.0.1:53914
02-02 18:41:03  __main__ INFO  Received connection from 127.0.0.1:53914
18:41:03 APPP[EXAMPLE-55453216] INFO: Received connection from 127.0.0.1:53915
02-02 18:41:03  __main__ INFO  Received connection from 127.0.0.1:53915
Resolve 'mail.google.com' to ['74.125.128.18', '74.125.128.83', '74.125.128.19',
 '74.125.128.17'] with dns 8.8.8.8.
Resolve 'www.google.com.hk' to ['74.125.128.199'] with dns 8.8.8.8.
Resolve 'www.google-analytics.com' to ['203.208.36.1', '203.208.36.7', '203.208.
36.2', '203.208.36.9', '203.208.36.3', '203.208.36.8', '203.208.36.4', '203.208.
36.5', '203.208.36.14', '203.208.36.6', '203.208.36.0'] with dns 8.8.8.8.
------------------------------------------------------------------------------
Resolve 'www.google.com' to ['74.125.128.103', '74.125.128.99', '74.125.128.104'
, '74.125.128.106', '74.125.128.147', '74.125.128.105'] with dns 8.8.8.8.
Resolve 'talkx.l.google.com' to ['74.125.141.125'] with dns 8.8.8.8.
Resolve 'talk.google.com' to ['74.125.128.125'] with dns 8.8.8.8.
PAC RuleList result:
  https://autoproxy-gfwlist.googlecode.com/svn/trunk/gfwlist.txt: k0|0|1180+h0:0
|98:103|1246:1683+r0|0|34=3000, Wed, 30 Jan 2013 05:53:35 GMT
  userlist.ini: k0|0|0+h0:0|0:0|9:10+r0|0|0=10, Thu, 24 Jan 2013 23:14:48 GMT
  Total: k0|0|1180+h0:0|98:103|1252:1693+r0|0|34=3010
18:41:09 APPP[EXAMPLE-PROXY-TEST] ERROR: APPP connectivity test to http://mail.g
oogle.com failed: no correctly formatted response header received.
02-02 18:41:09  __main__ ERROR APPP connectivity test to http://mail.google.com
failed: no correctly formatted response header received.
18:41:09 APPP[EXAMPLE-PROXY-TEST] ERROR: APPP connectivity test to https://mail.
google.com failed: no correctly formatted response header received.
02-02 18:41:09  __main__ ERROR APPP connectivity test to https://mail.google.com
 failed: no correctly formatted response header received.
18:41:09 APPP[EXAMPLE-TEST] ERROR: APPP connectivity test to http://mail.google.
com failed: no correctly formatted response header received.
02-02 18:41:09  __main__ ERROR APPP connectivity test to http://mail.google.com
failed: no correctly formatted response header received.
18:41:09 APPP[EXAMPLE-TEST] ERROR: APPP connectivity test to https://mail.google
.com failed: no correctly formatted response header received.
02-02 18:41:09  __main__ ERROR APPP connectivity test to https://mail.google.com
 failed: no correctly formatted response header received.
18:41:24 APPP[EXAMPLE-PROXY-55452976] ERROR: Exception encountered forwarding re
quest: [Errno 10051] 
向一个无法连接的网络尝试了一个套接字操作。
02-02 18:41:24  __main__ ERROR Exception encountered forwarding request: [Errno
10051] 向一个无法连接的网络尝试了一个套接字操作。
18:41:27 APPP[EXAMPLE-PROXY-55452976] WARNING: Failed to process request from 12
7.0.0.1:53912
02-02 18:41:27  __main__ WARNING Failed to process request from 127.0.0.1:53912
18:41:27 APPP[EXAMPLE-PROXY-55453056] ERROR: Exception encountered forwarding re
quest: [Errno 10051] 
向一个无法连接的网络尝试了一个套接字操作。
02-02 18:41:27  __main__ ERROR Exception encountered forwarding request: [Errno
10051] 向一个无法连接的网络尝试了一个套接字操作。
18:41:28 APPP[EXAMPLE-PROXY-55453056] WARNING: Failed to process request from 12
7.0.0.1:53913
02-02 18:41:28  __main__ WARNING Failed to process request from 127.0.0.1:53913

Original comment by jlz19821...@gmail.com on 2 Feb 2013 at 10:42

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

can't you put the looooooooooooong output as an attachment?????????

Original comment by westmin...@gmail.com on 2 Feb 2013 at 2:52

GoogleCodeExporter commented 8 years ago

I have updated APPP: https://github.com/jvansteirteghem/appp

I have added DNS.ini:
[DNS]
appspot.com=google.be,google.com

So you do not have to configure a CUSTOM_HEADER (for example: 
CUSTOM_HEADER1=Host: XXX.appspot.com)

Original comment by jeroen.v...@gmail.com on 4 Feb 2013 at 2:23

GoogleCodeExporter commented 8 years ago

My settings:
APPP.ini
[gae]
HTTP_URL=https://myappid.appspot.com/HTTP
HTTPS_URL=https://myappid.appspot.com/HTTPS
(delete the last five lines)
DNS.ini
[DNS]
appspot.com=google.cn
Finally it works!
I love you jeroen!!
BTW,suggest you create a new Google Project Hosting for the new and reborn APPP.
Thank you.

Original comment by westmin...@gmail.com on 5 Feb 2013 at 10:50

Attachments:

success

GoogleCodeExporter commented 8 years ago

Thanks for testing!

Original comment by jeroen.v...@gmail.com on 6 Feb 2013 at 9:59

GoogleCodeExporter commented 8 years ago

@jeroen，could you have a look up at my problem at #32？
i run app with wallproxy

Original comment by ablmdr...@gmail.com on 6 Feb 2013 at 1:08

GoogleCodeExporter commented 8 years ago

How do I reproduce problem #32?

Original comment by jeroen.v...@gmail.com on 6 Feb 2013 at 1:23

GoogleCodeExporter commented 8 years ago

yeah！ can you solve it？

Original comment by ablmdr...@gmail.com on 6 Feb 2013 at 1:28

GoogleCodeExporter commented 8 years ago

I can not reproduce problem #32.
Do you have a APPP.pks and APPP.pem in your APPP directory?
Do you start APPP from your APPP directory or from another directory?
Can you retest with the latest source code: 
https://github.com/jvansteirteghem/appp (configure like #37)

Original comment by jeroen.v...@gmail.com on 6 Feb 2013 at 1:34

GoogleCodeExporter commented 8 years ago

i have put all files into the third.run dir of wallproxy
APPP.pks and APPP.pem have been generated in the same dir after the first run
then i import appp.pem

i downloaded the latest version just now and the output was not like before but 
stilled  couldnot work

Original comment by ablmdr...@gmail.com on 6 Feb 2013 at 1:55

Attachments:

GoogleCodeExporter commented 8 years ago

and my configurations:
[EXAMPLE]
# These must be defined for each server
HTTP_URL=https://xxx.cloudfoundry.com/HTTP
HTTPS_URL=https://xxx.cloudfoundry.com/HTTPS

Original comment by ablmdr...@gmail.com on 6 Feb 2013 at 1:57

GoogleCodeExporter commented 8 years ago

Have you imported APPP.pem in your browser (also delete old APPP.pem before you 
add new APPP.pem in your browser)?
Does APPP work without WALLPROXY?

Original comment by jeroen.v...@gmail.com on 6 Feb 2013 at 2:20

GoogleCodeExporter commented 8 years ago

the appp.pem is the new one

i cannot run appp alone in my sys with py2.7.3 installer or portablepython, 
maybe my configurations were not right, but according to muse gk, appp can work 
fine without wallproxy

Original comment by ablmdr...@gmail.com on 6 Feb 2013 at 3:01

GoogleCodeExporter commented 8 years ago

I do not understand chinese, so I cannot understand the error in your browser.
And yes, APPP works without WALLPROXY (APPP needs python 2.6 (or better) + 
openssl + pyopenssl).

Original comment by jeroen.v...@gmail.com on 6 Feb 2013 at 6:16

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

that’s the cert error
this error happens when appp.pem is not imported
but in fact i have imported it

i prefer to run it with wallproxy owning to some reasons
it would be better if you can fix it

Original comment by ablmdr...@gmail.com on 7 Feb 2013 at 2:35

GoogleCodeExporter commented 8 years ago

APPP generates a new APPP.pem when there is no APPP.pem in the APPP directory.
So when you install APPP, and you have an old APPP installation, you have to 
delete the APPP certificate of your old APPP installation in your browser.
Then you have to add the APPP certificate of your new APPP installation in your 
browser.

So can you:
1) delete the old APPP certificate in your browser
2) add the new APPP certificate in your browser
3) test the new APPP

Original comment by jeroen.v...@gmail.com on 7 Feb 2013 at 5:54

felixlu / jap

how can i run jap-ws on win7 without installing py2.7 #20