SSL (stunnel) not connecting

Visto 57 veces
Saltar al primer mensaje no leído

Fedot Serghei

no leída,
3 feb 2015, 17:54:263/2/15
a ratch...@googlegroups.com
Hello,
My push server works perfectly under http but under https i get request timed out.

After researching I setup my stunnel like this

[websockets]
accept = 8443
connect = 8080

but still not connecting

here is my stunnel logs


2015.02.04 00:46:51 LOG7[27768:139904013739968]: websockets accepted FD=20 from 95.76.165.236:57330
2015.02.04 00:46:51 LOG7[27768:139904013596416]: websockets started
2015.02.04 00:46:51 LOG7[27768:139904013596416]: FD 20 in non-blocking mode
2015.02.04 00:46:51 LOG7[27768:139904013596416]: Waiting for a libwrap process
2015.02.04 00:46:51 LOG7[27768:139904013596416]: Acquired libwrap process #0
2015.02.04 00:46:51 LOG7[27768:139904013596416]: Releasing libwrap process #0
2015.02.04 00:46:51 LOG7[27768:139904013596416]: Released libwrap process #0
2015.02.04 00:46:51 LOG7[27768:139904013596416]: websockets permitted by libwrap from 95.76.165.236:57330
2015.02.04 00:46:51 LOG5[27768:139904013596416]: websockets accepted connection from 95.76.165.236:57330
2015.02.04 00:46:51 LOG7[27768:139904013596416]: FD 21 in non-blocking mode
2015.02.04 00:46:51 LOG6[27768:139904013596416]: connect_blocking: connecting 0.0.0.0:8080
2015.02.04 00:46:51 LOG7[27768:139904013596416]: connect_blocking: s_poll_wait 0.0.0.0:8080: waiting 10 seconds
2015.02.04 00:46:51 LOG5[27768:139904013596416]: connect_blocking: connected 0.0.0.0:8080
2015.02.04 00:46:51 LOG5[27768:139904013596416]: websockets connected remote server from 127.0.0.1:39848
2015.02.04 00:46:51 LOG7[27768:139904013596416]: Remote FD=21 initialized
2015.02.04 00:46:51 LOG7[27768:139904013596416]: SSL state (connect): before/connect initialization
2015.02.04 00:46:51 LOG7[27768:139904013596416]: SSL state (connect): SSLv3 write client hello A

I stopped firewall.

Some sugestions please?

keith.r...@roofdiagnostics.com

no leída,
12 abr 2015, 20:51:2112/4/15
a ratch...@googlegroups.com
Have you tried setting your connect to localhost:8080?
Responder a todos
Responder al autor
Reenviar
0 mensajes nuevos