From zinphad at gmail.com  Thu Jul  7 16:56:19 2016
From: zinphad at gmail.com (Mike Williams)
Date: Thu, 7 Jul 2016 12:56:19 -0400
Subject: [Icecast] Icecast is running, but not responding
Message-ID: <CAHxTWLUFqz6w87Lpk9QrLjo6j5C25zVyyt4hXvBu2bxy4J73qw@mail.gmail.com>

Howdy,

I work for a public radio station, and have setup several Icecast servers
in the past to stream our content.  We have a new HD channel that we are
trying to stream, and the new server is vexing me.

This is a fresh dedicated server running RHEL 7.2 on a virtual system
running VMWare 6.1.

The install was done with the command  yum --nogpgcheck localinstall
icecast-2.4.2-1.el7.x86_64.rpm

I copied the old icecast.xml file from my primary Icecast server, to save
some time, but when that did not work, I started again from scratch and
setup a very basic xml file, but that did not work either.  The current
icecast.xml file (a bit redacted) is:

<icecast>
    <limits>
        <clients>1000</clients>
        <sources>5</sources>
        <threadpool>5</threadpool>
        <queue-size>524288</queue-size>
        <client-timeout>30</client-timeout>
        <header-timeout>15</header-timeout>
        <source-timeout>10</source-timeout>
        <burst-size>65535</burst-size>
    </limits>

    <authentication>
        <!-- Sources log in with username 'source' -->
        <source-password>mypass</source-password>
        <!-- Relays log in username 'relay' -->
        <relay-password>mypass</relay-password>
        <!-- Admin logs in with the username given below -->
        <admin-user>admin</admin-user>
        <admin-password>mypass</admin-password>
    </authentication>

    <hostname>my.ip.address</hostname>

    <listen-socket>
        <port>8000</port>
    </listen-socket>
    <fileserve>1</fileserve>

    <mount>
<mount-name>/hd2</mount-name>
    </mount>
    <paths>
        <basedir>/usr/share/icecast</basedir>
        <logdir>/var/log/icecast</logdir>
        <webroot>/usr/share/icecast/web</webroot>
        <adminroot>/usr/share/icecast/admin</adminroot>
        <pidfile>/var/run/icecast/icecast.pid</pidfile>
        <alias source="/" dest="/status.xsl"/>
    </paths>

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <playlistlog>playlist.log</playlistlog>
      <loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
    </logging>

    <security>
        <chroot>0</chroot>
        <changeowner>
            <user>icecast</user>
            <group>icecast</group>
        </changeowner>
    </security>
</icecast>

When I run netstat -tnlp I get
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
    PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
     1358/sshd
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN
     2054/master
tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN
     3095/icecast
tcp6       0      0 :::22                   :::*                    LISTEN
     1358/sshd
tcp6       0      0 ::1:25                  :::*                    LISTEN
     2054/master

So it's listening.  But when I try to access it via my.ip.address:8000, it
times out.  Also when I try to send audio from the encoder, it will not
connect.  However, when I do a tcpdump -n -i eth0 tcp port 8000 while the
encoder is trying to hit it, I get
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
12:40:42.043018 IP encoder.ip.address.52497 > my.ip.address.irdmi: Flags
[S], seq 3183330347, win 8192, options [mss 1460,nop,wscale
8,nop,nop,sackOK], length 0

every couple of seconds.  When trying to connect via web browser I get
12:43:38.625144 IP browser.ip.address.54947 > my.ip.address.irdmi: Flags
[S], seq 1526231377, win 8192, options [mss 1460,nop,nop,sackOK], length 0

So packets from both the browser and the encoder are getting to the server.

The error log from last night (when I last restarted it) reads
[2016-07-06  22:53:09] INFO main/main Icecast 2.4.2 server started
[2016-07-06  22:53:09] DBUG yp/yp_recheck_config Updating YP configuration
[2016-07-06  22:53:09] INFO yp/yp_update_thread YP update thread started
[2016-07-06  22:53:09] INFO connection/get_ssl_certificate No SSL
capability on any configured ports
[2016-07-06  22:53:10] DBUG slave/_slave_thread checking master stream list

The last line repeats every couple of minutes from there on.

Icecast was started using the command
systemctl start icecast.service
systemctl -l status icecast.service

Jul 06 22:53:09 servername.company.name icecast[3094]: Starting icecast2

Jul 06 22:53:09 servername.company.name icecast[3094]: Detaching from the
console

Jul 06 22:53:09 servername.company.name icecast[3094]: Changed groupid to
991.

Jul 06 22:53:09 servername.company.name icecast[3094]: Changed
supplementary groups based on user: icecast.

Jul 06 22:53:09 servername.company.name icecast[3094]: Changed userid to
994.

The icecast.service file is
[Unit]
Description=Icecast Network Audio Streaming Server
After=network.target

[Service]
ExecStart=/usr/bin/icecast -b -c /etc/icecast.xml
Type=forking
ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target

I am sure there is info that I did not think to include.

Any thought you have as to why this is happening are welcome.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160707/ef55f55e/attachment.htm>

From bluntroller at yandex.com  Thu Jul  7 17:11:33 2016
From: bluntroller at yandex.com (buddylove)
Date: Thu, 7 Jul 2016 19:11:33 +0200
Subject: [Icecast] Icecast is running, but not responding
In-Reply-To: <CAHxTWLUFqz6w87Lpk9QrLjo6j5C25zVyyt4hXvBu2bxy4J73qw@mail.gmail.com>
References: <CAHxTWLUFqz6w87Lpk9QrLjo6j5C25zVyyt4hXvBu2bxy4J73qw@mail.gmail.com>
Message-ID: <577E8D45.80509@yandex.com>

whats the quest?
your post is incomplete...
'... but when that did not work, I started again from scratch and setup
a very basic xml file...'

did you notice the probably newer version?

-- 
The only absolute knowledge attainable by man is
that life is meaningless. (Tolstoi)

Never underestimate the power of stupid people
in large groups. (George Carlin)

CONFIDENTIALITY : This  e-mail  and  any attachments are
confidential and may be privileged. If  you are not a named
recipient, please notify the sender immediately and do not
disclose the contents to another person, use it for any
purpose or store or copy the information in any medium.


-----BEGIN PUBLIC INFO BLOCK-----
Workstation(s) XH61V
2xIvy Bridge|16GB-SDRAM|120GB-SDHD|2x3TB - LUKS
-
Operating System
Arch Linux|Ubuntu Studio
-
Programming
C/C++|bash|awk|php|java|ruby|asm|css|html
-
Server (Hardware)
3 Cores|3GB-RAM|75GB-SDHD|10TB Traffic
-
Server (Software)
Tor-Exit|Icecast-Stream|Torrent-Stream|I2P
-
Gee Bee Productions
Radio
IT-Contractor
Hardware/PCB One-Off-Productions
Intrusion Detection -  Forensic - Pentesting
Webdesign - Web-Authoring - Content Management
www.pirate-radio.eu
+41/76-7569208
bitcoin 13aXxBnwBnnJApKhCA9ZYLHqPYfHMY8B1d
-----END PUBLIC INFO BLOCK-----



From zinphad at gmail.com  Fri Jul  8 13:09:02 2016
From: zinphad at gmail.com (Mike Williams)
Date: Fri, 8 Jul 2016 09:09:02 -0400
Subject: [Icecast]  Icecast is running, but not responding
Message-ID: <CAHxTWLUgoCPT1kvghpqPqMTf5jYi9ocSz5fp2e7qJQRFmt5r_Q@mail.gmail.com>

Sorry, I seem to have buried the issue in the midst of the post.

The issue is, the Icecast is running, but will not display a web interface
at my.ip.address:8000 and will not accept connections from my encoder.
Anyone have any idea why it might be behaving this way?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160708/36410bd7/attachment.htm>

From schultmc at affordablestreaming.com  Fri Jul  8 16:38:55 2016
From: schultmc at affordablestreaming.com (Michael Schultheiss)
Date: Fri, 8 Jul 2016 12:38:55 -0400
Subject: [Icecast] Icecast is running, but not responding
In-Reply-To: <CAHxTWLUgoCPT1kvghpqPqMTf5jYi9ocSz5fp2e7qJQRFmt5r_Q@mail.gmail.com>
References: <CAHxTWLUgoCPT1kvghpqPqMTf5jYi9ocSz5fp2e7qJQRFmt5r_Q@mail.gmail.com>
Message-ID: <CAPT-twncUzF2yt6yY-35gkqbpR3FGipa-vFHeaooEKfnSBRO8Q@mail.gmail.com>

firewalld is likely blocking the connection to icecast.
On Jul 8, 2016 9:09 AM, "Mike Williams" <zinphad at gmail.com> wrote:

> Sorry, I seem to have buried the issue in the midst of the post.
>
> The issue is, the Icecast is running, but will not display a web interface
> at my.ip.address:8000 and will not accept connections from my encoder.
> Anyone have any idea why it might be behaving this way?
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160708/bd58df30/attachment.htm>

From djkennyray at djkennyray.com  Fri Jul  8 22:53:54 2016
From: djkennyray at djkennyray.com (Kenneth Ray)
Date: Fri, 8 Jul 2016 17:53:54 -0500
Subject: [Icecast] Icecast is running, but not responding
In-Reply-To: <CAPT-twncUzF2yt6yY-35gkqbpR3FGipa-vFHeaooEKfnSBRO8Q@mail.gmail.com>
References: <CAHxTWLUgoCPT1kvghpqPqMTf5jYi9ocSz5fp2e7qJQRFmt5r_Q@mail.gmail.com>
 <CAPT-twncUzF2yt6yY-35gkqbpR3FGipa-vFHeaooEKfnSBRO8Q@mail.gmail.com>
Message-ID: <015301d1d96b$9b1f8fc0$d15eaf40$@djkennyray.com>

Check your mount point 

 

 

From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Michael Schultheiss
Sent: Friday, July 08, 2016 11:39 AM
To: Icecast streaming server user discussions
Subject: Re: [Icecast] Icecast is running, but not responding

 

firewalld is likely blocking the connection to icecast.

On Jul 8, 2016 9:09 AM, "Mike Williams" <zinphad at gmail.com> wrote:

Sorry, I seem to have buried the issue in the midst of the post.  

 

The issue is, the Icecast is running, but will not display a web interface at my.ip.address:8000 and will not accept connections from my encoder.  Anyone have any idea why it might be behaving this way?


_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160708/e2a9d092/attachment.htm>

From walteryork at hotmail.com  Sat Jul  9 00:19:30 2016
From: walteryork at hotmail.com (Walter York)
Date: Fri, 8 Jul 2016 20:19:30 -0400
Subject: [Icecast] icecast and SSL
Message-ID: <BLU180-W8020D1C7412B4CDF74DC66D93D0@phx.gbl>

