search for: get_ssl_certificate

...roup is icecast:icecast ... > > > > > Secondly, check the Icecast2's error.log looking about SSL or TLS > > > capability. > > > On Debian GNU/Linux /var/log/icecast2/error.log. > > > > From the log, I get a simple: > > > > WARN connection/get_ssl_certificate Invalid cert file <my cert > > filepath> > > INFO connection/get_ssl_certificate No SSL capability on any > > configured ports > > > Make sure you have set up Icecast correctly: > > <listen-socket> > <port>8443</port> > <ssl>1&...

...ast2 and group icecast, then icecast2:icecast. I'm on RHEL 7, so the user/group is icecast:icecast ... > Secondly, check the Icecast2's error.log looking about SSL or TLS capability. > On Debian GNU/Linux /var/log/icecast2/error.log. From the log, I get a simple: WARN connection/get_ssl_certificate Invalid cert file <my cert filepath> INFO connection/get_ssl_certificate No SSL capability on any configured ports So... not sure what else I can do here... using simple openssl verify commands I can see that the cert chain is valid... Thanks!

...ic> <fallback-override>1</fallback-override> <fallback-when-full>0</fallback-when-full> </mount> Error log with yp [2019-01-07 15:04:19] WARN main/main YP server handling has been disabled [2019-01-07 15:04:19] INFO connection/get_ssl_certificate No SSL capability [2019-01-07 15:52:43] WARN main/main YP server handling has been disabled [2019-01-07 15:52:43] INFO connection/get_ssl_certificate No SSL capability [2019-01-07 15:52:43] DBUG source/source_apply_mount YP changed to 1 -------------- next part -------------- An HTML attachm...

...y, check the Icecast2's error.log looking about SSL or > > > > > TLS capability. > > > > > On Debian GNU/Linux /var/log/icecast2/error.log. > > > > > > > > From the log, I get a simple: > > > > > > > > WARN connection/get_ssl_certificate Invalid cert file <my cert > > > > filepath> > > > > INFO connection/get_ssl_certificate No SSL capability on any > > > > configured ports > > > > > > > > > > Make sure you have set up Icecast correctly: > > > > &gt...

...> > > > > > or TLS capability. > > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log. > > > > > > > > > > > > From the log, I get a simple: > > > > > > > > > > > > WARN connection/get_ssl_certificate Invalid cert file <my cert > > > > > > filepath> > > > > > > INFO connection/get_ssl_certificate No SSL capability on any > > > > > > configured ports > > > > > > > > > > > > > > > > Make sur...

...> > > > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log. > > > > > > > > > > > > > > > > From the log, I get a simple: > > > > > > > > > > > > > > > > WARN connection/get_ssl_certificate Invalid cert file <my > > > > > > > > cert > > > > > > > > filepath> > > > > > > > > INFO connection/get_ssl_certificate No SSL capability on > > > > > > > > any configured ports > > > &gt...

