StreisandEffect / discussions

30 stars 3 forks source link

Streisand Openvpn stunnel #184

Closed zee-shany closed 4 years ago

zee-shany commented 4 years ago

Hello,

I've just setup Streisand on AWS EC2, I was able to use SSH and proxy through with Firefox. However when i try to establish Openvpn stunnel i'm getting error mentioned in the log. I've followed the instruction as it is and have also followed this youtube (https://www.youtube.com/watch?v=UGNVXtSurvQ) when setting up the Streisand.

I've had Openvpn client work before on my home network so its probably not the ISP blocking. Altho the ISP does throttle down the speed and I was getting around 2 Mb down on a 200Mb broadband connection. my ISP is Etisalat, UAE.

any help from streisand team will be highly appreciated.


Mon Jul 15 12:30:45 2019 OpenVPN 2.4.7 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Feb 21 2019 Mon Jul 15 12:30:45 2019 Windows version 6.2 (Windows 8 or greater) 64bit Mon Jul 15 12:30:45 2019 library versions: OpenSSL 1.1.0j 20 Nov 2018, LZO 2.10 Enter Management Password: Mon Jul 15 12:30:45 2019 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340 Mon Jul 15 12:30:45 2019 Need hold release from management interface, waiting... Mon Jul 15 12:30:45 2019 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340 Mon Jul 15 12:30:45 2019 MANAGEMENT: CMD 'state on' Mon Jul 15 12:30:45 2019 MANAGEMENT: CMD 'log all on' Mon Jul 15 12:30:46 2019 MANAGEMENT: CMD 'echo all on' Mon Jul 15 12:30:46 2019 MANAGEMENT: CMD 'bytecount 5' Mon Jul 15 12:30:46 2019 MANAGEMENT: CMD 'hold off' Mon Jul 15 12:30:46 2019 MANAGEMENT: CMD 'hold release' Mon Jul 15 12:30:46 2019 Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key Mon Jul 15 12:30:46 2019 Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication Mon Jul 15 12:30:46 2019 Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key Mon Jul 15 12:30:46 2019 Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication Mon Jul 15 12:30:46 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:41194 Mon Jul 15 12:30:46 2019 Socket Buffers: R=[65536->65536] S=[65536->65536] Mon Jul 15 12:30:46 2019 Attempting to establish TCP connection with [AF_INET]127.0.0.1:41194 [nonblock] Mon Jul 15 12:30:46 2019 MANAGEMENT: >STATE:1563179446,TCP_CONNECT,,,,,, Mon Jul 15 12:32:46 2019 TCP: connect to [AF_INET]127.0.0.1:41194 failed: Unknown error Mon Jul 15 12:32:46 2019 SIGUSR1[connection failed(soft),init_instance] received, process restarting Mon Jul 15 12:32:46 2019 MANAGEMENT: >STATE:1563179566,RECONNECTING,init_instance,,,,, Mon Jul 15 12:32:46 2019 Restart pause, 5 second(s) Mon Jul 15 12:32:51 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:41194 Mon Jul 15 12:32:51 2019 Socket Buffers: R=[65536->65536] S=[65536->65536] Mon Jul 15 12:32:51 2019 Attempting to establish TCP connection with [AF_INET]127.0.0.1:41194 [nonblock] Mon Jul 15 12:32:51 2019 MANAGEMENT: >STATE:1563179571,TCP_CONNECT,,,,,, Mon Jul 15 12:34:51 2019 TCP: connect to [AF_INET]127.0.0.1:41194 failed: Unknown error Mon Jul 15 12:34:51 2019 SIGUSR1[connection failed(soft),init_instance] received, process restarting Mon Jul 15 12:34:51 2019 MANAGEMENT: >STATE:1563179691,RECONNECTING,init_instance,,,,, Mon Jul 15 12:34:51 2019 Restart pause, 5 second(s) Mon Jul 15 12:34:56 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:41194 Mon Jul 15 12:34:56 2019 Socket Buffers: R=[65536->65536] S=[65536->65536] Mon Jul 15 12:34:56 2019 Attempting to establish TCP connection with [AF_INET]127.0.0.1:41194 [nonblock] Mon Jul 15 12:34:56 2019 MANAGEMENT: >STATE:1563179696,TCP_CONNECT,,,,,, Mon Jul 15 12:36:17 2019 SIGTERM[hard,init_instance] received, process exiting Mon Jul 15 12:36:17 2019 MANAGEMENT: >STATE:1563179777,EXITING,init_instance,,,,,

zee-shany commented 4 years ago

apologies, i guess i found the issue. I had pasted the stunnel.conf file straight under stunnel folder as per instruction on streisand, instead of the sub-folder config . after pasting the stunnel.conf file in sub-folder named config. the connection was established right away.