I use IceCast with Centova and I'm having a hard time setting up SSL with icecast.
I updated both config files:/usr/local/icecast/etc/icecast.xml/usr/local/centovacast/var/vhosts/music/etc/server.conf
Both files above were modified to include:    <listen-socket>        <port>8000</port>        <ssl>1</ssl>
and the path section updated <ssl-certificate>/home/.../ssl/keys/icecast.pem</ssl-certificate>... replaced with actual folder name.
I read that the PEM file requires both private and public keys so I created an empty file called icecast.pem and pasted -----BEGIN RSA PRIVATE KEY----- private key content-----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- public key content-----END CERTIFICATE----- 
I am unable to serve SSL pages.  I created CSR on the server and had CA send me key back.  They are in PEM format and the individual files (CRT & KEY) are working on both my Centova and Apache webservers.
I would greatly appreciate your assistance to resolve... 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160708/a2af4a2e/attachment.htm>

From bluntroller at yandex.com  Sat Jul  9 09:54:51 2016
From: bluntroller at yandex.com (buddylove)
Date: Sat, 9 Jul 2016 11:54:51 +0200
Subject: [Icecast] Icecast is running, but not responding
In-Reply-To: <015301d1d96b$9b1f8fc0$d15eaf40$@djkennyray.com>
References: <CAHxTWLUgoCPT1kvghpqPqMTf5jYi9ocSz5fp2e7qJQRFmt5r_Q@mail.gmail.com>
 <CAPT-twncUzF2yt6yY-35gkqbpR3FGipa-vFHeaooEKfnSBRO8Q@mail.gmail.com>
 <015301d1d96b$9b1f8fc0$d15eaf40$@djkennyray.com>
Message-ID: <5780C9EB.7030907@yandex.com>

yeah right, check your *mountpoint*.
also you should consider to take a look at the *config-file* as a whole.
there are differences between old config files and the ones used in the
recent icecast version.
they are not compatible or at least (in my configuration) weren't
interchangeable and the new version uses a *larger tag-set*.
you can't go far from an distant analyses by mailing-list users without
fingerprinting your whole system.
also people in here are busy (speaking for myself) and only in the mood
to reply when they search for distraction. (see before)
i learned that the hard way...

Greets and GL
Gee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160709/e340f772/attachment.htm>

From bluntroller at yandex.com  Sat Jul  9 11:19:03 2016
From: bluntroller at yandex.com (buddylove)
Date: Sat, 9 Jul 2016 13:19:03 +0200
Subject: [Icecast] ssl-cert's
Message-ID: <5780DDA7.90104@yandex.com>

@ the guy with the ssl certs problem:

recheck file- and folder-permissions.
check if the ssl.-cert is generated correct.
re-check the icecast config-file and it's file- and folder-permissions.
are the involved files in the correct location so icecast can find them?
what about the pid-entry?

greets
gee


From epirat07 at gmail.com  Sat Jul  9 11:59:39 2016
From: epirat07 at gmail.com (Marvin Scholz)
Date: Sat, 09 Jul 2016 13:59:39 +0200
Subject: [Icecast] ssl-cert's
In-Reply-To: <5780DDA7.90104@yandex.com>
References: <5780DDA7.90104@yandex.com>
Message-ID: <E0060C2A-1DE6-4EB9-A11E-0712A1048465@gmail.com>

On 9 Jul 2016, at 13:19, buddylove wrote:

> @ the guy with the ssl certs problem:

Please reply properly to the E-Mails, just replaying to the list without the
correct In-reply-to will break threads and makes using the mailinglist very
annoying, as if I had chosen to ignore the thread you replied to, I would
still see your E-Mail.

>
> recheck file- and folder-permissions.
> check if the ssl.-cert is generated correct.
> re-check the icecast config-file and it's file- and folder-permissions.
> are the involved files in the correct location so icecast can find them?
> what about the pid-entry?
>
> greets
> gee
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From bluntroller at yandex.com  Sat Jul  9 13:36:39 2016
From: bluntroller at yandex.com (buddylove)
Date: Sat, 9 Jul 2016 15:36:39 +0200
Subject: [Icecast] ssl-cert's
In-Reply-To: <E0060C2A-1DE6-4EB9-A11E-0712A1048465@gmail.com>
References: <5780DDA7.90104@yandex.com>
 <E0060C2A-1DE6-4EB9-A11E-0712A1048465@gmail.com>
Message-ID: <5780FDE7.8090207@yandex.com>

soooory


From walteryork at hotmail.com  Sun Jul 10 21:11:06 2016
From: walteryork at hotmail.com (Walter York)
Date: Sun, 10 Jul 2016 17:11:06 -0400
Subject: [Icecast] ssl-cert's
In-Reply-To: <5780DDA7.90104@yandex.com>
References: <5780DDA7.90104@yandex.com>
Message-ID: <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>

1.  I already have the cert and key files.  How do I combine these existing keys into a single PEM file?2.  What directory do you suggest I place they PEM file?

> To: icecast at xiph.org
> From: bluntroller at yandex.com
> Date: Sat, 9 Jul 2016 13:19:03 +0200
> Subject: [Icecast] ssl-cert's
> 
> @ the guy with the ssl certs problem:
> 
> recheck file- and folder-permissions.
> check if the ssl.-cert is generated correct.
> re-check the icecast config-file and it's file- and folder-permissions.
> are the involved files in the correct location so icecast can find them?
> what about the pid-entry?
> 
> greets
> gee
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160710/3be7ac6e/attachment.htm>

From fountainbridge at live.com  Mon Jul 11 03:23:35 2016
From: fountainbridge at live.com (Roger Bailey)
Date: Mon, 11 Jul 2016 03:23:35 +0000
Subject: [Icecast] set up help
Message-ID: <CY1PR15MB021973445D54152AE403CE40BC3F0@CY1PR15MB0219.namprd15.prod.outlook.com>

I'm an Icecast noob looking to start my own radio station, but have come to a wall in terms of installation/finishing. I've gotten as far as where you can see that administrator screen with the "Global Server Stats".
What next? I'm totally confused on how Winamp is connected to it. (Using a pc with Win 7)
Thanks for Any help!


-R
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160711/fdc222b7/attachment.htm>

From bluntroller at yandex.com  Mon Jul 11 06:56:10 2016
From: bluntroller at yandex.com (buddylove)
Date: Mon, 11 Jul 2016 08:56:10 +0200
Subject: [Icecast] ssl-cert's
In-Reply-To: <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>
References: <5780DDA7.90104@yandex.com>
 <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>
Message-ID: <5783430A.3050209@yandex.com>

I am not familiar with the usage of SSL-Certs (in Icecast).
I'd recommend to put them somewhere into a folder the webserver has
access to.
Don't forget to change ownership and mode etc.

check this out about you problem with the files ->
http://stackoverflow.com/questions/991758/how-to-get-an-openssl-pem-file-from-key-and-crt-files


From jerickson at logicalnetworking.net  Mon Jul 11 16:10:04 2016
From: jerickson at logicalnetworking.net (Jordan Erickson)
Date: Mon, 11 Jul 2016 09:10:04 -0700
Subject: [Icecast] ssl-cert's
In-Reply-To: <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>
References: <5780DDA7.90104@yandex.com>
 <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>
Message-ID: <9959349b-34cd-4988-d483-639d199df944@logicalnetworking.net>

# cat fullchain.pem privkey.pem >combined.pem

I wouldn't think it matters much where you put the cert as long as the
running Icecast user has permissions to read it. I'd create (if not
already created) /etc/icecast personally.

<ssl-certificate>:

If specified, this points to the location of a file that contains both
the X.509 private and public key. This is required for HTTPS support to
be enabled. Please note that the user Icecast is running as must be able
to read the file. Failing to ensure this will cause a "Invalid cert
file" WARN message, just as if the file wasn't there.


Cheers,
Jordan


On 07/10/2016 02:11 PM, Walter York wrote:
> 1.  I already have the cert and key files.  How do I combine these
> existing keys into a single PEM file?
> 2.  What directory do you suggest I place they PEM file?
> 
>> To: icecast at xiph.org
>> From: bluntroller at yandex.com
>> Date: Sat, 9 Jul 2016 13:19:03 +0200
>> Subject: [Icecast] ssl-cert's
>>
>> @ the guy with the ssl certs problem:
>>
>> recheck file- and folder-permissions.
>> check if the ssl.-cert is generated correct.
>> re-check the icecast config-file and it's file- and folder-permissions.
>> are the involved files in the correct location so icecast can find them?
>> what about the pid-entry?
>>
>> greets
>> gee
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
> 
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 

-- 
Jordan Erickson (PGP: 0x78DD41CB)
Logical Networking Solutions, 707-636-5678




From bluntroller at yandex.com  Mon Jul 11 16:25:45 2016
From: bluntroller at yandex.com (buddylove)
Date: Mon, 11 Jul 2016 18:25:45 +0200
Subject: [Icecast] ssl-cert's
In-Reply-To: <9959349b-34cd-4988-d483-639d199df944@logicalnetworking.net>
References: <5780DDA7.90104@yandex.com>
 <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>
 <9959349b-34cd-4988-d483-639d199df944@logicalnetworking.net>
Message-ID: <5783C889.2040800@yandex.com>

all in the docs (btw)
yeah you are right...
the webserver doesn't deal with the icecast-server.
but me personally, I put these kind of stuff into the webroot or near it.

greets

Werner Scherentz


From jerickson at logicalnetworking.net  Mon Jul 11 16:38:22 2016
From: jerickson at logicalnetworking.net (Jordan Erickson)
Date: Mon, 11 Jul 2016 09:38:22 -0700
Subject: [Icecast] ssl-cert's
In-Reply-To: <5783C889.2040800@yandex.com>
References: <5780DDA7.90104@yandex.com>
 <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>
 <9959349b-34cd-4988-d483-639d199df944@logicalnetworking.net>
 <5783C889.2040800@yandex.com>
Message-ID: <0b989b5e-0172-0ec0-07a1-571d9c1cde94@logicalnetworking.net>

Putting your ssl certificate chain in a publicly accessible place like
webroot is a very bad idea. Anyone could read it which means anyone
could use it to impersonate your Icecast server.


Cheers,
Jordan

On 07/11/2016 09:25 AM, buddylove wrote:
> all in the docs (btw)
> yeah you are right...
> the webserver doesn't deal with the icecast-server.
> but me personally, I put these kind of stuff into the webroot or near it.
> 
> greets
> 
> Werner Scherentz
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 

-- 
Jordan Erickson (PGP: 0x78DD41CB)
Logical Networking Solutions, 707-636-5678




From bluntroller at yandex.com  Mon Jul 11 16:52:06 2016
From: bluntroller at yandex.com (buddylove)
Date: Mon, 11 Jul 2016 18:52:06 +0200
Subject: [Icecast] ssl-cert's
In-Reply-To: <0b989b5e-0172-0ec0-07a1-571d9c1cde94@logicalnetworking.net>
References: <5780DDA7.90104@yandex.com>
 <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>
 <9959349b-34cd-4988-d483-639d199df944@logicalnetworking.net>
 <5783C889.2040800@yandex.com>
 <0b989b5e-0172-0ec0-07a1-571d9c1cde94@logicalnetworking.net>