...nd or such, sigh... Cheers, TBR >> On 14 May 2019, at 8.45, Oskar Vilkevuori <oskar.vilkevuori at ovt.fi >> <mailto:oskar.vilkevuori at ovt.fi>> wrote: >> >> Hi there, >> >> Is there something I’m missing here… >> >> INFO connection/get_ssl_certificate No SSL capability >> >> Does this indicate that I have a package not supporting SSL or have I >> misconfigured something somewhere? >> >> Two Listening sockets 8000 and 8001 (tried also 8002 & 8443) SSL enabled. >> >> Certificate (public and private par...

...s. No core file nor a entry in error.log is posted. In the remaining 20% of the starts icecast start with no problem. Contents of the error.log with a succesfull start (20% of icecast starts): [2015-04-25 21:08:40] INFO main/main Icecast 2.4.1 server started [2015-04-25 21:08:40] INFO connection/get_ssl_certificate No SSL capability [2015-04-25 21:08:40] INFO stats/_stats_thread stats thread started [2015-04-25 21:08:40] INFO yp/yp_update_thread YP update thread started [2015-04-25 21:08:40] INFO source/source_fallback_file mountpoint /geen-uitzending.mp3 is reserved [2015-04-25 21:08:40] WARN format/form...

...t; > In the remaining 20% of the starts icecast start with no problem. > > > > Contents of the error.log with a succesfull start (20% of icecast > starts): > > [2015-04-25 21:08:40] INFO main/main Icecast 2.4.1 server started > > [2015-04-25 21:08:40] INFO connection/get_ssl_certificate No SSL > > capability > > [2015-04-25 21:08:40] INFO stats/_stats_thread stats thread started > > [2015-04-25 21:08:40] INFO yp/yp_update_thread YP update thread started > > [2015-04-25 21:08:40] INFO source/source_fallback_file mountpoint > > /geen-uitzending.mp3 i...

Hi there, Is there something I’m missing here… INFO connection/get_ssl_certificate No SSL capability Does this indicate that I have a package not supporting SSL or have I misconfigured something somewhere? Two Listening sockets 8000 and 8001 (tried also 8002 & 8443) SSL enabled. Certificate (public and private part together in one file) .pem. read access for user, group an...

...t; I'm on RHEL 7, so the user/group is icecast:icecast ...  > > > Secondly, check the Icecast2's error.log looking about SSL or TLS > > capability. > > On Debian GNU/Linux /var/log/icecast2/error.log. > > From the log, I get a simple:  > > WARN connection/get_ssl_certificate Invalid cert file <my cert > filepath> > INFO connection/get_ssl_certificate No SSL capability on any > configured ports > Make sure you have set up Icecast correctly: <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> ... <p...

...Secondly, check the Icecast2's error.log looking about SSL or > > > > TLS > > > > capability. > > > > On Debian GNU/Linux /var/log/icecast2/error.log. > > > > > > From the log, I get a simple: > > > > > > WARN connection/get_ssl_certificate Invalid cert file <my cert > > > filepath> > > > INFO connection/get_ssl_certificate No SSL capability on any > > > configured ports > > > > > > > Make sure you have set up Icecast correctly: > > > > <listen-socket> > &gt...

Terve, I used You guidance and yes… version 2.4.4 Now I have one new line on error.log WARN connection/get_ssl_certificate Invalid cert file /usr/share/icecast2/icecast.pem It might be that Michel van Dop was right… This is how I generated the cert: openssl req -new -newkey rsa:2048 -days 365 -nodes -x509 -keyout icecast2.pem -out icecast2.pem Have I done something wrong? There is still this: INFO connection/get_...

...n/main Icecast 2.4.3 server started [2017-10-17 07:26:37] INFO yp/yp_recheck_config Adding new YP server "http://dir.xiph.org/cgi-bin/yp-cgi" (timeout 6s, default interval 30s) [2017-10-17 07:26:37] INFO yp/yp_update_thread YP update thread started [2017-10-17 07:26:37] INFO connection/get_ssl_certificate SSL certificate found at ssl.pem [2017-10-17 07:26:37] INFO connection/get_ssl_certificate SSL using ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-G CM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AE S128-GCM-SHA256:kEDH+AESGCM:ECDHE-R...

...gt; > > > > or > > > > > > TLS capability. > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log. > > > > > > > > > > From the log, I get a simple: > > > > > > > > > > WARN connection/get_ssl_certificate Invalid cert file <my > > > > > cert > > > > > filepath> > > > > > INFO connection/get_ssl_certificate No SSL capability on any > > > > > configured ports > > > > > > > > > > > > > Make sure y...

...gt; or TLS capability. > > > > > > > > On Debian GNU/Linux /var/log/icecast2/error.log. > > > > > > > > > > > > > > From the log, I get a simple: > > > > > > > > > > > > > > WARN connection/get_ssl_certificate Invalid cert file <my > > > > > > > cert > > > > > > > filepath> > > > > > > > INFO connection/get_ssl_certificate No SSL capability on > > > > > > > any > > > > > > > configured ports &gt...

...t; > > > > On Debian GNU/Linux /var/log/icecast2/error.log. > > > > > > > > > > > > > > > > > > From the log, I get a simple: > > > > > > > > > > > > > > > > > > WARN connection/get_ssl_certificate Invalid cert file > > > > > > > > > <my > > > > > > > > > cert > > > > > > > > > filepath> > > > > > > > > > INFO connection/get_ssl_certificate No SSL capability > > > > &g...

I set icecast.xmp: <listen-socket> <port>8000</port> </listen-socket> <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> 8000 work, 8443 not work. If set ssl to port 8000 not work nothing V V sob., 27. jun. 2020 ob 18:13 je oseba Paul Martin <pm at nowster.me.uk> napisala:

...ning 20% of the starts icecast start with no problem. > > > > Contents of the error.log with a succesfull start (20% of > icecast starts): > > [2015-04-25 21:08:40] INFO main/main Icecast 2.4.1 server started > > [2015-04-25 21:08:40] INFO connection/get_ssl_certificate No SSL > > capability > > [2015-04-25 21:08:40] INFO stats/_stats_thread stats thread started > > [2015-04-25 21:08:40] INFO yp/yp_update_thread YP update thread > started > > [2015-04-25 21:08:40] INFO source/source_fallback_file mountpoint >...

...for each part like link has message link has "> > bad start (segfault): > > [2015-04-28 15:56:53] INFO main/main Icecast 2.4.1 server started > > [2015-04-28 15:56:53] DBUG yp/yp_recheck_config Updating YP > configuration > > [2015-04-28 15:56:53] INFO connection/get_ssl_certificate No SSL > > capability > > [2015-04-28 15:56:53] INFO yp/yp_update_thread YP update thread started > > [2015-04-28 15:56:53] INFO source/source_fallback_file mountpoint > > /geen-uitzending.mp3 is reserved > > [2015-04-28 15:56:53] DBUG connection/connection_complete...