stunnel | Simple SOCKS5/HTTP tunnel | Proxy library

i have a problem with a script, when is executed from cron the script does not work as expected but when i execute it from ssh it runs as is supposed.

Setup: QNAP NAS

The script that i'm trying to run:

Using sTunnel with QuickFix C++: To login to the LMAX UAT over SSL-internet and send FIX 4.2 messages over a TCP connection. Another similar SO question can be found here, but doesn't appear to solve this particular issue.

OS: Ubuntu 19.10 | sTunnel version: 5.55 | Engine: quickfix-1.15.1 | Venue: LMAX [UAT-LD4]

Cannot login to the UAT. After starting sTunnel and then running the client application which first sends a LOGON message, no authentication is received. LMAX have said the client server public IP addr has been whitelisted.

*Configs found further below. When trying to login:

I have a cron job that runs dehydrated to renew Let's Encrypt certificates on my QNAP webserver.

I want it to fetch the current vhosts file that is generated by QNAP, get the section for the actual site, and then replace that information with correct certificate data.

Here is a section of the vhosts-file:

i'm working on a chat application using django Channels and reconnecting-web-socket the app works fine locally but when deployed to heroku the site works fine but the web socket closes before connection is established and sometimes it works fine.

it tries to connect and says websocket open and established

!!JUST WRITING THIS POST SO THAT SOMEONE CAN SAVE HOURS IN THIS!!

I tried a hell lot to install this "stunnel" but was unable to do so I was in my cpanel's terminal

What I tried all with 'sudo'

I'm trying to figure out the way docker handles commands presented to it.

For example if I run this the JS app starts fine.

I would like to set up a basic 3-node Redis Sentinel setup using the new TLS features of Redis 6. Unfortunately, it doesn't seem like Redis 6 Sentinel is smart enough to speak TLS to clients.

Does anyone know of a way to do this, or if it's not possible, if there are any mentions online about adding support for this in the future? It seems a shame to have these nice TLS features and not be able to use them with Redis' own tools.
I am aware that in the past people have used Stunnel to do this. With TLS support added to Redis, I am only interested in doing this if it can be done without third party addtions.

My setup:
3 Redis servers (6.0-rc, last pulled last week), running TLS with the test certs as specified in the Redis docs - one master and 2 replicas
3 Sentinels (6.0-rc, also last pulled last week), not running TLS on their ports (I would like to, but that's a secondary problem)

What I've Tried:

1. Pointing Sentinel to the Redis TLS port - this results in lots of TLS errors in Redis' logs about incorrect TLS version received, as Sentinel is not speaking TLS to Redis. Since it fails, Sentinel thinks the master is down.

2. Adding "https://" in the Sentinel config in front of the master IP - this results in Sentinel refusing to run, saying it can't find the master hostname.

3. Adding TLS options to Sentinel - this results in Sentinel trying to talk TLS on its ports, but not to clients, which doesn't help. I couldn't find any options specifically about making Sentinel speak TLS to clients.

4. Pointing Sentinel to the Redis not-TLS port (not ideal, I would rather only have the TLS port open) - this results in Sentinel reporting the wrong (not-TLS) port for the master to the simple Python client I'm testing with (it literally just tries to get master info from Sentinel) - I want the client to talk to Redis over TLS for obvious reasons

5. Adding the "replica-announce-port" directive to Redis with Sentinel still pointed to the not-TLS port - this fails in 2 ways: the master port is still reported incorrectly as the not-TLS port (seems to be because the master is not a replica and so the directive does not apply), and Sentinel now thinks the replicas are both down (because the TLS port is reported, replicas are auto discovered, and it can't speak to the replicas on the TLS port).

I am aware of this StackOverflow question (Redis Sentinel and TLS) - it is old and asks about Redis 4, so it's not the same.

In a TLS communication I always thought the server would send the public certificate to the client during the handshake process.

However, I received a request from a provider asking us to manually install a certificate in order to initiate a TLS communication with one of their STunnel server.

I'm a bit confuse by this request. Is there's a situation where TLS server would not be able to send the certificate to the client and therefore required a manuel certificate installation?

I've got a dropwizard app, which runs fine with the standard JRE.

I've tried creating a runtime using jlink which is considerably smaller: