• Welcome to RadioDJ - Free Radio Automation Software Forum. Please log in or sign up.

Why would one instance of RDJ work with web page and not another

Started by starlite, July 02, 2014, 09:35:19 AM

starlite

I am still trying to connect get the Demo Script 2.2 to my new RDJ17 db as here ad nauseum..

http://www.radiodj.ro/community/index.php?topic=5326.0

however I have opened this new thread due to finding that my previous setup of RDJ 1657 with MySQL, Standalone some encoder and Shoutcast, does still work with Gary's Web Page. It shows playlist, most played etc perfectly.

Now why is it that the new Radio17 with new db now MariaDB and some encoder plug in, will not get any reaction in the Demo Script.

At first I thought it was the port blocked, however it cannot be as it works with the RDJ 165 setup.

Has anyone any idea at all what could be stopping the new setup not working?

Thanks..appreciate any input as it could start me on the right track.

oz


BTW

Can I have 2 RDJ working each with their own full setup as above work at the same time on the same box?

SnowHow

OK, I'll take a shot...

I skimmed through the other thread. Here's a question I didn't see asked:

Does the computer your working on have a static IP assigned to it?

Here's another:

This new instal of 1.7.0/MariaDB - is it on the same or a different computer?

If it's on a different computer, does it have it's own assigned ip on your LAN and did you change the port forwarding in the router to point to the new box?

Those are just the basic questions off the top. Answer those and maybe I can accidentally nudge you in the right direction...  :D


J-


starlite

Firstly many thanks for the help.

Yes both are on the same box and yes we do have a static IP.
They both use the same playlist from the same place.

The RDJ 165 works fine with the old setup.. MySQL, some encoder standalone, Shoutcast and Gary's Playlist web page.  All works fine as it always did.

RDJ 17 is now with MariaDB (I thought I'd change to see if it would work with Maria when it didn't with MySQL however it made no difference there), Alstacast Plugin and Icecast.

RDJ works on the box fine, Icecast webpage shows on box and also via IP on web.

At the moment I am doing housework on the box but I can't work out why one would work and the other not as they both use 3306 and all the same options.

Same  box so same box IP, nothing else touched, port forwarding or anything in router etc should not need changing should it?

Is it something I need to do within RDJ?

Thanks for the 'nudge'. At this stage I am open to anything..well   :-)

AndyDeGroo

How about PHP errors? Do you get any? Preferably set PHP error_reposting to E_ALL in script and enable display_errors temporary.

To achieve this, add following code at the beginning of page that connects to database:

<?php
error_reporting
(E_ALL);
ini_set('display_errors'1);
?>



It could be that script is using mysql_connect() function and you are getting error because of PHP5 bug with MariaDB.

starlite

HI,

I placed the code in but didn't get any reaction so guess that is not the problem.

As I said, Gary's page works so I figured this should as well.

Nothing has changed, same XP Box, same Box IP, same Web Page IP
except...

Demo 2.2 Script instead of Gary's,
RDJ 1.7 not 1657,
Icecast not Shoutcast,
some encoder PLug In, not Standalone.

I also now use MariaDB although this still didn't work when I used the same MySQL.

On re-looking at everything , I came across this in the router.

I assume the Source Port of 80 which works for Gary's Script should work for the Demo script unless something is written into it. Both scripts are on the same domain site, but different directories.

Incoming IP Filtering Setup

When the firewall is enabled on a WAN or LAN interface, all incoming IP traffic is BLOCKED. However, some IP traffic can be ACCEPTED  by setting up filters.

Choose Add or Remove to configure incoming IP filters.

Filter Name IP Version Interfaces Protocol SrcIP/ PrefixLength SrcPort DstIP/ PrefixLength DstPort Remove
RadioDj170 4         br0 , ppp0 TCP 223.130.27.185      80 192.168.1.10                3306


AndyDeGroo

Quote from: starlite on July 06, 2014, 03:31:58 PM
I placed the code in but didn't get any reaction so guess that is not the problem.

As I said, Gary's page works so I figured this should as well.
If by Gary's page you meant this, it does not work because it cannot connect to database.

Quote from: starlite on July 06, 2014, 03:31:58 PM
On re-looking at everything , I came across this in the router.

I assume the Source Port of 80 which works for Gary's Script should work for the Demo script unless something is written into it. Both scripts are on the same domain site, but different directories.

Incoming IP Filtering Setup

When the firewall is enabled on a WAN or LAN interface, all incoming IP traffic is BLOCKED. However, some IP traffic can be ACCEPTED  by setting up filters.

Choose Add or Remove to configure incoming IP filters.

Filter Name IP Version Interfaces Protocol SrcIP/ PrefixLength SrcPort DstIP/ PrefixLength DstPort Remove
RadioDj170 4         br0 , ppp0 TCP 223.130.27.185      80 192.168.1.10                3306


No, your source port 80 is wrong. MySQL client won't use source port 80 to connect to database via port 3306. Source port should be left empty in your firewall configuration because it is chosen randomly. TCP port 80 is used by HTTP server to listen for incoming requests from browsers and sending responses.

If you see text "For the moment, our server is off-line. Please come back later...", it means that the script could no connect to MySQL database.

starlite

Well at the moment I am sipping on a fresh orange juice relaxing in front of the fire not really believing my problem is virtually resolved.

AndyDeGroo, I have raised my glass and wished you well with loads of thanks.

This is the story...

I added another entry into the virtual server area of my router and as suggested, left the port blank. I decided to leave the initial entry there with port 80, as maybe it is necessary for Gary's playlist.


It still didn't show the page so I decided to place the port 80 after the server IP xxx.xxx.xxx.xxx:80 and up it bounced.!

Even the Request works !

There is a slight problem though, and that is the Now Playing list is not showing what actually is playing.

I will investigate after the orange juice :-)

So happy I have finally got it working.

starlite

With the initial db problem resolved I will create another post with current problem.