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

Connect gets EPERM #27

Closed
daknob opened this issue Jan 19, 2015 · 3 comments
Closed

Connect gets EPERM #27

daknob opened this issue Jan 19, 2015 · 3 comments

Comments

@daknob
Copy link

daknob commented Jan 19, 2015

The script fails to access a few hosts by reporting EPERM on connect() while they are accessible, although usually have HTTPS errors like NET::ERR_CERT_AUTHORITY_INVALID, 403:FORBIDDEN, ERR_SSL_PROTOCOL_ERROR, HTTP-META-REDIRECT, ERR_CERT_COMMON_NAME_INVALID. There are also sites that cause this problem that are perfectly fine and accessible through a web browser (even Firefox).

For the hosted copy that has these errors live, see https://httpswatch.daknob.net/

@daknob
Copy link
Author

daknob commented Jan 19, 2015

The certificate-related issues can be accepted as possible causes since they are probably caused because you supply the moz-certs.pem in the library directly. The HTTP related ones though do not really make much sense..
If only there was a way to better identify the error and print that instead of a simple EPERM on connect().

@benjaminp
Copy link
Owner

This should be fixed now.

@daknob
Copy link
Author

daknob commented Jan 19, 2015

Okay, now sites do not show up as EPERM when failing. The problem still remains as described in issue #16 though.

@daknob daknob closed this as completed Jan 19, 2015
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