2 copy the included files into /etc in the same hierarchy structure, which is:
8 etc/stunnel/stunnel.conf
12 chmod 755 /etc/init.d/stunnel
16 modify /etc/stunnel/stunnel.conf to represent your desired tunneling
17 configuration. the example turns a trac install on localhost with standard
18 http protocol into a TLS version on the https protocol.
20 run this command to get stunnel registered:
22 sudo /sbin/chkconfig --add stunnel
24 afterwards the service should start with:
26 /etc/init.d/stunnel start
28 if problems result from starting the service:
30 + maybe you need to fix the path in the /etc/init.d/stunnel script.
32 "which stunnel" (or "whence stunnel")
33 and updating the script with the path shown for stunnel.
35 + maybe there's a port conflict from another service?
36 check with the configuration files or ask the system administrators for
37 assistance. the telnet tool will connect to an arbitrary tcp service and
38 inform you if the connection succeeded, e.g. "telnet myhost 23230".
39 if it says "Connected to ...." then the connection was successful,
40 regardless of the type of tcp protocol actually on that port. if that
41 reports instead "unable to connect to remote host", then no answer was
42 received. if the telnet session just says "Trying ...." and never comes
43 back or takes a really long time, then a firewall may be blocking the
44 port or the machine may be down.