Message-ID: <5783CEB6.6040902@yandex.com>

you did say THAT.
however, as always... pleasure :-/


From fountainbridge at live.com  Mon Jul 11 17:16:54 2016
From: fountainbridge at live.com (Roger Bailey)
Date: Mon, 11 Jul 2016 17:16:54 +0000
Subject: [Icecast] ssl-cert's
In-Reply-To: <5783430A.3050209@yandex.com>
References: <5780DDA7.90104@yandex.com>
 <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>,<5783430A.3050209@yandex.com>
Message-ID: <CY1PR15MB0219FB8D90F742FA142C2F09BC3F0@CY1PR15MB0219.namprd15.prod.outlook.com>

This tech chat between buddylove and others is all going totally over my head.
I just need someone to walk me through it step by step like I'm trying to land a plane since the directions on the icecast site are Greek to me.
Thanks for Any help!



Sent on my Boost Mobile Samsung Galaxy S? 5


-------- Original message --------
From: buddylove <bluntroller at yandex.com>
Date: 7/11/16 2:56 AM (GMT-05:00)
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: Re: [Icecast] ssl-cert's

I am not familiar with the usage of SSL-Certs (in Icecast).
I'd recommend to put them somewhere into a folder the webserver has
access to.
Don't forget to change ownership and mode etc.

check this out about you problem with the files ->
http://stackoverflow.com/questions/991758/how-to-get-an-openssl-pem-file-from-key-and-crt-files
_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160711/9d17212f/attachment.htm>

From bluntroller at yandex.com  Mon Jul 11 18:58:07 2016
From: bluntroller at yandex.com (buddylove)
Date: Mon, 11 Jul 2016 20:58:07 +0200
Subject: [Icecast] ssl-cert's
In-Reply-To: <CY1PR15MB0219FB8D90F742FA142C2F09BC3F0@CY1PR15MB0219.namprd15.prod.outlook.com>
References: <5780DDA7.90104@yandex.com>
 <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl> <5783430A.3050209@yandex.com>
 <CY1PR15MB0219FB8D90F742FA142C2F09BC3F0@CY1PR15MB0219.namprd15.prod.outlook.com>
Message-ID: <5783EC3F.80503@yandex.com>

Hi Roger

sorry if I bothered you or even mislead you with some former post.
With respect to IT I have totally different topics in my head than the
'Icecast-thing'. It's history for me already quite a while and the work
I invested in making
it running disgusted me.
Please consider that English is not my mother-language and even if my
English is
good, it's not perfect or without mistakes.

Where you put your certs and stuff isn't really of any importance
because by the correct masking you can hide them - even in a folder
where the webserver has access too. Security comes not by putting files
in some folder or not (even jails), Security comes as a whole but that's
another topic and the deeper I dig into it the
more distant I get from your problem. Also there are always and everywhere
people disagreeing, trying to put their own mustard on the sausage.

Nice bla interlude isn't it.

My recommendation and without crawling in my resources and the ones in
the web
here my advice:

1. check your cert files
2. download and read the suitable manual to your icecast-server
3. check the linkage between the files (icecast.xml <-> cert-files)
4. check the ownership and mode of the files and folders
(icecast:icecast, 740)
5. check the linkage to the pid-file

additionally you can
4.
    . check the webservers configs
    . if the ssl mod is loaded
    . if ssl is enable in the webserver of your choice

Even if the other nerd around mentioned correct that the webserver
usually has
no meaning in that scenario...
Can you set up the webserver (or any other similar application) you use
to use
your certs, are they working?


There should usually not be more to do than that.
I never set up a ssl-connection with my stream (for what?
superfluous...) so I
can't really report out of my experiences.


From walteryork at hotmail.com  Mon Jul 11 19:06:14 2016
From: walteryork at hotmail.com (Walter York)
Date: Mon, 11 Jul 2016 15:06:14 -0400
Subject: [Icecast] ssl-cert's
In-Reply-To: <9959349b-34cd-4988-d483-639d199df944@logicalnetworking.net>
References: <5780DDA7.90104@yandex.com>,
 <BLU180-W89E0148294530CBF8C0A3D93E0@phx.gbl>,
 <9959349b-34cd-4988-d483-639d199df944@logicalnetworking.net>
Message-ID: <BLU180-W37D78167A34AB5F31343A3D93F0@phx.gbl>

Seems like I had SSL setup properly in the first place...  Apparently Centovacast is not playing fair with my mount port, after setting up an alternate port and setting ssl and path to the cert in the config file, everything is good.  I'll place these steps below for others to use...
I used the following command to create a self-signed cert for testing...
openssl req -new -newkey rsa:2048 -days 365 -nodes -x509 -keyout sample.pem -out sample.pem
(this created a correctly formatted self-signed certificate that works)  I placed the pem file into my ssl folder, made sure the user that runs icecast has perms to the pem file.  I added the <ssl>1</ssl> to my config file and then added the path as well following the instructions from here: http://www.icecast.org/docs/icecast-2.4.1/config-file.html
I also used the instructions from here to create my pem file:  https://www.digicert.com/ssl-support/pem-ssl-creation.htmSpecifically under the heading: Creating a .pem with the Private Key and Entire Trust Chain
If you are using a Windows based system and not linux cat, you must use Wordpad and NOT Notepad.  The certificate begin and certificate ends from consecutive certificates are on separate lines... not sure if that matters though.
Now, since changing the ports from 8000 to 8050 having a secure page, the new page doesn't show any active streams... another thing to troubleshoot but I'm further along!

> To: icecast at xiph.org
> From: jerickson at logicalnetworking.net
> Date: Mon, 11 Jul 2016 09:10:04 -0700
> Subject: Re: [Icecast] ssl-cert's
> 
> # cat fullchain.pem privkey.pem >combined.pem
> 
> I wouldn't think it matters much where you put the cert as long as the
> running Icecast user has permissions to read it. I'd create (if not
> already created) /etc/icecast personally.
> 
> <ssl-certificate>:
> 
> If specified, this points to the location of a file that contains both
> the X.509 private and public key. This is required for HTTPS support to
> be enabled. Please note that the user Icecast is running as must be able
> to read the file. Failing to ensure this will cause a "Invalid cert
> file" WARN message, just as if the file wasn't there.
> 
> 
> Cheers,
> Jordan
> 
> 
> On 07/10/2016 02:11 PM, Walter York wrote:
> > 1.  I already have the cert and key files.  How do I combine these
> > existing keys into a single PEM file?
> > 2.  What directory do you suggest I place they PEM file?
> > 
> >> To: icecast at xiph.org
> >> From: bluntroller at yandex.com
> >> Date: Sat, 9 Jul 2016 13:19:03 +0200
> >> Subject: [Icecast] ssl-cert's
> >>
> >> @ the guy with the ssl certs problem:
> >>
> >> recheck file- and folder-permissions.
> >> check if the ssl.-cert is generated correct.
> >> re-check the icecast config-file and it's file- and folder-permissions.
> >> are the involved files in the correct location so icecast can find them?
> >> what about the pid-entry?
> >>
> >> greets
> >> gee
> >> _______________________________________________
> >> Icecast mailing list
> >> Icecast at xiph.org
> >> http://lists.xiph.org/mailman/listinfo/icecast
> > 
> > 
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> > 
> 
> -- 
> Jordan Erickson (PGP: 0x78DD41CB)
> Logical Networking Solutions, 707-636-5678
> 
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160711/a7800c52/attachment.htm>

From jeffares.robert at gmail.com  Sun Jul 17 07:46:48 2016
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Sun, 17 Jul 2016 19:46:48 +1200
Subject: [Icecast] setup for inclusion of now and next data on mp3 stream
Message-ID: <578B37E8.4050402@gmail.com>

I have a streaming server running Darkice and Icecast2 on Ubuntu server.

The audio part works perfectly.

My playout system [Rivendell] outputs 'now playing' data and can be 
configured to point to the streaming server and the default 8000 port.

My problem is getting the meta-data included in the stream.

I just can't figure out how to enable this in icecast.xml

I have search the help files and googled myself cross eyed!

any help appreci8ated

regards

Robert

-- 
*Big Valley Radiio *
64 Warner Park Avenue

Laingholm

Auckland 0604

09 8176358

0221693124

06 650 6087
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160717/392bac4a/attachment.htm>

From damien at dcpendleton.plus.com  Fri Jul 22 18:39:11 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Fri, 22 Jul 2016 19:39:11 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <8B33E19A234C4A77B1CB18C357DB195D@Psycheman>

Hi there,
I am relatively new in the field of server administration, so please do bear with me if my question has an answer which seems blatantly obvious.
I recently installed the latest Icecast onto my machine and read the documentation in order to find out how to configure the server. Both the information in the docs, and even the example config file, seemed reasonablly self-explanatory.
After successfully configuring and starting the server I decided to see if I could get something to stream. I started up my streamer and was able to successfully connect.
Then I decided to see whether I could connect to the stream as a listener. Here's where the problems started. My media player refused point blank to connect to the stream.
I then tried accessing the stream directly from the url and found to my surprise that the stream was working. Since my browser has stream playback support, it started playing straight away.
Once I was pretty sure that I could connect, albeit in a nonstandard way, to my stream and server interface on localhost, I then decided to see if my stream was being broadcast to the world. Unfortunately that failed in all areas. Despite having forwarded my ports through my router, tried all sorts of combinations, with many more references to the documentation and server/streamer restarts, I could not access it through my domain address whatsoever.
I then attempted to reconfigure the server hostname to my domain and the streamer to point to my domain, but that failed. The streamer wouldn't even connect.
At this point I?m out of ideas and am beginning to feel, if I may use this expression, crushed by the ice!
So, I'm wondering:
1. Playback: I initially thought this was to do with extensions, but since I was encoding in mp3, I didn't think an extension was needed. Could there be any other reason as to why my browser is playing but my media player isn't?
2. Mountpoints: I noticed that when configuring, mountpoints were only either used for Shoutcast compatibility or for more advanced control. Does the server simply create the mountpoint specified in the stream settings?
3. Format: Again, I noticed that the server has no way to specify what format it needs to use. Is that also defined by the stream somehow?
4. Outside world: Is this something to do with bound addresses and the like? I can't imagine it somehow, because I think all those are to do with your hosts file and again, the documentation said this was an advanced topic. If not then what else, if anything, am I missing?
5. 32 v. 64 bit: I am running a 64-bit system but could only find a 32-bit Icecast. Does this matter?

