Skip to content
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

Doesnt work with Chrome HTTPS on OSX #363

Open
avboy72 opened this issue Jan 8, 2018 · 3 comments
Open

Doesnt work with Chrome HTTPS on OSX #363

avboy72 opened this issue Jan 8, 2018 · 3 comments

Comments

@avboy72
Copy link

avboy72 commented Jan 8, 2018

OSX 10.13.2

After following the https instructions....

When I try to use with Chrome, I cant access any https sites. Just says "The site cant be reached".

If I open the developer console in James, I see the following error:

index.js:46792 hoxy error:  Error: Invalid openssl exit code: 1
% openssl genrsa -rand /var/log/mail:/var/log/messages 2048
usage: genrsa [args] [numbits]
 -des            encrypt the generated key with DES in cbc mode
 -des3           encrypt the generated key with DES in ede cbc mode (168 bit key)
 -aes128, -aes192, -aes256
                 encrypt PEM output with cbc aes
 -camellia128, -camellia192, -camellia256
                 encrypt PEM output with cbc camellia
 -out file       output the key to 'file
 -passout arg    output file pass phrase source
 -f4             use F4 (0x10001) for the E value
 -3              use 3 for the E value
 -engine e       use engine e, possibly a hardware device.


    at done (file:///Applications/James.app/Contents/Resources/app.asar/index.js:46196:30)
    at ChildProcess.<anonymous> (file:///Applications/James.app/Contents/Resources/app.asar/index.js:46213:13)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:850:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:492:12)`
@avboy72
Copy link
Author

avboy72 commented Jan 8, 2018

James 1.5.0

@avboy72
Copy link
Author

avboy72 commented Jan 8, 2018

Found your 2.0.0 beta 3 tag and tried it. Confirmed that Chrome works in that build. ( Note, that Safari doesnt proxy at all in that build, and Firefox doesnt proxy HTTPS )

@mitchhentges
Copy link
Member

Huh, that's bizarre. Thanks for showing the console, that sheds some light - hoxy is choking on SSL? Hmm.
We're going to release 2.0.0 soon. If, like beta.3, that release also doesn't have this issue, then let's close this ticket. Otherwise, we'll look into further investigation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants