Ajiq,
On 12/3/19 09:13, Ajjq . wrote:
Hi Christopher:
You are right. I needed C:> TELNET LOCALHOST 80 and expect to be connected to sub.dominio.com:443
I modified stunnel.conf with client=yes. I am including stunnel.con and log.
I created the service Stunnel service, but when I start it, I get this error message.
[Stunnel server is down due to an error. You need to exit and correct
the problem. Click OK to see the error log window.]
The screenshot shows an error "bind: Address already in use".
Do you have stunnel running twice at once?
Please stop stunnel, delete your log file, then start it again. Post the resulting log file to the mailing list.
-chris
stunnel.conf
debug = 7 output = stunnel3.log
; TLS front-end to a web server [https] client=yes accept = 127.0.0.1:80 connect = subd.dominio.com:443 cert = stunnel.pem TIMEOUTclose = 0
Is TIMEOPUTclose=0 actually on one line? That might be a syntax error.
-chris
On Tue, Dec 03, 2019 at 09:42:10AM -0500, Christopher Schultz wrote:
Ajiq,
On 12/3/19 09:13, Ajjq . wrote:
[snip]
stunnel.conf
debug = 7 output = stunnel3.log
; TLS front-end to a web server [https] client=yes accept = 127.0.0.1:80 connect = subd.dominio.com:443 cert = stunnel.pem TIMEOUTclose = 0
Is TIMEOPUTclose=0 actually on one line? That might be a syntax error.
Erm, no, "TIMEOUTclose" is a valid stunnel configuration option.
G'luck, Peter