System configuration looks like this:
OS: Windows 7 64-bit (SP1 Build 7601)
Browser: Mozilla Firefox 47.0.1
Icecast: 2.4.3
Streamer: SAM 3.8.3 alongside Station Playlist Studio 5.11
Media player: Winamp 5.7.3323

Any help appreciated.
Thanks.
Damien.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/3c60700e/attachment.htm>

From epirat07 at gmail.com  Fri Jul 22 19:41:10 2016
From: epirat07 at gmail.com (Marvin Scholz)
Date: Fri, 22 Jul 2016 21:41:10 +0200
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <8B33E19A234C4A77B1CB18C357DB195D@Psycheman>
References: <8B33E19A234C4A77B1CB18C357DB195D@Psycheman>
Message-ID: <8034D4A0-C382-4E17-BE75-389CA8458C99@gmail.com>

On 22 Jul 2016, at 20:39, Damien Sykes-Lindley wrote:

> Hi there,
Hello!

> [?]
> I then tried accessing the stream directly from the url and found to 
> my surprise that the stream was working. Since my browser has stream 
> playback support, it started playing straight away.

If your browser is able to play the stream, Icecast works and if it does 
not with a different player, that's likely a player issue or you used 
the wrong URL.

> Once I was pretty sure that I could connect, albeit in a nonstandard 
> way, to my stream and server interface on localhost, I then decided to 
> see if my stream was being broadcast to the world. Unfortunately that 
> failed in all areas. Despite having forwarded my ports through my 
> router, tried all sorts of combinations, with many more references to 
> the documentation and server/streamer restarts, I could not access it 
> through my domain address whatsoever.

Make sure you are not explicitly binding Icecast to 127.0.0.1 as then, 
it would not be possible to access it by other means than using 
localhost. If it was working before in your browser using the local 
address, than it's likely that it's not a problem with Icecast or how it 
is configured.

> [?]
> So, I'm wondering:
> 1. Playback: I initially thought this was to do with extensions, but 
> since I was encoding in mp3, I didn't think an extension was needed. 
> Could there be any other reason as to why my browser is playing but my 
> media player isn't?
See above.

> 2. Mountpoints: I noticed that when configuring, mountpoints were only 
> either used for Shoutcast compatibility or for more advanced control. 
> Does the server simply create the mountpoint specified in the stream 
> settings?
Yes, if you do not require special configuration for a specific 
mountpoint, you can just use the source password with your source client 
and Icecast will implicitly "create" the mountpoint set in your source 
client.

> 3. Format: Again, I noticed that the server has no way to specify what 
> format it needs to use. Is that also defined by the stream somehow?
The server does not do any transcoding, it knows the format based on the 
content-type, so there is no need to set it. All the encoding is done by 
your source client.

> 4. Outside world: Is this something to do with bound addresses and the 
> like? I can't imagine it somehow, because I think all those are to do 
> with your hosts file and again, the documentation said this was an 
> advanced topic. If not then what else, if anything, am I missing?
No idea, never had such problems, maybe someone else is able to provide 
more information about this.

> 5. 32 v. 64 bit: I am running a 64-bit system but could only find a 
> 32-bit Icecast. Does this matter?
There is no 64 bit version of Icecast, that's not problem. You can just 
use the 32-bit Icecast on a 64 bit system.

>
> System configuration looks like this:
> OS: Windows 7 64-bit (SP1 Build 7601)
> Browser: Mozilla Firefox 47.0.1
> Icecast: 2.4.3
> Streamer: SAM 3.8.3 alongside Station Playlist Studio 5.11
> Media player: Winamp 5.7.3323
You might want to try some other player, like the VLC media player and 
tell us if it works with that, as it should.

> Any help appreciated.
> Thanks.
> Damien.


From damien at dcpendleton.plus.com  Fri Jul 22 20:21:50 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Fri, 22 Jul 2016 21:21:50 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <8034D4A0-C382-4E17-BE75-389CA8458C99@gmail.com>
References: <8B33E19A234C4A77B1CB18C357DB195D@Psycheman>
 <8034D4A0-C382-4E17-BE75-389CA8458C99@gmail.com>
Message-ID: <7A356B147FBB47C1AEEE09C948194676@Psycheman>

Hi Marvin,
Thanks for the clarifications.
I didn't enter any address in the <listen-socket> section, just a port. The 
example came with the 127.0.0.1 commented out, so I removed it altogether.
The only other thing I can think of is the hostname in the main <icecast> 
section, but that is set to my domain address, not to localhost or any IP 
address, local or otherwise.
Cheers.



From awi3 at live.com  Fri Jul 22 20:31:04 2016
From: awi3 at live.com (Alan Bowness)
Date: Fri, 22 Jul 2016 21:31:04 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS713017E9472D21ED1BE35FEF0A0@phx.gbl>

try the IP of the server, and port ford ward that.
my best guess, works on a machine with localhost, if you port forward the localhosts IP




From: Damien Sykes-Lindley 
Sent: Friday, July 22, 2016 9:21 PM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi Marvin,
Thanks for the clarifications.
I didn't enter any address in the <listen-socket> section, just a port. The 
example came with the 127.0.0.1 commented out, so I removed it altogether.
The only other thing I can think of is the hostname in the main <icecast> 
section, but that is set to my domain address, not to localhost or any IP 
address, local or otherwise.
Cheers.

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/3b0a4555/attachment.htm>

From damien at dcpendleton.plus.com  Fri Jul 22 20:54:29 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Fri, 22 Jul 2016 21:54:29 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS713017E9472D21ED1BE35FEF0A0@phx.gbl>
References: <DUB408-EAS713017E9472D21ED1BE35FEF0A0@phx.gbl>
Message-ID: <69C139CED8B1478A86C382414DCE14D3@Psycheman>

Hi Alan,
In actual fact, I?m having to test everything (server, streamer and player) on the same machine, which is configured in my router to be the server. I have opened the port specified in my config and the port after it and I have set it to allow both TCP and UDP, as I didn?t know which it used.
I have also tried setting the hostname to my external IP address rather than a domain, and have even tried linking the port to a bound address, nothing. In fact if I specify a bind-address it actually comes up with an error when starting the server itself.
Cheers.
Damien.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/c5e8641b/attachment.htm>

From jeffares.robert at gmail.com  Fri Jul 22 21:08:08 2016
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Sat, 23 Jul 2016 09:08:08 +1200
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS713017E9472D21ED1BE35FEF0A0@phx.gbl>
References: <DUB408-EAS713017E9472D21ED1BE35FEF0A0@phx.gbl>
Message-ID: <57928B38.80605@gmail.com>



On 23/07/16 08:31, Alan Bowness wrote:
> The only other thing I can think of is the hostname in the main <icecast>
> section, but that is set to my domain address, not to localhost or any IP
> address, local or otherwise
hostname should be the 'name' of your host computer. I use ip address so 
hostname = 192.168.x.x  or 10.0.0.x or whatever your network uses
make sure your computer has a FIXED not a DYNAMIC IP address.

On your router you need to set up port forwarding so that the outside 
world looking at your modem/router address on port 8000 is directed to 
the host running Icecast .

If you get stuck; post your icecast.xml

regards

Robert

-- 
*Communication Consultants*
64 Warner Park Avenue

Laingholm

Auckland 0604

09 8176358

0221693124

06 650 6087
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/ce4645e0/attachment.htm>

From awi3 at live.com  Fri Jul 22 21:12:09 2016
From: awi3 at live.com (Alan Bowness)
Date: Fri, 22 Jul 2016 22:12:09 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS375CF38EC9C9B33639FC708EF0A0@phx.gbl>

I use a few raspberry pi?s and leave the icecast settings as localhost, and run darkice on the same Pi, I have let the router know to pass requests to port 8000 to the IP of the Pi.
Using your external IP is not right, if your server is say 192.168.1.21 thats the port forward, just be sure that the ports you use are in the router too, udp/tcp I use both myself watch for typos.

I think you are looking into it too far, its basic really, sometimes I find rebooting the router (depends on type) will open the ports after a config change within the router, find its system settings in router, and use the reboot option if you can find it, else a cold boot ? switch it off for 30sec.

Regards

From: Damien Sykes-Lindley 
Sent: Friday, July 22, 2016 9:54 PM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi Alan,
In actual fact, I?m having to test everything (server, streamer and player) on the same machine, which is configured in my router to be the server. I have opened the port specified in my config and the port after it and I have set it to allow both TCP and UDP, as I didn?t know which it used.
I have also tried setting the hostname to my external IP address rather than a domain, and have even tried linking the port to a bound address, nothing. In fact if I specify a bind-address it actually comes up with an error when starting the server itself.
Cheers.
Damien.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/08eeaa25/attachment.htm>

From jeffares.robert at gmail.com  Fri Jul 22 21:31:15 2016
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Sat, 23 Jul 2016 09:31:15 +1200
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS375CF38EC9C9B33639FC708EF0A0@phx.gbl>
References: <DUB408-EAS375CF38EC9C9B33639FC708EF0A0@phx.gbl>
Message-ID: <579290A3.5090904@gmail.com>

Hi Alan,

Icecast set up is almost too easy:
heres the checklist

Give your server a fixed IP In Windows this is easy and there are plenty 
of help files.
Make sure you get the DNS number right. Various modem routers default to 
192.168.1.1 or 192.168.1.254 or variants of 10.x.x.x

in a console [ black screen with c:> under accessories] type ipconfig 
<enter>  to see what you have now.

On your router set up port fowarding so the outside world connects to 
your router on x.x.x.x and port 8000 is fowarded to the fixed IP of your 
server.

You can get in to your router by typing 192.168.1.1 [or whatever it is] 
in a browser and the username admin password admin for 99% of the time.

Configure icecast.xml as below; this is from a linux server but 
basically it's the same

