主页 / server / 问题 / 479074
Accepted
lacrosse1991
Asked: 2013-02-15 17:02:55 +0800 CST

为什么 stunnel 这样做

  • 772

我正在尝试设置 stunnel 来加密来自 rsyslog 的流量（使用 relp 协议），但是每当我尝试启动 stunnel 并将日志发送到远程服务器时，我都会得到以下信息：

    Remote socket (FD=13) closed
    Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Local socket (FD=3) closed
    Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Service [ssyslog] finished (0 left)
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316320512]: Service [ssyslog] accepted (FD=3) from 127.0.0.1:42481
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Service [ssyslog] started
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Waiting for a libwrap process
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Acquired libwrap process #0
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Releasing libwrap process #0
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Released libwrap process #0
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Service [ssyslog] permitted by libwrap from 127.0.0.1:42481
Feb 15 01:25:55 ruby stunnel: LOG5[26750:140598316271360]: Service [ssyslog] accepted connection from 127.0.0.1:42481
Feb 15 01:25:55 ruby stunnel: LOG6[26750:140598316271360]: connect_blocking: connecting 98.235.203.58:60514
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: connect_blocking: s_poll_wait 98.235.203.58:60514: waiting 10 seconds
Feb 15 01:25:55 ruby stunnel: LOG5[26750:140598316271360]: connect_blocking: connected 98.235.203.58:60514
Feb 15 01:25:55 ruby stunnel: LOG5[26750:140598316271360]: Service [ssyslog] connected remote server from 78.46.65.138:43235
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: Remote socket (FD=13) initialized
Feb 15 01:25:55 ruby stunnel: LOG7[26750:140598316271360]: SNI: host name: xx.xx.xx.xx
Feb 15 01:25:55 ruby stunnel: LOG3[26750:140598316271360]: SSL_connect: Peer suddenly disconnected
Feb 15 01:25:55 ruby stunnel: LOG5[26750:140598316271360]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket

一遍又一遍地快速连续，有谁知道我怎么能弄清楚是什么导致了这种情况发生？在过去的几个小时里，我一直在努力解决这个问题，但现在还不知道该怎么做

ssl

2 个回答

  1. Best Answer

    好的，在谷歌上进行了多次咒骂和无果而终的搜索之后，我能够找出它是什么。不确定我是否只是个白痴，或者这是否正常，但远程服务器正在侦听端口（例如 60000）但出于某种原因，即使我已经告诉客户端连接到60000，它一直试图连接到 60001，所以我只需要告诉客户端连接到端口 59999，它就完美地工作了:)

    • 1

  2. 编辑：此处不适用，但如果您在尝试为 http/https 调试类似问题时偶然发现此线程：确保在浏览器/客户端中输入 https 而不是 http。当有人访问 http 时，Stunnel 不会自动重定向到 https

    • -3

相关问题