localhost does not work as broadcasting host

Bug #1091852 reported by xorik
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Expired
Medium
Unassigned

Bug Description

Hi!
I think connection to icecast2 server was broken some time ago in trunk (I use lp:mixxx).

1) I start icecast2 server on my gento (64 bit)
2) Try to connect with correct params to localhost:8000 (mp3 128, correct mountpoint, login and pass) and got this:
Debug [EngineSideChain 1]: EngineShoutcast: updating from preferences
Debug [EngineSideChain 1]: Couldn't find shoutcast metadata codec for codec: "" defaulting to ISO-8859-1.
Debug [EngineSideChain 1]: Loaded libmp3lame version 3.99.5
Debug [EngineSideChain 1]: Shoutcast failed connect. Failures: 1
Debug [EngineSideChain 1]: Shoutcast failed connect. Failures: 2
Debug [EngineSideChain 1]: Shoutcast failed connect. Failures: 3
Warning [EngineSideChain 1]: Shoutcast error: "Please check your connection to the Internet and verify that your username and password are correct."

3) If I try another soft to connect with icecast2 with same params (server, login, pass, sound encoding) (e.g. I tryed mpd), all done correct

I have icecast-2.3.3. I build mixxx with just "scons" in source dir.

Tags: broadcast
Revision history for this message
xorik (xor29a) wrote :

Ok, find way to connect to icecast server, just replace "localhost" with "127.0.0.1". I think this is not very user-friendly...
Anyway, bug report is invalid and may be closed

Revision history for this message
jus (jus) wrote :

<quote>
You can enter the host name either as an IP address or an URL.
</quote>
http://mixxx.org/manual/latest/chapters/livebroadcasting.html#icecast

It would be preferable if this would actually work.
Does Mixxx need the "http://" protocol hint to recognize a valid URL?
I agree that allowing just "localhost" would be more user-friendly.

Additionally we should add some specific examples to this part of the manual.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

The manual is wrong! You can't input the name as a URL. If you put http://localhost it will fail. However, putting "localhost" should work. I fixed the manual.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

xorik -- could you paste the result of /etc/hosts ? I think that some distros are putting 127.0.1.1 as localhost in /etc/hosts for some reason. I'm not sure why that wouldn't work with icecast2 but it's important to note that localhost sometimes does not resolve to 127.0.0.1 on some distros.

Changed in mixxx:
milestone: none → 1.11.0
importance: Undecided → Medium
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

FWIW I've seen people in #mixxx either confused about hte lack of support for URLs or having issues with 'localhost' not working.

Revision history for this message
xorik (xor29a) wrote :

My /etc/hosts (without comments):

127.0.0.1 notebook localhost.localdomain localhost
::1 notebook localhost6.localdomain6 localhost6
::1 localhost

Revision history for this message
xorik (xor29a) wrote :

$ ping localhost
PING notebook (127.0.0.1) 56(84) bytes of data.
64 bytes from notebook (127.0.0.1): icmp_seq=1 ttl=64 time=0.069 ms

RJ Skerry-Ryan (rryan)
Changed in mixxx:
milestone: 1.11.0 → 1.11.1
RJ Skerry-Ryan (rryan)
tags: added: shoutcast
summary: - Couldn't conect to icecast2 server
+ localhost does not work as broadcasting host
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I realized I could reproduce this on my macbook.

My /etc/hosts has this weird entry:

fe80::1%lo0 localhost

libshout was resolving localhost to this entry which was blocking the connection.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Xorik -- in your case it's quite likely libshout was resolving localhost to ::1 instead of 127.0.0.1. Is it possible that your icecast bind-host was 127.0.0.1? In that case libshout would have failed to connect to ::1 because icecast was not listening on that address.

Changed in mixxx:
assignee: nobody → RJ Ryan (rryan)
milestone: 1.11.1 → 1.12.0
Revision history for this message
Owen Williams (ywwg) wrote :

update?

Revision history for this message
jus (jus) wrote :

Any news?

Changed in mixxx:
status: New → Incomplete
Revision history for this message
xorik (xor29a) wrote :

Sorry guys, can't check now.
Also this bug is not so important for me now, I'll check it later.
Thank you

tags: removed: icecast icecast2
Revision history for this message
Daniel Schürmann (daschuer) wrote :

I free this up for possible GSoC students

Changed in mixxx:
assignee: RJ Ryan (rryan) → nobody
Revision history for this message
Victor Weeks (vicweeks) wrote :

I'm a potential GSoC student assigned to look into this bug.

After thorough investigation into the issue, and testing with my own broadcasting servers, I have concluded that more information about this specific case is needed.

In particular, I believe this is not so much an issue with the Mixxx implementation of server connection. For instance, whilst testing I also ran into the same error when using localhost to connect to the server. Once I verified that the icecast server was up and running, I checked the other parameters. The issue for me was using the incorrect login/password. Not sure if this is the same for the OP, but I was entering my own admin login/password, as opposed to the specific 'sources' login/password that is set in icecast.xml. Once that was cleared up I was able to broadcast without a problem.

Hope this helps.

Revision history for this message
JosepMa (josepma) wrote :

Ok, this is the result of my tests:

Windows, Mixxx 2.1 alpha, sever icecast 2 on localhost, connects and works as expected, using "localhost" as the address.
guest Linux on a virtual machine, Mixxx 2.0, server icecast on the windows host, connects and works as expected, using the IP address.

Generally, I would say there is no problem, and in fact, earlier in the post it seemed that the bug was not really a bug after all.

What could be an improvement is the handling of addresses. As said also in this post, sometimes users add the "http://" to the host name, and then that does not resolve to a valid address and it cannot connect. It would be an improvement to detect the existence of a protocol address in the text box and strip it out from the text.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Does this mean we can mark this bug as invalid and open a new one that contains your findings / improvement ideas?

Revision history for this message
xorik (xor29a) wrote :

Hi guys. I'm an author of the bug.
Unfortunately I can't test it right now. I could try to check status a bit later, maybe in a week. Since the bug is minor, you could close it.

RJ Skerry-Ryan (rryan)
Changed in mixxx:
milestone: 2.0.0 → none
tags: added: broadcas
removed: shoutcast
tags: added: broadcast
removed: broadcas
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mixxx because there has been no activity for 60 days.]

Changed in mixxx:
status: Incomplete → Expired
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6792

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.