Hi,
after upgrade seems to working all fine at the moment.

2 questions:

How to use the proxy80?  it appears "disabled" everywhere.
(What you mean for Experimental nginx-based port-80 proxy support ?)

The ssl mail doesn't work ( usually I use ssl://smtp.google.com in centova 2.2.6 and it works fine)
Output error is:
Error: Failed to connect socket: Unable to find the socket transport "ssl" - did you forget to enable it when you configured PHP?

How to use the proxy80?  it appears "disabled" everywhere.
(What you mean for Experimental nginx-based port-80 proxy support ?)

See the /usr/local/centovacast/sbin/setproxy utility.

The ssl mail doesn't work ( usually I use ssl://smtp.google.com in centova 2.2.6 and it works fine)
Output error is:
Error: Failed to connect socket: Unable to find the socket transport "ssl" - did you forget to enable it when you configured PHP?

Thanks, added to the to-do list.

See the /usr/local/centovacast/sbin/setproxy utility.

Ok.  Installed.
It seems to work really fine!    :-)

It works fine on Shoutcast 2

In shoutcast1 doesn't work because the pls file generated has the mp=/stream  not good for sh1.

If I edit pls  with mp=/    it works!

So you have to tell to the script to use  mp=/  if the stream is for shoutcast v1

Excellent observation -- thanks!  This will be fixed for the next build.

Hi Steve,
after upgrade, now proxy80 works fine with shoutcast1 but not in shoutcast2.

Same problem:  now the pls file generated for shoutcastV2 has for mountpoint  /  and not  /stream
Seems cc3 not pass the right mount in shoutcast2.

The opposite of before... 

Ah, this was a caching issue -- we have caching turned off on most of our test servers which is how this slipped past.

This is fixed and we'll be pushing out a new build soon.  Thanks!

The ssl mail doesn't work ( usually I use ssl://smtp.google.com in centova 2.2.6 and it works fine)
Output error is:
Error: Failed to connect socket: Unable to find the socket transport "ssl" - did you forget to enable it when you configured PHP?

Just an update -- OpenSSL support has been added for the next build, so this issue will be fixed once it's released.