<icecast>
     <!-- location and admin are two arbitrary strings that are e.g. visible
          on the server info page of the icecast web interface
          (server_version.xsl). -->
     <location>putsomethinginhere</location>
     <admin>youremail at somewhere/admin>

     <limits>
         <clients>100</clients>			<--- note increases on defaults
         <sources>20</sources>
         <threadpool>15</threadpool>
         <queue-size>524288</queue-size>
         <client-timeout>30</client-timeout>
         <header-timeout>15</header-timeout>
         <source-timeout>10</source-timeout>
         <!-- If enabled, this will provide a burst of data when a client
              first connects, thereby significantly reducing the startup
              time for listeners that do substantial buffering. However,
              it also significantly increases latency between the source
              client and listening client.  For low-latency setups, you
              might want to disable this. -->
         <burst-on-connect>1</burst-on-connect>
         <!-- same as burst-on-connect, but this allows for being more
              specific on how much to burst. Most people won't need to
              change from the default 64k. Applies to all mountpoints  -->
         <burst-size>65535</burst-size>
     </limits>

     <authentication>
         <!-- Sources log in with username 'source' -->
         <source-password>somepassword</source-password>
         <!-- Relays log in username 'relay' -->
         <relay-password>somepassword</relay-password>

         <!-- Admin logs in with the username given below -->
         <admin-user>admin</admin-user>
         <admin-password>somepassword</admin-password>
     </authentication>

     <!-- set the mountpoint for a shoutcast source to use, the default if not
          specified is /stream but you can change it here if an alternative is
          wanted or an extension is required
     <shoutcast-mount>/live.nsv</shoutcast-mount>
     -->

     <!-- Uncomment this if you want directory listings -->
     <!--
     <directory>
         <yp-url-timeout>15</yp-url-timeout>
         <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
     </directory>
      -->

     <!-- This is the hostname other people will use to connect to your server.
     It affects mainly the urls generated by Icecast for playlists and yp
     listings. -->
     <hostname>192.168.0.30</hostname>					<-- this is where you put the server "name"

     <!-- You may have multiple <listener> elements -->
     <listen-socket>
         <port>8000</port>
        <!-- <bind-address>127.0.0.1</bind-address> -->			<-- the <!-- and --> comment the line out
         <!-- <shoutcast-mount>/stream</shoutcast-mount> -->
     </listen-socket>

     <listen-socket>
         <port>8004</port>
     </listen-socket>

     <!--<master-server>127.0.0.1</master-server>-->
     <!--<master-server-port>8001</master-server-port>-->
     <!--<master-update-interval>120</master-update-interval>-->
     <!--<master-password>hackme</master-password>-->

     <!-- setting this makes all relays on-demand unless overridden, this is
          useful for master relays which do not have <relay> definitions here.
          The default is 0 -->
     <!--<relays-on-demand>1</relays-on-demand>-->

     <!--
     <relay>
         <server>127.0.0.1</server>
         <port>8001</port>
         <mount>/example.ogg</mount>
         <local-mount>/different.ogg</local-mount>
         <on-demand>0</on-demand>

         <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
     </relay>
     -->

     <!-- Only define a <mount> section if you want to use advanced options,
          like alternative usernames or passwords -->


<!--    <mount>
         <mount-name>/thewirelessstation.mp3</mount-name>			<-- ignore this and leave defaults. I have this set up for something.

         <username>someuser</username>
         <password>somepassword</password>



         <max-listeners>100</max-listeners>
         <burst-size>65536</burst-size>

     <stream-name>The Wireless Station 1530kHz Hawkes Bay</stream-name>
     <stream-description>The best music you ever will hear</stream-description>

     </mount>
-->

     <fileserve>1</fileserve>

     <paths>
		<!-- basedir is only used if chroot is enabled -->
         <basedir>/usr/share/icecast2</basedir>

         <!-- Note that if <chroot> is turned on below, these paths must both
              be relative to the new root, not the original root -->
         <logdir>/var/log/icecast2</logdir>
         <webroot>/usr/share/icecast2/web</webroot>
         <adminroot>/usr/share/icecast2/admin</adminroot>
         <!-- <pidfile>/usr/share/icecast2/icecast.pid</pidfile> -->

         <!-- Aliases: treat requests for 'source' path as being for 'dest' path
              May be made specific to a port or bound address using the "port"
              and "bind-address" attributes.
           -->
         <!--
         <alias source="/foo" destination="/bar"/>
           -->
         <!-- Aliases: can also be used for simple redirections as well,
              this example will redirect all requests for http://server:port/ to
              the status page
           -->
         <alias source="/" destination="/status.xsl"/>
     </paths>

     <logging>
         <accesslog>access.log</accesslog>
         <errorlog>error.log</errorlog>
         <!-- <playlistlog>playlist.log</playlistlog> -->
       	<loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
       	<logsize>10000</logsize> <!-- Max size of a logfile -->
         <!-- If logarchive is enabled (1), then when logsize is reached
              the logfile will be moved to [error|access|playlist].log.DATESTAMP,
              otherwise it will be moved to [error|access|playlist].log.old.
              Default is non-archive mode (i.e. overwrite)
         -->
         <!-- <logarchive>1</logarchive> -->
     </logging>

     <security>						<-- not sure what happens in windows but the default will work
         <chroot>0</chroot>
         <!--
         <changeowner>
             <user>nobody</user>
             <group>nogroup</group>
         </changeowner>
         -->
     </security>
</icecast>


This should help

regards
Robert


-- 
*Communication Consultants*
64 Warner Park Avenue

Laingholm

Auckland 0604

09 8176358

0221693124

06 650 6087
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/174f643e/attachment.htm>

From tjudd at illinois.edu  Fri Jul 22 21:01:23 2016
From: tjudd at illinois.edu (Judd, Taylor Allen)
Date: Fri, 22 Jul 2016 21:01:23 +0000
Subject: [Icecast] Log visualization
Message-ID: <F50ECDBD5F40F04F8510FE619C6C02D19F731323@chimbx2.ad.uillinois.edu>

Is anyone doing anything fun with their logs? Visualizing it for non-technical folks?  Trying to find a way to analyze unique listeners, start/stop time, length listened to on average, potentially even broken down by hour.

I've played around with awstats, goaccess.io  even tablaue.   So far without a lot of heavy editing I've yet to get anything solid and even then it's not that great.  Most the tools I've found are focused on web logs, not streaming services.

Other successes in this area? Avenues of approach I haven't considered?

Thanks,
Taylor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/22f7079e/attachment.htm>

From awi3 at live.com  Fri Jul 22 21:40:52 2016
From: awi3 at live.com (Alan Bowness)
Date: Fri, 22 Jul 2016 22:40:52 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS309FB81134BD41EF00742B7EF0A0@phx.gbl>


>Hi Alan,

Best direct it to: Damien
Hi... anyway 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/b3aa3891/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wlEmoticon-smile[1].png
Type: image/png
Size: 1046 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/b3aa3891/attachment.png>

From epirat07 at gmail.com  Fri Jul 22 21:58:37 2016
From: epirat07 at gmail.com (Marvin Scholz)
Date: Fri, 22 Jul 2016 23:58:37 +0200
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <57928B38.80605@gmail.com>
References: <DUB408-EAS713017E9472D21ED1BE35FEF0A0@phx.gbl>
 <57928B38.80605@gmail.com>
Message-ID: <3ABE592E-94B2-4D0D-BDB7-DC31E77A8235@gmail.com>

On 22 Jul 2016, at 23:08, Robert Jeffares wrote:

> On 23/07/16 08:31, Alan Bowness wrote:
>> The only other thing I can think of is the hostname in the main 
>> <icecast>
>> section, but that is set to my domain address, not to localhost or 
>> any IP
>> address, local or otherwise
> hostname should be the 'name' of your host computer. I use ip address 
> so hostname = 192.168.x.x  or 10.0.0.x or whatever your network uses
> make sure your computer has a FIXED not a DYNAMIC IP address.
Actually, is he wants to use his Icecast instance from the Internet, the 
hostname SHOULD NOT be set to internal IP (like 192.168.x.x  or 
10.0.0.x). But generally this does not matter for connecting from the 
outside. That is not affected at all by the hostname configured. It's 
important for some things on the web interface and the playlists to work 
properly and especially for yellow page (Icecast directory) listings, so 
it's important it's set correct but does not impact the ability to 
connect to the server.

>
> On your router you need to set up port forwarding so that the outside 
> world looking at your modem/router address on port 8000 is directed to 
> the host running Icecast .
>
> If you get stuck; post your icecast.xml
>
> regards
>
> Robert
>
> -- 
> *Communication Consultants*
> 64 Warner Park Avenue
>
> Laingholm
>
> Auckland 0604
>
> 09 8176358
>
> 0221693124
>
> 06 650 6087
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From epirat07 at gmail.com  Fri Jul 22 22:03:15 2016
From: epirat07 at gmail.com (Marvin Scholz)
Date: Sat, 23 Jul 2016 00:03:15 +0200
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS375CF38EC9C9B33639FC708EF0A0@phx.gbl>
References: <DUB408-EAS375CF38EC9C9B33639FC708EF0A0@phx.gbl>
Message-ID: <BC776871-BC77-4116-B73B-E764590BE954@gmail.com>

On 22 Jul 2016, at 23:12, Alan Bowness wrote:

> I use a few raspberry pi?s and leave the icecast settings as 
> localhost, and run darkice on the same Pi, I have let the router know 
> to pass requests to port 8000 to the IP of the Pi.
> Using your external IP is not right, if your server is say 
> 192.168.1.21 thats the port forward, just be sure that the ports you 
> use are in the router too, udp/tcp I use both myself watch for typos.
The hostname should be set to the external hostname of the server, NOT 
the internal IP (like 192.168.x.x) unless you only use Icecast in your 
private network and do not want to use it from the internet.

>
> I think you are looking into it too far, its basic really, sometimes I 
> find rebooting the router (depends on type) will open the ports after 
> a config change within the router, find its system settings in router, 
> and use the reboot option if you can find it, else a cold boot ? 
> switch it off for 30sec.
>
> Regards
>
> From: Damien Sykes-Lindley
> Sent: Friday, July 22, 2016 9:54 PM
> To: Icecast streaming server user discussions
> Subject: Re: [Icecast] Config and other areas of struggle
>
> Hi Alan,
> In actual fact, I?m having to test everything (server, streamer and 
> player) on the same machine, which is configured in my router to be 
> the server. I have opened the port specified in my config and the port 
> after it and I have set it to allow both TCP and UDP, as I didn?t 
> know which it used.
> I have also tried setting the hostname to my external IP address 
> rather than a domain, and have even tried linking the port to a bound 
> address, nothing. In fact if I specify a bind-address it actually 
> comes up with an error when starting the server itself.
> Cheers.
> Damien.
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From awi3 at live.com  Fri Jul 22 22:31:23 2016
From: awi3 at live.com (Alan Bowness)
Date: Fri, 22 Jul 2016 23:31:23 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS19977E1F408549C965E4F00EF0A0@phx.gbl>

I use it for streaming 24/7/365 on the WAN ? no issues at all in using the default ?localhost?, sometimes I may use the LAN assigned IP too.
Though it is just a constant stream, no tunes or play lists are used here. So I have no experience with that, though port forwarding is part of my day job in regard to anything ?servers?.

I still think it?s a simple forwarding/addressing thing, else wouldn't have chipped in, though I do like to try now and then.

You did not explain why ?The hostname should be set to the external hostname of the server, NOT 
the internal IP (like 192.168.x.x) unless you only use Icecast in your private network and do not want to use it from the internet? 

It?s not constructive at all, to me, or anyone who does not comprehend the reasons why one should NOT do that.

BTW, Damien has the issue, not me.

Be nice to know why I should not do what I do, do, with my Pi?s though

Regards


From: Marvin Scholz 
Sent: Friday, July 22, 2016 11:03 PM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

On 22 Jul 2016, at 23:12, Alan Bowness wrote:

> I use a few raspberry pi?s and leave the icecast settings as 
> localhost, and run darkice on the same Pi, I have let the router know 

