search for: 8443

tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 8421/icecast2 tcp 0 0 192.168.1.159:8443 192.168.1.1:65003 ESTABLISHED 8421/icecast2 Den sön 25 okt. 2020 kl 18:42 skrev Kwame Bahena <informatux at gmail.com>: > Hello, > > What does the command > > sudo netstat...

Any help here, please? Here is the settings in icecast-config: <hostname>bananradion.bananklubben.se</hostname> <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> <listen-socket> <port>8086</port> </listen-socket> ..and ices-config <hostname>bananradion.bananklubben.se</hostname> <port>8086</port> <password>Banan123??</password> &l...

...ces on the same server as your icecast, try > using localhost instead of "bananradion.bananklubben.se" > > > Cheers, > -- > Kwame > > On Sun, Oct 25, 2020 at 11:44 AM Bananradion <bananradion at gmail.com> > wrote: > >> tcp 0 0 0.0.0.0:8443 0.0.0.0:* >> LISTEN 8421/icecast2 >> tcp 0 0 192.168.1.159:8443 192.168.1.1:65003 >> ESTABLISHED 8421/icecast2 >> >> Den sön 25 okt. 2020 kl 18:42 skrev Kwame Bahena <informatux at gmail.com>: >> >>> Hello, >&g...

Hello All, I had installed icecast2.2.4 with openSSL. I created a wordpress web site with SSL. If I stream with HTTPS under chrome , the player don’t work. If I stream without yes ! Could you please help me ? Thanks -------- Norbert Deleutre  <http://www.lmgc.univ-montp2.fr/perso/norbert-deleutre/> P 0467149655 UMR CNRS 5508  <http://www.lmgc.univ-montp2.fr/> A Campus

...orts > > > > > > > > > > > > > > > > > > > > > > Make sure you have set up Icecast correctly: > > > > > > > > > > > > > > <listen-socket> > > > > > > > <port>8443</port> > > > > > > > <ssl>1</ssl> > > > > > > > </listen-socket> > > > > > > > > > > > > Yeah... it's setup properly... > > > > > > > > > > > > > <pat...

...capability on any > > > > > > configured ports > > > > > > > > > > > > > > > > Make sure you have set up Icecast correctly: > > > > > > > > > > <listen-socket> > > > > > <port>8443</port> > > > > > <ssl>1</ssl> > > > > > </listen-socket> > > > > > > > > Yeah... it's setup properly... > > > > > > > > > <paths> > > > > > ... > > > > &gt...

On Sun, 25 Oct 2020, Bananradion wrote: > I changed to "localhost" in the ices-config and got this error: > > EROR stream/ices_instance_stream Failed initial connect to localhost:8443 > (TLS connection can not be established because of bad certificate: Success) This might not help your situation, but there is absolutely 0 need to use TLS on localhost as the packets never leave the machine. If someone has access to your machine, you've got bigger problems than them int...

On Mon, 26 Oct 2020, Bananradion wrote: > Ok! So how can i fix this issue then? > All works great if I connect ices to port 8086, but I need it to connect to > 8443 without getting "Socket is busy". In all honesty, I don't know what that error means adn I've not tried to use TLS with Icecast. I guess you could set up two listen sockets on port 8443, one on 127.0.0.1 without SSL and one on your external IP address with SSL. But if it all...

I changed to "localhost" in the ices-config and got this error: EROR stream/ices_instance_stream Failed initial connect to localhost:8443 (TLS connection can not be established because of bad certificate: Success) /Daniel Den sön 25 okt. 2020 kl 19:00 skrev Bananradion <bananradion at gmail.com>: > Both icecast and ices are on the same server. > Where shall i change to "localhost"? > > > /Daniel &gt...

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: > On Fri, Jun 26, 2020 at 09:08:48PM +0200, Ervin Bizjak wrot...

