Once created, the certificates are stored in /etc/letsencrypt/live/. Which will ask for additionnal parameters. opt/letsencrypt/letsencrypt-auto -apache -d -d or more simply: ("-depth=1" says not to download the full history").Ĭertificates are produced with the command: To obtain certificates, you must first download and install git then letsencrypt. On the first occurence, or after a significant activity interruption, the super-user password will be requested. Alternatively, all commands can be prefixed with sudo. This is achieved by typing sudo -s for Ubuntu or su root for Debian, followed by the super-user password. nano will be the preferred etxt editor, but vi or any other editor of your choice can be used.Ĭommands are executed in super-user root mode. domaine or Example:Īll commands in this tutorial are issued from a terminal window. Geneweb must be installed in CGI mode behind an Apache server, or directly in service or daemon mode, listening on port 2317 (in our example). At this time (01/17) it is not usable under macOS. It is most likely valid for other Linux derivatives, but may require small adjustments (thanks for documenting those adjustments and updating this page). The folloving tutorial has been tested on a GNU/Linux machine Ubuntu Server Edition Xenial Xerus 16.04 and a OVH VPS server (SMP Debian 3.2.68-1+deb7u5 x86_64 in january 2017. It is possible to access your GeneWeb server in HTTPS mode by configuring properly your Apache server when in CGI mode, or by acessing the service through a secure tunnel such as stunnel. 5 HTTPS for GeneWeb in daemon or service mode behind port 2317.4 HTTPS for GeneWeb in CGI mode behind Apache server.2 Installing Let's Encrypt certificates.Can you help please? This used to work great. I have tried my own daemon for a pid and tried your out-of-the-box pid=/tmp/stunnel.pid and both fail. Sep 29 03:14:00 virtualstreamer systemd: Failed to start LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons). Sep 29 03:14:00 virtualstreamer systemd: rvice: Failed with result 'exit-code'. Sep 29 03:14:00 virtualstreamer systemd: rvice: Control process exited, code=exited, status=1/FAILURE Sep 29 03:14:00 virtualstreamer stunnel4: You should check that you have specified the pid= in you configuration file Sep 29 03:14:00 virtualstreamer stunnel4: failed Sep 29 03:14:00 virtualstreamer stunnel4: Deallocating section defaults Sep 29 03:14:00 virtualstreamer stunnel4: Service : Either "CAfile" or "CApath" has to be configured Sep 29 03:14:00 virtualstreamer stunnel4: Initializing service Sep 29 03:14:00 virtualstreamer stunnel4: No PRNG seeding was required Sep 29 03:14:00 virtualstreamer stunnel4: Compression disabled Process: 1078 ExecStart=/etc/init.d/stunnel4 start (code=exited, status=1/FAILURE) Loaded: loaded (/etc/init.d/stunnel4 generated)Īctive: failed (Result: exit-code) since Tue 03:14:00 UTC 11s ago rvice - LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons).I keep getting the same errors as follows: I saved the previous configuration files and followed your steps but cannot get stunnel to start. I am now trying to reinstall stunnel so I can route through Facebook and through other outlets at the same time from OBS. I had my virtual machine run into some major problems with a bad install which would not uninstall. I had this working beautifully but had to alter ownership of the pid. You know how you know that you've exhausted all searching for information that you need? It's when you keep Googling using different key phrases and each time, all the links on Google come up purple. If you have any knowledge on how to make ffmpeg output a rtmps stream or how the librtmp library works and how to get it to do what it is supposed to when using a rtmps call, I would really appreciate the help. I came here in desperation for a work around to get a rtmps stream working to Facebook in the light that I cannot get a ssl/tls connection going with ffmpeg. Shouldn't ffmpeg be able to stream directly to Facebook if librtmp was working properly? Why do you need to use stunnel and nginx in the first place if you can stream to Facebook using an rtmps encoded stream from within ffmpeg. I can't find anywhere that explains enough to get ffmpeg working with rtmps and OpenSSL. It appears with all the Googling I've done that OpenSSL is not a library that librtmp uses but rather a running service. I've read that librtmp uses openssl to encode with and it is not enabled on my ffmpeg build. You use rtmps in ffmpeg which causes librtmp to stall out in my ffmpeg build. It neither works from a ffmpeg command line string or from your direction with nginx.
0 Comments
Leave a Reply. |