The hostname should be set to the external hostname of the server, NOT 
the internal IP (like 192.168.x.x) unless you only use Icecast in your 
private network and do not want to use it from the internet.





 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/58433088/attachment.htm>

From jeffares.robert at gmail.com  Fri Jul 22 22:34:25 2016
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Sat, 23 Jul 2016 10:34:25 +1200
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <BC776871-BC77-4116-B73B-E764590BE954@gmail.com>
References: <DUB408-EAS375CF38EC9C9B33639FC708EF0A0@phx.gbl>
 <BC776871-BC77-4116-B73B-E764590BE954@gmail.com>
Message-ID: <57929F71.6020406@gmail.com>

Hi Marvin,

On 23/07/16 10:03, Marvin Scholz wrote:
>>
> The hostname should be set to the external hostname of the server, NOT 
> the internal IP (like 192.168.x.x) unless you only use Icecast in your 
> private network and do not want to use it from the internet. 

I must disagree.
I have a site [ one of several running icecast2] where we have 2 icecast 
servers one primary and one backup.
They are on the same IP network
We have 2 external IP's both running fibre.
This allows us to feed audio from server A or server B via IP 1 or IP 2  
because either network can and has 'gone down' and sometimes one or 
other server has failed. [usually power; either UPS or mains]
We have outages; we don't have disruption.
The hostname has to be ' the buck stops here' and the ip address of the 
host is preferable because M$ name resolution is not 100% perfect and 
it's one less thing to go wrong. The external IP address of your 
modem/router is a waypoint.
I have also found that regardless of any instructions this is what you 
have to do to get it to work.

In this instance the network runs both Windows and Linux machines to 
enable end users to us the software they prefer, while Linux does the 
heavy lifting.

Each router is set to point external clients on port 8000 or 8004 to one 
or other of the servers on port 8000.
One of our external clients is a streaming server, four others are 
repeaters of the programme.
We have a main and a fall back option at each client location.

I have 5 possibly 6 Icecast servers all configured the same. The IP 
address of the host is used in the <hostname></hostname> setting.

regards

Robert Jeffares



-- 
*Communication Consultants*
64 Warner Park Avenue

Laingholm

Auckland 0604

09 8176358

0221693124

06 650 6087
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/fbd957e9/attachment.htm>

From thatjackelliott at kpov.org  Sat Jul 23 00:48:18 2016
From: thatjackelliott at kpov.org (that Jack Elliott)
Date: Fri, 22 Jul 2016 17:48:18 -0700
Subject: [Icecast] Icecast source client on Raspberry Pi?
Message-ID: <13003daa-10d8-2793-71be-96c3d495d9fb@kpov.org>

Anyone know if there is any code for a Raspberry Pi to use it as a 
source client?

-- 
Jack Elliott
Producer, The Point Wednesday
Host, The Sunday Classics
KPOV 88.9 High Desert Radio
kpov.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160722/965185d5/attachment.htm>

From un at aporee.org  Sat Jul 23 07:30:32 2016
From: un at aporee.org (unosonic)
Date: Sat, 23 Jul 2016 09:30:32 +0200
Subject: [Icecast] Icecast source client on Raspberry Pi?
In-Reply-To: <13003daa-10d8-2793-71be-96c3d495d9fb@kpov.org>
References: <13003daa-10d8-2793-71be-96c3d495d9fb@kpov.org>
Message-ID: <20160723073032.GA6606@aporee.org>

that Jack Elliott:
> Anyone know if there is any code for a Raspberry Pi to use it as a
> source client?


for live / line in from your sound device, just install darkice
https://stmllr.net/blog/live-mp3-streaming-from-audio-in-with-darkice-and-icecast2-on-raspberry-pi/

/u


From damien at dcpendleton.plus.com  Sat Jul 23 08:39:21 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 09:39:21 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <57928B38.80605@gmail.com>
References: <DUB408-EAS713017E9472D21ED1BE35FEF0A0@phx.gbl>
 <57928B38.80605@gmail.com>
Message-ID: <9E9D85C839334EE18DC2661986D23214@Psycheman>

Hi all,
OK, this stuff about internal and external IP addresses is confusing me. I always thought that an internal IP address (192.168.x.x) was for running things on a network, and an external for running things on the internet.
I use 192.168.1.254 to log into my router and have forwarded port 28888 (8000 is already being used by another server I?m running) for Icecast, as specified in the <listen-socket> section. The router doesn?t ask me for an IP address, but instead gives me a list of connected machines.
My config file is below.
<icecast>
<location>Wherever</location>
<admin>contact</admin>
<hostname>home.dayme.me</hostname> <!-- home.dayme.me resolves to my machine's external IP address (81.174.146.88), which is static. -->

<limits>
<clients>100</clients>
<sources>2</sources>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-size>65535</burst-size>
</limits>

<authentication>
<source-password>blah</source-password>
<relay-password>whatever</relay-password>
<admin-user>admin</admin-user>
<admin-password>ahem-ahem</admin-password>
</authentication>

<listen-socket>
<port>28888</port>
</listen-socket>

<http-headers>
<header name="Access-Control-Allow-Origin" value="*" />
</http-headers>

<fileserve>1</fileserve>

<paths>
<logdir>./log</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<alias source="/" destination="/status.xsl"/>
</paths>

<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<logsize>10000</logsize> <!-- Max size of a logfile -->
<logarchive>1</logarchive>
</logging>
</icecast>

Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/8db1e3d2/attachment.htm>

From awi3 at live.com  Sat Jul 23 09:01:57 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 10:01:57 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS9366950606EB0F68911319EF0B0@phx.gbl>

Confused me for ages.. until one day! 

Which out of the listed machines (on the router) is the one you are needing the port forwarded to? 
Forward that machine to the port you require, I would have used a lower port number 8010 or another unused port.




From: Damien Sykes-Lindley 
Sent: Saturday, July 23, 2016 9:39 AM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi all,
OK, this stuff about internal and external IP addresses is confusing me. I always thought that an internal IP address (192.168.x.x) was for running things on a network, and an external for running things on the internet.
I use 192.168.1.254 to log into my router and have forwarded port 28888 (8000 is already being used by another server I?m running) for Icecast, as specified in the <listen-socket> section. The router doesn?t ask me for an IP address, but instead gives me a list of connected machines.
My config file is below.
<icecast>
<location>Wherever</location>
<admin>contact</admin>
<hostname>home.dayme.me</hostname> <!-- home.dayme.me resolves to my machine's external IP address (81.174.146.88), which is static. -->

<limits>
<clients>100</clients>
<sources>2</sources>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-size>65535</burst-size>
</limits>

<authentication>
<source-password>blah</source-password>
<relay-password>whatever</relay-password>
<admin-user>admin</admin-user>
<admin-password>ahem-ahem</admin-password>
</authentication>

<listen-socket>
<port>28888</port>
</listen-socket>

<http-headers>
<header name="Access-Control-Allow-Origin" value="*" />
</http-headers>

<fileserve>1</fileserve>

<paths>
<logdir>./log</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<alias source="/" destination="/status.xsl"/>
</paths>

<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<logsize>10000</logsize> <!-- Max size of a logfile -->
<logarchive>1</logarchive>
</logging>
</icecast>

Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/3792208b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wlEmoticon-smile[1].png
Type: image/png
Size: 1046 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/3792208b/attachment.png>

From awi3 at live.com  Sat Jul 23 09:04:29 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 10:04:29 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS118D09910DC116948DC8935EF0B0@phx.gbl>

Dan... 
I see icecast on the external IP..
Its working, though theres no stream being sent to it
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/a2bc0c4e/attachment.htm>

From damien at dcpendleton.plus.com  Sat Jul 23 09:11:08 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 10:11:08 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS9366950606EB0F68911319EF0B0@phx.gbl>
References: <DUB408-EAS9366950606EB0F68911319EF0B0@phx.gbl>
Message-ID: <627E3021BA29482BBAEE2B9B9C576419@Psycheman>

Hi Alan,
Yes, this is what I am saying. The ports are already forwarded. Still no go.
Cheers.


From: Alan Bowness 
Sent: Saturday, July 23, 2016 10:01 AM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Confused me for ages.. until one day! 

Which out of the listed machines (on the router) is the one you are needing the port forwarded to? 
Forward that machine to the port you require, I would have used a lower port number 8010 or another unused port.




From: Damien Sykes-Lindley 
Sent: Saturday, July 23, 2016 9:39 AM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi all,
OK, this stuff about internal and external IP addresses is confusing me. I always thought that an internal IP address (192.168.x.x) was for running things on a network, and an external for running things on the internet.
I use 192.168.1.254 to log into my router and have forwarded port 28888 (8000 is already being used by another server I?m running) for Icecast, as specified in the <listen-socket> section. The router doesn?t ask me for an IP address, but instead gives me a list of connected machines.
My config file is below.
<icecast>
<location>Wherever</location>
<admin>contact</admin>
<hostname>home.dayme.me</hostname> <!-- home.dayme.me resolves to my machine's external IP address (81.174.146.88), which is static. -->

<limits>
<clients>100</clients>
<sources>2</sources>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-size>65535</burst-size>
</limits>

<authentication>
<source-password>blah</source-password>
<relay-password>whatever</relay-password>
<admin-user>admin</admin-user>
<admin-password>ahem-ahem</admin-password>
</authentication>

<listen-socket>
<port>28888</port>
</listen-socket>

<http-headers>
<header name="Access-Control-Allow-Origin" value="*" />
</http-headers>

<fileserve>1</fileserve>

<paths>
<logdir>./log</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<alias source="/" destination="/status.xsl"/>
</paths>

<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<logsize>10000</logsize> <!-- Max size of a logfile -->
<logarchive>1</logarchive>
</logging>
</icecast>

Cheers.



--------------------------------------------------------------------------------
_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/4de1a0e7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wlEmoticon-smile[1].png
Type: image/png
Size: 1046 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/4de1a0e7/attachment.png>

From awi3 at live.com  Sat Jul 23 09:19:45 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 10:19:45 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <627E3021BA29482BBAEE2B9B9C576419@Psycheman>
References: <DUB408-EAS9366950606EB0F68911319EF0B0@phx.gbl>
 <627E3021BA29482BBAEE2B9B9C576419@Psycheman>
Message-ID: <DUB408-EAS4213BAD2349D54A66AC5848EF0B0@phx.gbl>

What are you using to forward the 'music' to the Icecast server that I can see? If you are using darkice for example, have you configured the darkice.cfg so that it matches icecast's configuration? Icecast appears to be working, but has no stream.

If I knew what the passwords were, I could configure my darkice on my pi to forward music to your Icecast and it would stream it - you just need a source for Icecast to mount as far as I can see.

Regards

Sent from my iPhone

