Error message when clicking on an artist in the search results

408 is the error
one of your tables in the database is damaged, or have you done any modification?

I ran a repair on the database and it didn;t find any errors. This is a fresh install of SAM and WordPress.
Anyone else have an idea of what might be going on ?

Also, I am running php 5.4
https://www.roundrockradio.com/newsite/phpinfo.php

Okay. That’s not coming from the database, that’s actually coming from SAM. The XML functions parse the data returned by SAM Broadcaster, not the database. Out of curiosity, which version of SAM Broadcaster are you running?

Hi there,
When I go to Help >> About
It shows version 2013.6

Okay. A few different possibilities here. One is that there is something else on the port that SAM uses. By default, this will be port 1221. This can easily be changed in both SAM Broadcaster and the plug-in, if needed.

Quick and (relatively) easy way to test this is to manually send the request to SAM and see what comes back. You will need to find a valid song id first. Easiest way to do this is to pull up your songlist page on the site, hover over one of the songs, and the link will have the song id in it. Should look something like: (Website)/requests/top-requests/?songid=347&startat=55&number=25. In this case, 347 is what we are looking for in that URL.

Once you have the id, you will open a browser tab or window and type in a URL to send a request directly to SAM. Using the IP address of your SAM Broadcaster client instead of 1.2.3.4, tyep in

https://1.2.3.4:1221/req/?SongID=347&Host=0.0.0.0

The data that gets returned should look something like:

<REQUEST>
  <application>
    <apptype>SAM Broadcaster</apptype>
    <version>3.4.3</version>
  </application>
  <status>
    <code>200</code>
    <message>Request OK</message>
    <requestID>30086</requestID>
  </status>
  <song>
    <artist>Led Zeppelin</artist>
    <title>Whole Lotta Love</title>
    <album>Led Zeppelin</album>
    <duration>334</duration>
  </song>
</REQUEST>

If you get a blank page, try to view the page source and it should look like the above. If you get anything else, we are closer to identifying the problem. ??

For your own safety, please don’t post anything that has your actual connection details. As long as you know what they are, there shouldn’t be any need to share them.

Okay, so I changed the port # from 1221 to 1223. I changed it in SAM, and my routers firewall.

I then ran
https://99.116.232.95:1223/req/?SongID=2020&Host=99.116.232.95

and got the following result:

<REQUEST>
<application>
<apptype>SAM Broadcaster PRO</apptype>
<version>2013.6</version>
</application>
<status>
<code>700</code>
<message>Invalid request</message>
<requestID>-1</requestID>
</status>
<song>
<duration>0</duration>
</song>
</REQUEST>

Okay. That data is at least coming from SAM. If you have changed the port number, go into your settings in the plug-in and change it there and see if that helps things.

I have confirmed that your SAM host is reachable. I was, of course, unable to manually submit a request since my IP address is not in your list of authorized IP addresses.

Yeah I changed the port in the plugin already before I submitted that last post, sorry about that.
If you wanna give me your IP to test it out I’ll add you to SAM.

I’m curious now if this may be something between the plug-in and SAM 2013. I am still using SAM 3 myself. If that’s the case, I may need to do some revisions for version detection. Do me a favor, if you go to my website, you can find me on Facebook. Send me a message there. I may get you to send me a file. It’s nothing that would violate any copyrights, but it would let me see if SAM 2013 needs to be handled differently.

Out of curiosity, if there’s anyone who is using this plug-in with SAM 2013 already, could you confirm whether you are seeing the same problem?

I can’t find you on Facebook, and going to your website didn’t help.
Can you link me to your Facebook page?

It’s just https://www.facebook.com/netguysteve ??

Oh, that’s too easy….okay, message sent..

And the puzzle continues. Using a demo version of SAM 2013, I had a look at the PHP code they distribute. They’ve restructured it a bit, fixed some vulnerabilities in their original code (which had already been fixed in the plugin) and cleaned things up, but there’s nothing that should break compatibility. The handling for the sending of the request and the parsing of the returned data is identical to the SAM 3.x code.

Adding to the perplexing nature of this is that you were already using a web-based request system, so provided you are using the same connection details in the plug-in, there shouldn’t be any issues there either.

Well I updated to the last version of the plugin today and the previous error message is gone.
Now when I click on an artist just like before I get this message.
Unable to connect to :. Station might be offline.
The error returned was ().

You can see this error at
https://roundrockradio.com/newsite/requests/?songid=2527&startat=0&number=10&songsearchtext=slayer

I checked and port 1223 is open.
My station is indeed online contrary to what the error message says.
Any suggestions are appreciated.