httpQ Problems

General discussion about netjukebox
Post Reply
BigBossMan
User
Posts: 33
Joined: Wed Mar 30, 2005 9:27 am
Location: SLC, Utah, USA

httpQ Problems

Post by BigBossMan »

Hey guys - It's been a while...

I have recently rebuilt my server using RHFC5, MySQL 5.0.18, PHP 5.1.2 and apache 2.2.0. I have the latest NJB as well.

Got everything up and running - new features are cool.

I seem to be have big issue connecting to the httpQ and Winamp, locally.

I have made sure no firewall issues exist on either the server or the client. No matter how many different ways I configure httpQ, I can't seem to get it to connect. Is there some debuging or something I could turn on to troubleshoot this further?

Stuck and I don't know which way to turn...

Thanks in advance...

BBM
User avatar
wbartels
netjukebox developer
Posts: 872
Joined: Thu Nov 04, 2004 3:12 pm
Location: Netherlands
Contact:

Post by wbartels »

Have you checked the button Start service automatically in Winamp httpQ plugin?

If the httpQ plugin is correctly installed you must get a list with filenames when using this line from a web browser.
Of course change the client-local-ip-adress section with the client ip adress ;-)

Code: Select all

http://client-local-ip-adress:4800/getplaylistfile?p=pass&delim=<br>
<update>To be sure the server can communicate with the client httpQ plugin.
Test the above line from a server web browser.</update>
BigBossMan
User
Posts: 33
Joined: Wed Mar 30, 2005 9:27 am
Location: SLC, Utah, USA

Post by BigBossMan »

Yeah, I have search everywhere for what might be broken.

I have started the service, checked the auto start, tried configuring the httpQ plugin for both the local client IP address and 0.0.0.0.

I have tried using host names, IP addresses (of both server and client), UNC shares, mapped network drives, changing the password on both the profile and the plug in...I am out of options.

I thought maybe there was some PHP login info somewhere or error echos I could turn on, anything that my help my track down what is broken.

The odd thing is, I have been using NJB for a year or more, ever since 3.67. I had some real rough spots getting this to work in a LAMP environment, but the easiest part about the whole thing was the httpQ plugin. After a year and a new server, now it is the hard part ?

Maybe I need to work on this before work and not after... when my brain is still intact.

You code snippet, this will allow me to echo out php ? (Sorry, Not a PHP wizard) :oops:

Any other Ideas ?

Thanks - BBM
User avatar
wbartels
netjukebox developer
Posts: 872
Joined: Thu Nov 04, 2004 3:12 pm
Location: Netherlands
Contact:

Post by wbartels »

BigBossMan wrote:You code snippet, this will allow me to echo out php ? (Sorry, Not a PHP wizard) :oops:
You can cut and past it in your web browser Adress bar.
For example if your client ip is 192.168.1.11

Code: Select all

http://192.168.1.11:4800/getplaylistfile?p=pass&delim=<br>
Then you must get a litst with filenames that are in the Winamp playlist.

The best way to test is:
- Start Winamp with httpQ on a client computer.
- Add some file to the playlist (may be local files).
- Start a web browser on the Server and do the above test with a client ip adress.
User avatar
wbartels
netjukebox developer
Posts: 872
Joined: Thu Nov 04, 2004 3:12 pm
Location: Netherlands
Contact:

Post by wbartels »

The default Fedora 5 firewall seems to be tighter.

(cut and past from: http://www.fedoraforum.org/forum/archiv ... 89622.html)
Remember the default firewall configuration blocks out anything that doesnt explicitly have a configuration done by the user during or post installation to allow the service to listen to a port.
(cut and past from: http://www.fedoraforum.org/forum/archiv ... 04192.html)
did you open the firewall (outbound / inbound) on your fedora box for:
135 - 137 -138 UDP
139 - 445 TCP
?
NDV
Good luck,

Willem
BigBossMan
User
Posts: 33
Joined: Wed Mar 30, 2005 9:27 am
Location: SLC, Utah, USA

Post by BigBossMan »

:D ** Found IT !! **

Not only is the firewall tighter in FC5, So is the policies in SELinux.

I have never had to tangle with it before, but here is some basic info:

http://www.nsa.gov/selinux/

http://fedora.redhat.com/docs/selinux-f ... #id2925009

One of the policies turned OFF by default is the following:

Allow HTTPD scripts and modules to connect to the network.

I turned this on to allow it and it fired right up.

The only service I have open are FTP, SSH, Samba, Https, Http, Webmin (TCP:10000). I monkeyed around for hours runnign ethereal against the server and client. I saw tons of port traffic on all kinds of different ports, but no matter what I opened up nothing seemed to work.

So for future firewall problems, don't forget to check extended policies on default ports like 80.

I feel kinda of dumb :oops:
User avatar
wbartels
netjukebox developer
Posts: 872
Joined: Thu Nov 04, 2004 3:12 pm
Location: Netherlands
Contact:

Post by wbartels »

Thanks BigBossMan for posting you solution.
This post will definitely help other users with the same problem.

Willem
Post Reply