> On 23 Jul 2016, at 10:11, Damien Sykes-Lindley <damien at dcpendleton.plus.com> wrote:
> 
> Hi Alan,
> Yes, this is what I am saying. The ports are already forwarded. Still no go.
> Cheers.
>  
>  
> From: Alan Bowness
> Sent: Saturday, July 23, 2016 10:01 AM
> To: Icecast streaming server user discussions
> Subject: Re: [Icecast] Config and other areas of struggle
>  
> Confused me for ages.. until one day! <wlEmoticon-smile[1].png>
>  
> Which out of the listed machines (on the router) is the one you are needing the port forwarded to?
> Forward that machine to the port you require, I would have used a lower port number 8010 or another unused port.
>  
>  
>  
>  
> From: Damien Sykes-Lindley
> Sent: Saturday, July 23, 2016 9:39 AM
> To: Icecast streaming server user discussions
> Subject: Re: [Icecast] Config and other areas of struggle
>  
> Hi all,
> OK, this stuff about internal and external IP addresses is confusing me. I always thought that an internal IP address (192.168.x.x) was for running things on a network, and an external for running things on the internet.
> I use 192.168.1.254 to log into my router and have forwarded port 28888 (8000 is already being used by another server I?m running) for Icecast, as specified in the <listen-socket> section. The router doesn?t ask me for an IP address, but instead gives me a list of connected machines.
> My config file is below.
>  
> <icecast>
> <location>Wherever</location>
> <admin>contact</admin>
> <hostname>home.dayme.me</hostname> <!-- home.dayme.me resolves to my machine's external IP address (81.174.146.88), which is static. -->
>  
> <limits>
> <clients>100</clients>
> <sources>2</sources>
> <queue-size>524288</queue-size>
> <client-timeout>30</client-timeout>
> <header-timeout>15</header-timeout>
> <source-timeout>10</source-timeout>
> <burst-size>65535</burst-size>
> </limits>
>  
> <authentication>
> <source-password>blah</source-password>
> <relay-password>whatever</relay-password>
> <admin-user>admin</admin-user>
> <admin-password>ahem-ahem</admin-password>
> </authentication>
>  
> <listen-socket>
> <port>28888</port>
> </listen-socket>
>  
> <http-headers>
> <header name="Access-Control-Allow-Origin" value="*" />
> </http-headers>
>  
> <fileserve>1</fileserve>
>  
> <paths>
> <logdir>./log</logdir>
> <webroot>./web</webroot>
> <adminroot>./admin</adminroot>
> <alias source="/" destination="/status.xsl"/>
> </paths>
>  
> <logging>
> <accesslog>access.log</accesslog>
> <errorlog>error.log</errorlog>
> <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
> <logsize>10000</logsize> <!-- Max size of a logfile -->
> <logarchive>1</logarchive>
> </logging>
> </icecast>
>  
> Cheers.
>  
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/998f3dcc/attachment.htm>
-------------- next part --------------
_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

From damien at dcpendleton.plus.com  Sat Jul 23 09:28:40 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 10:28:40 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS4213BAD2349D54A66AC5848EF0B0@phx.gbl>
References: <DUB408-EAS9366950606EB0F68911319EF0B0@phx.gbl>
 <627E3021BA29482BBAEE2B9B9C576419@Psycheman>
 <DUB408-EAS4213BAD2349D54A66AC5848EF0B0@phx.gbl>
Message-ID: <149D31462F4249BCB125463D62485FFE@Psycheman>

Hi Alan,
Very interesting indeed. What URL are you looking at the status from? I?ve tried home.dayme.me:28888, 81.174.146.88:28888, when I am streaming I even tried the /mountpointname at the end, and all I keep getting is:
Unable to connect
Firefox can't establish a connection to the server at 81.174.146.88:28888.
If it?s working your end, that suggests that it is a problem trying to log in with the same machine. Bizarre.
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/90a35454/attachment.htm>

From awi3 at live.com  Sat Jul 23 09:34:22 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 10:34:22 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS3389635BF115EEDC06787ECEF0B0@phx.gbl>

Hi Damien (where Dan come from??)

I use 81.174.146.88:28888
Bet your router does not have loopback

So if you are using sam broadcaster it needs the icecast settings input to it, so it can forward to the icecast server.
If you use the local IP address of the icecast server you will see what I see.

Regards


From: Damien Sykes-Lindley 
Sent: Saturday, July 23, 2016 10:29 AM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi Alan,
Very interesting indeed. What URL are you looking at the status from? I?ve tried home.dayme.me:28888, 81.174.146.88:28888, when I am streaming I even tried the /mountpointname at the end, and all I keep getting is:
Unable to connect
Firefox can't establish a connection to the server at 81.174.146.88:28888.
If it?s working your end, that suggests that it is a problem trying to log in with the same machine. Bizarre.
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/6dba4496/attachment.htm>

From damien at dcpendleton.plus.com  Sat Jul 23 09:38:58 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 10:38:58 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS3389635BF115EEDC06787ECEF0B0@phx.gbl>
References: <DUB408-EAS3389635BF115EEDC06787ECEF0B0@phx.gbl>
Message-ID: <4175F724ECA54B09999FE99CDC8D813B@Psycheman>

Hi there,
It?s not Dan, it?s Dayme, shortened version of Damien. I didn?t want to use Dame for obvious reasons.
I think the encoder is set to broadcast on localhost. I tried to set my encoders to home.dayme.me but it wouldn?t connect. I?m streaming now, just me talking and trying to sort this out.
What do you mean about not having loopback? I can access all my other servers through my domain, just not this one.
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/f37d8948/attachment.htm>

From jeffares.robert at gmail.com  Sat Jul 23 09:42:14 2016
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Sat, 23 Jul 2016 21:42:14 +1200
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS3389635BF115EEDC06787ECEF0B0@phx.gbl>
References: <DUB408-EAS3389635BF115EEDC06787ECEF0B0@phx.gbl>
Message-ID: <466e03e0-d101-6cbf-b278-8145d3ac2026@gmail.com>

I can see it from here.

I should be able to mount a stream on it


The way you have it set up the stream on the same machine can't mount 
that address.

The port is being hogged by the router for router server only [ no local 
loopback ]

Use the machine IP and it wil work.


R



On 23/07/16 21:34, Alan Bowness wrote:
> Hi Damien (where Dan come from??)
> I use 81.174.146.88:28888
> Bet your router does not have loopback
> So if you are using sam broadcaster it needs the icecast settings 
> input to it, so it can forward to the icecast server.
> If you use the local IP address of the icecast server you will see 
> what I see.
> Regards
> *From:* Damien Sykes-Lindley <mailto:damien at dcpendleton.plus.com>
> *Sent:* Saturday, July 23, 2016 10:29 AM
> *To:* Icecast streaming server user discussions <mailto:icecast at xiph.org>
> *Subject:* Re: [Icecast] Config and other areas of struggle
> Hi Alan,
> Very interesting indeed. What URL are you looking at the status from? 
> I?ve tried home.dayme.me:28888, 81.174.146.88:28888, when I am 
> streaming I even tried the /mountpointname at the end, and all I keep 
> getting is:
> Unable to connect
> Firefox can't establish a connection to the server at 81.174.146.88:28888.
> If it?s working your end, that suggests that it is a problem trying to 
> log in with the same machine. Bizarre.
> Cheers.
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-- 
*Communication Consultants*
64 Warner Park Avenue

Laingholm

Auckland 0604

09 8176358

0221693124

06 650 6087
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/b13daa79/attachment.htm>

From damien at dcpendleton.plus.com  Sat Jul 23 09:53:50 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 10:53:50 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <466e03e0-d101-6cbf-b278-8145d3ac2026@gmail.com>
References: <DUB408-EAS3389635BF115EEDC06787ECEF0B0@phx.gbl>
 <466e03e0-d101-6cbf-b278-8145d3ac2026@gmail.com>
Message-ID: <6FC6B4C566604CED925E4454E890E3BA@Psycheman>

Hi,
I still don?t get what you mean about this loopback thing. I can access all my other available servers through either localhost or home.dayme.me. Are you saying that Icecast works slightly differently so can?t recognise this from the same machine it?s broadcasting from? Or is there a way to allow this somehow?
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/44f4d7c7/attachment.htm>

From awi3 at live.com  Sat Jul 23 10:37:28 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 11:37:28 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS84DA2F3A24AF6908EE90B7EF0B0@phx.gbl>

I think some fundamental misunderstanding thing is perhaps going on.

What is the icecast server that I can see here: http://home.dayme.me:28888 supposed to be streaming?

And

If you use the local IP of that icecast server on another local machine (or same machine) can you then see the admin page?

Go back to first line: 
What is the icecast server that I can see here: http://home.dayme.me:28888 supposed to be streaming?

Configure the thing that is sending info to this icecast server, and test locally again.
Worry about port forwarding later (not that this is an issue at all)

I?m fair at networking and have quite a bit of experience configuring icecast to work with darkice only.

Regards


From: Damien Sykes-Lindley 
Sent: Saturday, July 23, 2016 10:53 AM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi,
I still don?t get what you mean about this loopback thing. I can access all my other available servers through either localhost or home.dayme.me. Are you saying that Icecast works slightly differently so can?t recognise this from the same machine it?s broadcasting from? Or is there a way to allow this somehow?
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/0f489094/attachment.htm>

From damien at dcpendleton.plus.com  Sat Jul 23 10:48:34 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 11:48:34 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS84DA2F3A24AF6908EE90B7EF0B0@phx.gbl>
References: <DUB408-EAS84DA2F3A24AF6908EE90B7EF0B0@phx.gbl>
Message-ID: <CF1C1C1FD5B744229EC43D2088907F0E@Psycheman>

Hi Alan,
I am not currently streaming anything. Every now and then when I want to test something I?ll simply stream myself there with a mic pondering over things. When this is the case I can connect to the stream locally (through localhost) with no issue. Same for the server webpage. Again, though, I can only connect to the stream through the browser and not my media player. But I can?t connect at all through home.dayme.me or my external IP address.
This is what confuses me. You can connect through my domain and external IP. I can connect through localhost. But why can?t I connect through my domain or external IP?
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/a9207e30/attachment.htm>

From awi3 at live.com  Sat Jul 23 11:00:26 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 12:00:26 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <CF1C1C1FD5B744229EC43D2088907F0E@Psycheman>
References: <DUB408-EAS84DA2F3A24AF6908EE90B7EF0B0@phx.gbl>
 <CF1C1C1FD5B744229EC43D2088907F0E@Psycheman>
Message-ID: <DUB408-EAS1025CE8817B4263FB1A7ACBEF0B0@phx.gbl>

No loopback on router, try connecting via 3G to see. 
If there's no stream going to Icecast no media player can play nothing.
Firewall? Try switching it off for a few minutes and test.

You will get there!

Sent from my iPhone

