Request [https://yp.shoutcast.com/yp2] failed, code: 28

[bobk37]

I'm getting the same error. I did notice this when I ran tsc_serv.exe setup

2020-06-01 23:11:39 ERROR [YP] Request [https://yp.shoutcast.com/yp2] failed, code: 60 [SSL certificate problem: certificate has expired]

[Googe]

Same happening to me.

Errors:
DEBUG log:
2020-06-01 21:30:41 DEBUG [YP] pvt_update add still pending for key=1 [1] [20]
2020-06-01 21:30:41 DEBUG [YP] Creating new curl handle for: https://yp.shoutcast.com/yp2
2020-06-01 21:30:41 DEBUG [YP] Request URL: https://yp.shoutcast.com/yp2
2020-06-01 21:30:42 ERROR [YP] Request [https://yp.shoutcast.com/yp2] failed, code: 60 [SSL certificate problem: certificate has expired]

CURL:
curl -vvI https://yp.shoutcast.com/yp2
* Trying 31.12.71.119...
* TCP_NODELAY set
* Connected to yp.shoutcast.com (31.12.71.119) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, Server hello (2):
* SSL certificate problem: certificate has expired
* stopped the pause stream!
* Closing connection 0


running really old Mac version...10_07_2011

[Googe]

Working again, as of 6/2:
Response code=[200]
2020-06-02 13:14:29 INFO [YP] Updating listing details for stream #1 succeeded.

Thanks to whomever!

[bobk37]

Yes - working correctly now. Thanks for fixing!

[RickoDean]

Now my server is working and public. Thanks to whomever rectified this. Meanwhile My radio manager is still showing 0 live listeners although my server counter has me at a little past 3200. I hope this gets fixed as well.

[Googe]

Whoops, new error...

2020-06-02 22:38:00 DEBUG [METRICS] Creating new curl handle for: https://metrics.shoutcast.com/metrics
2020-06-02 22:38:00 ERROR [METRICS] Request failed on https://metrics.shoutcast.com/metrics with SSL certificate problem: certificate has expired

[Busby]

Sorry to bump this.
I have 1 server running SHOUTcast Server v2.5.5.732/posix(linux x64) which is listing OK at Shoutcast, and another running the same version and the same authhash, but getting the following error:
Status: Unable to access the Directory.
Check the server log for more details.
The stream will behave like it is private.
I have checked both the streaming port and the next one are open.

I am working on updating to sc_serv_update_linux_x64_2_6_1_777 but have limited Linux skills so waiting for a friend to have time.

Can anyone help please with the directory listing.

[DJ Egg]

Sorry to bump this.
I have 1 server running SHOUTcast Server v2.5.5.732/posix(linux x64) which is listing OK at Shoutcast, and another running the same version and the same authhash, but getting the following error:
Status: Unable to access the Directory.
Check the server log for more details.
The stream will behave like it is private.
I have checked both the streaming port and the next one are open.

I am working on updating to sc_serv_update_linux_x64_2_6_1_777 but have limited Linux skills so waiting for a friend to have time.

Can anyone help please with the directory listing.

fr1.1mix.co.uk & fr3.1mix.co.uk servers are both on port 8060

In listenh.m3u, fr4.1mix.co.uk is listed as being on port 8000

This is the server with the streams that are "unable to access the directory".
Is the port config correct, or should it also be 8060?

[Busby]

fr1.1mix.co.uk & fr3.1mix.co.uk servers are both on port 8060

In listenh.m3u, fr4.1mix.co.uk is listed as being on port 8000

This is the server with the streams that are "unable to access the directory".
Is the port config correct, or should it also be 8060?

Many thanks for the reply.

I have 3 servers;

fr1.1mix.co.uk using port 8060
fr2.1mix.co.uk using ports 8000 and 8060
fr3.1mix.co.uk using ports 8000 and 8060

I have 2 playout systems and the plan was to have 1 playout system streaming to fr1 on port 8000, and another on port 8060 with 8000 being the main stream with 8060 being the 'fallbackurl' and fr2 and fr3 acting as relays.

As I was never able to get 'fallbackurl' to work, I finished up with 2 separate servers relying to separate mount points.

I'm trying to make some sense of this now as it's just a mess..

[Busby]

fr1.1mix.co.uk & fr3.1mix.co.uk servers are both on port 8060

In listenh.m3u, fr4.1mix.co.uk is listed as being on port 8000

This is the server with the streams that are "unable to access the directory".
Is the port config correct, or should it also be 8060?

The server which displays "unable to access the directory" is FR2, both 8000 and 8060 ports.
FR1 and FR3 are fine.

Thanks in advance..

[Busby]

fr1.1mix.co.uk & fr3.1mix.co.uk servers are both on port 8060

In listenh.m3u, fr4.1mix.co.uk is listed as being on port 8000

This is the server with the streams that are "unable to access the directory".
Is the port config correct, or should it also be 8060?

Many thanks for the reply - a Unix update on the server resolved the problem..