Сервер Ubuntu, не удающийся выполнить квитирование SSL (ssl квитируют failure:s23_lib.c),
Простой способ вокруг этого использует количество Байтов программного обеспечения Web Analyser как веб-Тенденции. Должно быть много свободных.
править-
Извините, если это не было совершенно ясно. Программное обеспечение анализатора будет считать количество пропускной способности каждого сайта и обычно упоминать это у подножия отчетов, которые оно представляет. Тем путем каждый Виртуальный сервер, т.е. сайт или субдомен, на веб-сервере получают количество запроса в МБ или Байтах.
As it turns out, the problem had nothing to do with Java and everything to do with the cable modem my ISP provided me with. My network setup is as follows:
- TP-Link TL-ER5120 serves as gateway and firewall (and link load balancer)
- Two internet links server by equal Thomson DWG874B cable modems
- One internet link served by a TL-MR3020 connected to a 3G USB modem
The 3G modem is a failover measure, really. If I routed the server traffic through the 3G modem the SSL connection would work. So the problem was either with the cable modems or the ISP itself. I use the same ISP at home (with a different cable modem) and the connection worked. So I pinned it down to the cable modem.
That cable modem is actually a wireless router as well (although wireless is disabled). The modem has a DCHP server that assigns my firewall a local IP. So my actual local network is something like 192.168.0.x, there was another network between my firewall and the cable modem, let's say 192.168.1.x, and the cable modem had a public IP address. I never really liked this setup, but it didn't seem to cause any harm so I lived with it.
The cable modem has a setting that makes it behave as a pure cable modem and assigns whatever is connecting to it the public IP from the ISP. The setting is called switch mode, as shown below (the previous setting was Legacy RG IPv4 Mode).
As soon as I used that, my SSL connections to that specific website started working again from Linux. I have no clue of what was going on, but I am glad it's fixed.