Stunnel/Debugging - Revision history

Admin at 05:31, 5 April 2017

2017-04-05T05:31:15Z

← Older revision		Revision as of 05:31, 5 April 2017
Line 1:		Line 1:
			=A Guide to Debugging Stunnel Connections=

			==Start with Stunnel==

	Debugging stunnel is a lot easier if you can run stunnel in the foreground in one window, and monitor its output activity while you try and connect. This is true of monitoring stunnel on both the client side and the server side.		Debugging stunnel is a lot easier if you can run stunnel in the foreground in one window, and monitor its output activity while you try and connect. This is true of monitoring stunnel on both the client side and the server side.

Line 21:		Line 25:


			==Monitor stunnel log==

			check the log via:

			<pre>
			[remote] $ tail -f /var/log/stunnel4/stunnel.log
			</pre>

			==Check your ports==

			Use nmap to scan the server and verify the external port you specified the stunnel server and client to use (443, or 273, or 8000, or whatever) should show up in the nmap scan as "open".

			If you can't reach the server, you might have a firewall issue. Fix the firewall by using iptables.

			<pre>
			#!/bin/bash
			port=443
			iptables -A INPUT -p tcp --dport ${port} -j ACCEPT
			iptables -A FORWARD -p tcp -j ACCEPT --dport ${port} -m state --state NEW
			</pre>

	=Flags=		=Flags=

Admin at 05:16, 5 April 2017

2017-04-05T05:16:36Z

← Older revision		Revision as of 05:16, 5 April 2017
Line 28:		Line 28:
	{{SSHFlag}}		{{SSHFlag}}

	[[~~Categoroy~~:Stunnel.conf]]		[[Category:Stunnel.conf]]

Admin at 05:15, 5 April 2017

2017-04-05T05:15:29Z

← Older revision		Revision as of 05:15, 5 April 2017
Line 1:		Line 1:
	Debugging stunnel is a lot easier if you can run stunnel in the foreground in one window, and monitor its output activity while you try and connect. This is true of monitoring stunnel on both the client side and the server side.		Debugging stunnel is a lot easier if you can run stunnel in the foreground in one window, and monitor its output activity while you try and connect. This is true of monitoring stunnel on both the client side and the server side.

			Just add these two lines to your stunnel.conf:

			<pre>
			debug = 7
			foreground = yes
			</pre>

			Now, when you run the stunnel command, the output will be shown directly on the screen, and you'll be able to monitor what's happening with stunnel when you try and connect.

			For example stunnel.conf files, see the following links:
			* https://git.charlesreid1.com/docker/d-stunnel
			* https://git.charlesreid1.com/rpi/pi-stunnel
			* https://git.charlesreid1.com/mac/m-stunnel

			There are also some wiki files with config files:
			* https://charlesreid1.com/wiki/Stunnel/Rsync
			* https://charlesreid1.com/wiki/Stunnel/SSH
			* https://charlesreid1.com/wiki/Stunnel/Scp


Line 8:		Line 27:

	{{SSHFlag}}		{{SSHFlag}}

			[[Categoroy:Stunnel.conf]]

Admin: Created page with "Debugging stunnel is a lot easier if you can run stunnel in the foreground in one window, and monitor its output activity while you try and connect. This is true of monitoring..."

2017-04-05T05:11:58Z

Created page with "Debugging stunnel is a lot easier if you can run stunnel in the foreground in one window, and monitor its output activity while you try and connect. This is true of monitoring..."

New page

Debugging stunnel is a lot easier if you can run stunnel in the foreground in one window, and monitor its output activity while you try and connect. This is true of monitoring stunnel on both the client side and the server side.

=Flags=

{{StunnelFlag}}

{{SSHFlag}}