Revision as of 05:15, 5 April 2017

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:

debug = 7
foreground = yes

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:

There are also some wiki files with config files:

Flags

Categoroy:Stunnel.conf

@@ 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.
+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}}
+[[Categoroy:Stunnel.conf]]

Stunnel/Debugging: Difference between revisions

From charlesreid1

Revision as of 05:15, 5 April 2017

Flags