> On 23 Jul 2016, at 11:49, Damien Sykes-Lindley <damien at dcpendleton.plus.com> wrote:
> 
> Hi Alan,
> I am not currently streaming anything. Every now and then when I want to test something I?ll simply stream myself there with a mic pondering over things. When this is the case I can connect to the stream locally (through localhost) with no issue. Same for the server webpage. Again, though, I can only connect to the stream through the browser and not my media player. But I can?t connect at all through home.dayme.me or my external IP address.
> This is what confuses me. You can connect through my domain and external IP. I can connect through localhost. But why can?t I connect through my domain or external IP?
> Cheers.
>  
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/7adcb773/attachment.htm>
-------------- next part --------------
_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

From damien at dcpendleton.plus.com  Sat Jul 23 11:28:01 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 12:28:01 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS1025CE8817B4263FB1A7ACBEF0B0@phx.gbl>
References: <DUB408-EAS84DA2F3A24AF6908EE90B7EF0B0@phx.gbl>
 <CF1C1C1FD5B744229EC43D2088907F0E@Psycheman>
 <DUB408-EAS1025CE8817B4263FB1A7ACBEF0B0@phx.gbl>
Message-ID: <FF6561BDDFF04B50948190591C3CBCA2@Psycheman>

Hi Alan,
OK. The only thing I still don?t understand now is this router loopback thing. If my router has no loopback, why does Icecast need this when other servers don?t? What does it do? Is loopback something that can be enabled/disabled?
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/a4f88e06/attachment.htm>

From awi3 at live.com  Sat Jul 23 11:38:02 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 12:38:02 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS9235602BC5DA62BB45930EF0B0@phx.gbl>

No, you can?t configure that loopback. if the other machines work using an external address it must be something else.
What mount point name are you using?

I still think you are very close to realising the issue.
I?m here for a while, and will help you if you need it.
remote desktop if you need.

Regards


From: Damien Sykes-Lindley 
Sent: Saturday, July 23, 2016 12:28 PM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi Alan,
OK. The only thing I still don?t understand now is this router loopback thing. If my router has no loopback, why does Icecast need this when other servers don?t? What does it do? Is loopback something that can be enabled/disabled?
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/c4abaa66/attachment.htm>

From damien at dcpendleton.plus.com  Sat Jul 23 12:03:16 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 13:03:16 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS9235602BC5DA62BB45930EF0B0@phx.gbl>
References: <DUB408-EAS9235602BC5DA62BB45930EF0B0@phx.gbl>
Message-ID: <BEDA5E56AA5D4EC691A8D8AF0FB8F2AE@Psycheman>

Hi Alan,
OK. I am now streaming on mountpoint /blah. I?m not streaming music just yet, but if the stream works you should hear me typing and other stuff. Life in my living room, if you like.
I still don?t understand why Icecast needs loopback when other servers don?t.
Here?s an example: I have an SCM system, Fossil server running on port 80 and 8000. I can access repositories on that server by either localhost/repo or home.dayme.me/repo.
I have an FTP server which, again, I can access on ftp://localhost or ftp://home.dayme.me.
Why can?t I do the same thing on Icecast?
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/28fe600b/attachment.htm>

From awi3 at live.com  Sat Jul 23 12:08:04 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 13:08:04 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS146FBCEE834E540C9480477EF0B0@phx.gbl>

i hear you and you realising you can hear yourself

congrats

From: Damien Sykes-Lindley 
Sent: Saturday, July 23, 2016 1:03 PM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi Alan,
OK. I am now streaming on mountpoint /blah. I?m not streaming music just yet, but if the stream works you should hear me typing and other stuff. Life in my living room, if you like.
I still don?t understand why Icecast needs loopback when other servers don?t.
Here?s an example: I have an SCM system, Fossil server running on port 80 and 8000. I can access repositories on that server by either localhost/repo or home.dayme.me/repo.
I have an FTP server which, again, I can access on ftp://localhost or ftp://home.dayme.me.
Why can?t I do the same thing on Icecast?
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/5dc2ab20/attachment.htm>

From damien at dcpendleton.plus.com  Sat Jul 23 12:12:29 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 13:12:29 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS146FBCEE834E540C9480477EF0B0@phx.gbl>
References: <DUB408-EAS146FBCEE834E540C9480477EF0B0@phx.gbl>
Message-ID: <229819EAAA5B49468B66E300266869BE@Psycheman>

Hi Alan,
Yes. But that?s only locally. My router is going to let me into my own servers locally anyway. What I want to be able to do is try and connect through home.dayme.me because, if for whatever reason anything happens, I?ll then know that maybe there?s a problem with my domain, or my ports have been reset, etc etc. At the moment I can?t check any of that because I can only connect through localhost.
Sorry about this. But I really want to get this sorted if at all possible.
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/6a88fe69/attachment.htm>

From awi3 at live.com  Sat Jul 23 12:17:03 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 13:17:03 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS5609F32EEDDE6B9C58209EEF0B0@phx.gbl>

I?m listening to you both,

Its working, but not for you locally, could be a firewall issue on your PC?
perhaps changing the port to 8010?
If other servers can be seen on the WAN from your internal network it could be a port conflict, or firewall issue.

Alan

From: Damien Sykes-Lindley 
Sent: Saturday, July 23, 2016 1:12 PM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi Alan,
Yes. But that?s only locally. My router is going to let me into my own servers locally anyway. What I want to be able to do is try and connect through home.dayme.me because, if for whatever reason anything happens, I?ll then know that maybe there?s a problem with my domain, or my ports have been reset, etc etc. At the moment I can?t check any of that because I can only connect through localhost.
Sorry about this. But I really want to get this sorted if at all possible.
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/fd8a78ec/attachment.htm>

From damien at dcpendleton.plus.com  Sat Jul 23 12:37:43 2016
From: damien at dcpendleton.plus.com (Damien Sykes-Lindley)
Date: Sat, 23 Jul 2016 13:37:43 +0100
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <DUB408-EAS5609F32EEDDE6B9C58209EEF0B0@phx.gbl>
References: <DUB408-EAS5609F32EEDDE6B9C58209EEF0B0@phx.gbl>
Message-ID: <A1D2F662450444E2875DCFCD59FA27AB@Psycheman>

Hi Alan,
All firewalls are switched off and I?ve changed the port to 8010. Still can?t access it from the global IP or domain name.
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/334e96e1/attachment.htm>

From awi3 at live.com  Sat Jul 23 12:41:54 2016
From: awi3 at live.com (Alan Bowness)
Date: Sat, 23 Jul 2016 13:41:54 +0100
Subject: [Icecast] Config and other areas of struggle
Message-ID: <DUB408-EAS12978A5A7B05D9184FE83E7EF0B0@phx.gbl>

email me direct to free up the forum
awi3 at live.com
I?ll chat with you on skype if you need to, but you were working fine, don?t worry about not being able to see yourself on the WAN just for now


From: Damien Sykes-Lindley 
Sent: Saturday, July 23, 2016 1:37 PM
To: Icecast streaming server user discussions 
Subject: Re: [Icecast] Config and other areas of struggle

Hi Alan,
All firewalls are switched off and I?ve changed the port to 8010. Still can?t access it from the global IP or domain name.
Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/41bd4fe3/attachment.htm>

From abitar.com at gmail.com  Sat Jul 23 13:17:22 2016
From: abitar.com at gmail.com (David Saunders)
Date: Sat, 23 Jul 2016 09:17:22 -0400
Subject: [Icecast] Config and other areas of struggle
In-Reply-To: <A1D2F662450444E2875DCFCD59FA27AB@Psycheman>
References: <DUB408-EAS5609F32EEDDE6B9C58209EEF0B0@phx.gbl>
 <A1D2F662450444E2875DCFCD59FA27AB@Psycheman>
Message-ID: <CAOjZz+n-=XQBL4bwC=MgdMW19Br1ozJSFgUVqvii+D6xPKLuGw@mail.gmail.com>

Hey,
  Can you access the status/admin page?  When we have clients or sources
who having issue with connecting to our server we  have them in the browser
see if they can access this page.  This will show if or if not there an
connection issue in the network.

The bigest issue we have is the client/source sides have firewall setup
blocking the connection.

one thing you can do use a a vpn like tunnelBear(i suggested this since it
free and install on many platforms) and check the connection back to your
network from outside of your network.  If your local connection is working
the vpn connection should would work.  unless your router has an firewall
issue of some kind.   some routers do not do a local loop back to the
external ip and some will l loop it back before firewall rules are applied!

firewall  can be in the server and on any the routers it has to go through.


Simple debug track:
using the admin/status  page http://<ip/name>:8000/ in  your favorite  web
browser.
  1> check localhost ( connection from the server computer ) using internal
ip
         -- Mainly checks to see if the server is available
  2> check local network ( from another machine other then the server)
using local ip.
         -- checks to see if you can access out the server. ( check server
firewall if fails, or make sure server icecast is listening to the right
network, check the client compute for connection issues).
  3> check external connection ( from a computer/connection external to
your network) using the public IP and if needed the public name.
          -- This If your using a external connection( is a vpn or dial up
) you should have a direct connection back to the public ip and the issue
would be in the router OR YOUR ISP is not allowing it.
          Check make sure the public name is working , it could be the DNS
is messed up some how or your dynamic DNS is not updating.

      --OR you can go to a another next work external from you network,
most external networks that are public access do not block port 8000/8001 I
have found but some private ones will. Business and some schools who only
allow a very restrictive range.

if you use ping/traceroute, your router has to be setup to replies to these
commands. It become common place to block this tool for fear of DOS attacks.

I went over board on my description so someone having issues in the future
with connections issues can work on it. This is how I track down issues
 when out server having issue wit client/source connections.

Pardon my interruption if I was to far off subject.

On Sat, Jul 23, 2016 at 8:37 AM, Damien Sykes-Lindley <
damien at dcpendleton.plus.com> wrote:

> Hi Alan,
> All firewalls are switched off and I?ve changed the port to 8010. Still
> can?t access it from the global IP or domain name.
> Cheers.
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160723/d02b3537/attachment.htm>

From bhathaway at focustsi.com  Tue Jul 26 19:00:54 2016
From: bhathaway at focustsi.com (Brett Hathaway)
Date: Tue, 26 Jul 2016 19:00:54 +0000
Subject: [Icecast] =?windows-1252?q?In_search_of_MIB_and_or_OID=92s?=
Message-ID: <6AF63C1FCBBBE34BA71AF86EDCC3E428024734DA@FOCUS-XMS1.focustsi.com>

Hello,

We need to capture the current listeners using SNMP OID?s. At this time I?m not able to locate a MIB or OID(s) needed to obtain this information for our monitoring system. Unfortunately we?re not using Cacti as my research has uncovered all kinds of information related to this application.  Any help would be greatly appreciated.

I was able to locate the following OID which I extracted out of a PHP script, but when I tried to ?GET? this OID it was not found: .1.3.6.1.4.1.2021.8000.4.1.2.1.73.1

Regards,
-Brett H.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160726/2d752e6b/attachment.htm>