Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: gerys on October 30, 2014, 01:55:55 am

Title: problem Authhash after update shoutcast
Post by: gerys on October 30, 2014, 01:55:55 am

hi since the new update of shoutcast our client get this error:

DEBUG [YP] Unable to process the request. Check the server logs for more details. 669

in the log file:

ERROR [YP] Request [https://yp.shoutcast.com/createauthhash] failed, code: 77 [error setting certificate verify locations: CAfile: /usr/local/centovacast/var/vhosts/radiofantasy/cacert.pem CApath: none]

What goes wrong here?

Title: Re: problem Authhash after update shoutcast
Post by: DrO on October 30, 2014, 03:26:25 am

it's an issue with how the DNAS finds certain files it needs. there will be a newer DNAS build which will resolve it that should be out by the end of today (30th Oct).

Title: Re: problem Authhash after update shoutcast
Post by: Punjab Rocks Radio on November 02, 2014, 09:36:07 pm

Hey gerys
Are you running any firewall and have blocked some port. Try disabling fiewall and then restart the streams..

Title: Re: problem Authhash after update shoutcast
Post by: DrO on November 03, 2014, 06:02:54 am

the issue which is mentioned was due to a specific DNAS bulld. with the current Centova + DNAS update (at the time of this reply), the issue shown above should not be happening for anyone.

Title: Re: problem Authhash after update shoutcast
Post by: Punjab Rocks Radio on November 03, 2014, 08:06:43 am

Thanks DrO for looking into this, but when I disable CSF firewall it starts to work. Is there is list of ports that this Shoutcast and Centovacast uses? My be I just have the needed port blocked.
Thanks

Title: Re: problem Authhash after update shoutcast
Post by: DrO on November 03, 2014, 01:15:03 pm

you do realise this thread was from a few days ago and relates to the 2.4.1 builds, as that's all i'm referring to in relation to what gerys had posted at the time (which was prior to the DNAS 2.4.2 / Centova 3.1.1 updates). not finding the certificate file is completely unrelated to anything with firewalls as the 77 error prevents the connections even being made i.e. the firewall never gets a chance to be involved.