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

Untrusted SSL not working ? #247

Open
fculpo opened this issue Jun 15, 2013 · 5 comments
Open

Untrusted SSL not working ? #247

fculpo opened this issue Jun 15, 2013 · 5 comments

Comments

@fculpo
Copy link
Contributor

fculpo commented Jun 15, 2013

I didn't manage to connect to my personal UnrealIRCd serving a self signed / invalid ssl cert.
Subway just hangs at the login screen with the loading gif...

Trusted SSL like freenode are OK (but you knew that already :) )

@gyng
Copy link

gyng commented Jun 25, 2013

I think this might be related:

Subway crashes when I try to connect to some IRC servers with SSL enabled (self-signed or not). For some other servers with SSL it just hangs like in the first post, without any useful info in the console output. However, Freenode SSL works! Non-SSL connections also work fine.

Using node.js v0.10.12 on an Ubuntu box.
npm list

Output when it crashes:

user@box:/opt/subway# ./subway
   info  - socket.io started
Subway started on port 3000
Can't resolve image path: ../img/glyphicons-halflings.png
Can't resolve image path: ../img/glyphicons-halflings-white.png
Can't resolve image path: /assets/images/join.png
Can't resolve image path: /assets/images/part.png
Can't resolve image path: /assets/images/topic.png
Can't resolve image path: /assets/images/active.png
Can't resolve image path: /assets/images/idle.png
   debug - served static content /socket.io.js
   debug - client authorized
   info  - handshake authorized PPFN0A-ZJfPqGRywe12N
   debug - setting request GET /socket.io/1/websocket/PPFN0A-ZJfPqGRywe12N
   debug - set heartbeat interval for client PPFN0A-ZJfPqGRywe12N
   debug - client authorized for
   debug - websocket writing 1::
   debug - emitting heartbeat for client PPFN0A-ZJfPqGRywe12N
   debug - websocket writing 2::
   debug - set heartbeat timeout for client PPFN0A-ZJfPqGRywe12N
   debug - got heartbeat packet
   debug - cleared heartbeat timeout for client PPFN0A-ZJfPqGRywe12N
   debug - set heartbeat interval for client PPFN0A-ZJfPqGRywe12N
Restoring connection 1...
node: ../src/node_object_wrap.h:61: static T* node::ObjectWrap::Unwrap(v8::Handle<v8::Object>) [with T = node::crypto::Connection]: Assertion `handle-    >InternalFieldCount() > 0' failed.
Aborted

@cwc
Copy link
Contributor

cwc commented Aug 12, 2013

FWIW, I've been connecting to a server that does self-signed SSL for awhile, so it definitely works in at least some cases.

@fculpo fculpo closed this as completed Aug 13, 2013
@fculpo fculpo reopened this Aug 13, 2013
@Preston4tw
Copy link

Also having this issue. nodejs 0.10.16-1 on cent6 x64 from epel. Self signed SSL cert with IRC server inspircd 2.0.13, not sure to what extent that's relevant.

@subterfugium
Copy link

I'm having same issue with node 0.10.21 and ZNC bouncer...

@tlaundal
Copy link
Contributor

tlaundal commented Feb 9, 2014

I'm having the same issue. Running a ZNC bouncer with certificate signed by private CA.
Symptoms are exactly the same as fculpo reports.

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

No branches or pull requests

7 participants