Connecting to 127.0.0.1:9000... failed: Connection refused.

[r00tr4t]

Hi i installed TwonkyServer on my eBox but i cant access the web interface.

wget http://127.0.0.1:9000/config
--2011-11-10 01:25:00-- http://127.0.0.1:9000/config
Connecting to 127.0.0.1:9000... failed: Connection refused.

Any suggestion on how to fix this

[phibertron]

is an ebox like an emachine desktop ?

stupid question, i know
but are you trying to get to 127.0.0.1:9000 while being on a different machine
or if the ebox is a pc, your doing it from that desktop?

what os is it running on?
what version did you install?
did you change anything?
is it running av firewall?

I know lots of questions, but need more data

[r00tr4t]

Locks like the Twonkyform server crashed and posts was deleted :/

Any way i removed 127.0.0.1 from the ip and got connection refused.
Then i added the 127 and ip to my remote computer.
local wget = ok
remote Firefox = fail.


It locks like a problem accessing the server remotely.
Is there a way to select network kard for twonky?

[phibertron]

Yeah I noitced that, ouch

Good ?, I dont know of any way to bind it to an interface, just by ip

Since, it appears the 127.0.0.1 is needed in this scenario
there is one more setting I can think of thay may or may not help

In 6.0.37 it might be set as disabled by default
we could try enableing it
so if you add this to the server ini, it might help, not sure though
as we are trying to connect via http, and not through ssdp broadcast

disablelocalssdp=0

[r00tr4t]

No it did not help :/

[phibertron]

Aight, well we half way there

There a few people in this forum who more knowlegable in ubuntu than I am

Maybe they can chime in here and offer some other things to look at
As we have basically covered the main twonky settings that would effect
what ip twonky binds to

[cykelsmeden]

is an ebox like an emachine desktop ?

stupid question, i know
but are you trying to get to 127.0.0.1:9000 while being on a different machine
or if the ebox is a pc, your doing it from that desktop?

127.0.0.1:9000 while being on a different machine
is contradictory. 127.0.0.1 simply means "This Machine"
When you want to acces from another machine, you have to use the TwonymachineIP, ie.
192.168.1.110:9000

//finn

[r00tr4t]

some posts was deleted from this tree when the twonkyform server crashed.

the wget 127.0.0.1:9000 was made on the local machine to test if I could connect to the twonky server localy.
that did not work in the beginning before phibertron told me to sett the IP in the twonky ini file.
Now i can access the twonkyserver localy but not remotely.

[r00tr4t]

Is there a way to change the default port for twonky?

[phibertron]

In the twonky server ini

# Port of the http server default 9000
httpport=

[parnott]

Have you configured your ebox machine's firewall to allow external access on port 9000?

If not then that could likely cause a Connection Refused error. Twonky would not even come into play if port 9000 is blocked at the firewall.

[r00tr4t]

interesting error i got now ....

Code: Select all

$ sudo service twonkyserver restart
PID file /var/run/mediaserver.pid not found, stopping server anyway...

Starting /usr/local/twonkymedia/twonkymedia ... Daemonizing...

$ sudo service twonkyserver restart
PID file /var/run/mediaserver.pid not found, stopping server anyway...

Starting /usr/local/twonkymedia/twonkymedia ... Daemonizing...

$ sudo service twonkyserver start
Starting /usr/local/twonkymedia/twonkymedia ... Daemonizing...

$ sudo service twonkyserver start
TwonkyMedia server seems already be running under PID 7783
(PID file /var/run/mediaserver.pid already exists). Checking for process...
Process IS running. Not started again.

[r00tr4t]

Yes i got in to the interface now

But the unhappy news is that twonky server seems very unstable when i try to access it from my media streamer..
When i go in on the server every thing locks fine for 10sec then i lose connection :/
Dos it have anything to do whit that i posted above?

[cykelsmeden]

some posts was deleted from this tree when the twonkyform server crashed.

the wget 127.0.0.1:9000 was made on the local machine to test if I could connect to the twonky server localy.
that did not work in the beginning before phibertron told me to sett the IP in the twonky ini file.
Now i can access the twonkyserver localy but not remotely.

Well, I might be misunderstanding, but I don't believe using wget as test, tell anything, as the port(9000) probably only reacts on http requests. I have my twonky on a win- IP 192.168.1.62 , and I can use http://127.0.0.1:9000/ to access the config from the twonkyserver, or I can use http://192.168.1.62:9000 from either the twonkyserver or another pc on my lan.

From my lan I can use http://192.168.1.62:9440 to access my media (port 9440 being the remote port.)
Unfortenuately Twonky still carry a bug, making this impossible through the firewall ;(

//finn

[r00tr4t]

I do not know what hell i did but everything works now
Thank you for the help every one and big thanks to phibertron..

[phibertron]

Haha, I been there too, made a bunch of changes, and things worked but not sure of which ones

I would recommend, while its still fresh in your mind,
to try and retrace things you did and maybe takes some notes
or back track one change at time, till you break it again
but just one at a time =)