...talled icecast not work. Create certificate (.crt) and convert to .pem with openssl x509 -in mycert.crt -out mycert.pem -outform PEM certificate.pem copy to c:/icecast/cert/ Edit icecast.xml: <ssl-certificate>./cert/icecast.pem</ssl-certificate> <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> I don't know what can I do wrong V V pet., 2. avg. 2019 ob 03:47 je oseba <webmaster at berean-biblechurch.org> napisala: > On 2019-07-31 09:44, unosonic wrote: > > Thomas B. Rücker: > >> After all,...

thanks, that makes sense and works! btw: is port 8443 sort of standard, which clients do consider? bests, uno Per Gunnarsson: > I have one listening socket for http and one separate for https. > > It looks like this: > >    >     <listen-socket> >         <port>8000</port> >     </listen-socket> &gt...

...er in another server? If not, if you are running ices on the same server as your icecast, try using localhost instead of "bananradion.bananklubben.se" Cheers, -- Kwame On Sun, Oct 25, 2020 at 11:44 AM Bananradion <bananradion at gmail.com> wrote: > tcp 0 0 0.0.0.0:8443 0.0.0.0:* > LISTEN 8421/icecast2 > tcp 0 0 192.168.1.159:8443 192.168.1.1:65003 > ESTABLISHED 8421/icecast2 > > Den sön 25 okt. 2020 kl 18:42 skrev Kwame Bahena <informatux at gmail.com>: > >> Hello, >> >> What does the co...

Hello I am running https://radio.horsens-garage.rocks:8443. The SSL- certificate is made like this: cat /etc/letsencrypt/live/horsens-garage.rocks/fullchain.pem /etc/letsencrypt/live/horsens-garage.rocks/privkey.pem > /etc/icecast2/bundle.pem I have had no errors or warnings in any browser. Until now! Fulguris, a FOSS-browser for android, gave me a w...

...e over https. In the ezstream config file I have defined two servers (http and https) and the two streams point to the different servers (by their names). But, if I go to the following two url's, Icecast report same (http-) 'streaming url' for both: https://radio.horsens-garage.rocks:8443/ http://radio.horsens-garage.rocks:8000/ And, if I login as admin, the listenurl is: 'listenurl http://radio.horsens-garage.rocks:8443/stream' for both http and https. It looks like the "http://" is hardcoded into the icecast code, so it must be considered a (cosmetic?) bug i...

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=429 ------- Additional Comments From laforge@netfilter.org 2006-01-25 11:00 MET ------- Please specifically tell us about the exact kernel version, any patches that you might have applied, and the iptables version that you're using. -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla/userprefs.cgi?tab=email ------- You

Thomas B. Rücker: > After all, Icecast is just another web server. > > Please note the absence of 8000 and 8443. Neither are officially > specified for WWW type HTTP(S). They are commonly used as such, but 80 > and 443 are *much* better choices and should be preferred. makes sense, but if my webserver needs to serve http/s from the same IP, that would not work. Unless I want to use Icecast as a nginx...

Non SSL wor perfectly, but i need https://IP:8443 for another listeners. This I need, because chrome not play player in my web site (mixed content). Now is in my player in web site http://ip:8000, but website run in https V V pon., 29. jun. 2020 ob 09:15 je oseba Railgun <railgun.michael at gmail.com> napisala: > Try non SSL connection...

...#39;s public key? If so, I've tried this, and it doesn't work. On 11/25/2020 7:04 AM, Damien GENESTE wrote: > Hello Norbert, > > I don't know how i can help you but i'm actually streaming with HTTPS > under chrome. > My Icecast is available at : https://domainname:8443 > <https://domainname:8443> and my webplayer gets the stream at : > https://domainname:8443/stream <https://domainname:8443/stream> > > Is your server (Wordpress or other) with HTTPS ? > > BR, > > *Ceelo* > > On Wed, Nov 25, 2020 at 10:22 AM Norbert Deleu...

...; > > > > > > > > > > > > > > > > > > > Make sure you have set up Icecast correctly: > > > > > > > > > > > > > > > > <listen-socket> > > > > > > > > <port>8443</port> > > > > > > > > <ssl>1</ssl> > > > > > > > > </listen-socket> > > > > > > > > > > > > > > Yeah... it's setup properly... > > > > > > > > > >...