[3G Overview] How to connect SqueezePlayer via 3G
Via WiFi SqueezePlayer directly connects to your router which is connected to the Squeezebox server.
This is a rather simple setup, but still very versatile as you can walk around with your phone or tablet anywhere you are in reach of your own WiFi network.
But what about listening to your music in your car, at work, at college or school?
Well just connect via your mobile connection, but …
alas – now it looks much more complicated!
As you can see, your music needs to travel a long way now (through something call ‘THE NET’) and there are some obstacles to be cared of.
This multipart tutorial will help you to get things set up, but here is the short version.
If anything is not clear to you: follow the links to read an indepth tutorial about each needed step.
Part 1: Make SqueezePlayer find your home network
Typically you need to setup a service like DynDns.org on your router, so that it tells this service where it can be found on the internet. In SqueezePlayer you can then configure a name like ‘myserver.dyndns.org’.
You will also need to tell your Controller App (i.e. SqueezeCommander) this new address.
Part 2: Make your router forward traffic to your Squeezebox-Server
SqueezePlayer wants to talks on ports 3483 and 9000 with your server. Make your router forward these ports.
Activate Password protection in your server, otherwise anyone on the internet is able to control your Squeezeboxes
Part 4: Reduce the bandwidth to get robust streaming.
Typically DSL doesn’t have good upstream capabilities. Squeezebox-Server allows you to setup bitrate limiting, so any song will be transcoded to an appropiate mp3 stream that will make it’s way from your network through the internet to your Android device.
Part 5: Secure your communication channel
Think about setting up a virtual private network, to make your setup even more secure.
Another option is to setup a SSH tunnel (also called ‘poor mans VPN’) which we will do in the final chapter.
May 29th, 2011 at 08:35
Is it enough to have squeezeplayer for android able to connect to the home squeezebox server?
Don’t I also need to get Squeeze Commander to connect to the home squeezebox server as well?
May 29th, 2011 at 08:56
Hi Jerry,
yes you are right, in SqueezeCommander one needs to enter the DynDns-URL too (this is possible in the SqueezeCommander Settings).
As SqueezeCommander uses port 9000 as well, no additional steps are needed.
Will include this information in the main article tonight, thanks for the suggestion.
June 23rd, 2011 at 18:06
I have a static IP, and want to play music on my Motorola Xoom via mobile network. Squeeze Player connects fine, but I don’t know how to get Squeeze Commander to work. I’ve added a new server (on Squeeze Commander), pointing to my IP and port 9000. My router is directing port 3483 and 9000 to my NAS server having the Squeeze Server installed (Squeeze Commander works fine on the local network).
What am I missing?
June 23rd, 2011 at 20:36
Hi Kim,
to be honest I don’t have a clue why SqueezeCommander is not working for you.
I’m using it myself (having entered a dyndns-URL) and it connects fine.
I’d check first, if the port forwarding on port 9000 really works. Can you browse to YOURIP:9000 via the Android browser when only connected via 3G?
SqueezePlayer rarely uses port 9000 (just for syncing the volume level), so when SqueezePlayer can connect it does not prove yet, that port 9000 works as expected for SqueezeCommander.
June 24th, 2011 at 05:41
Hi Stefan. Thanks for your quick reply!
I don’t get anything via the browser on port 9000. Port 9001 (I opened poth ports for the sake of desperacy) though, shows me the Squeeze Server web interface. What am I supposed to see on port 9000?
June 24th, 2011 at 06:05
If you see the Web-interface on 9001, just configure both SqueezeCommander and SqueezePlayer to use 9001.
Though 9000 is the default port, on some NAS its used already, so the server decides to be on 9001.
June 24th, 2011 at 06:26
Cool – that was it! Quite obvious actually – I just didn’t understand exactly how the ports was used. Port 3483 still puzzles me – but don’t bother answer that here.
Thanks Stefan!
June 24th, 2011 at 16:39
9000 (or 9001) is the remote control port. This port is heavily used by SqueezeCommander and all other Apps to tell the server that it should start some song. Also the server provides the cover-art and menus here.
3484 is used by the playback devices. On this port they get instructions about starting a download, starting with playback, that they should change the volume, skip some milliseconds to get into sync again and so on.
So SqueezePlayer works fine for 99% of all features with just port 3483 forwarded. Only when you change the volume on your mobile this is told the server via port 9000, so that it knows the position of the volume slider.
July 24th, 2011 at 18:23
Hi Stefan,
When I enter my serveradress, http://*****.mycloudnas.com, It displays in squeezeplayer as “http%3A%2F%2F*****.mycloudnas.com:9000”.
So the “://” is replaced by “%3A%2F%2F”
Mycloudnas is a domain service from QNAP.
In a browser I can open SqueezeboxServer thru the internet just fine.
Any idea what causes the “://” to be replaced?
Thank you in advance.
July 24th, 2011 at 18:55
Hi Bert,
this is a protection of SqueezePlayer to avoid invalid characters in the server address.
Just remove http:// and just use ‘***.mycloudnas.com’
SqueezePlayer connects to your server on port 3483 and isn’t using http at all on that port.
Only when it downloads the music stream, http is used (and is then added automatically to the server address).
July 24th, 2011 at 19:28
Hi Stefan,
Thanx for your answer. I tried that before and it didn’t work.
But now it works miraculously !!!
Thanx again.
Bert.
October 19th, 2011 at 18:44
Stefan,
I set this up and had it working at home through a mr1clar.dyn-dns-wiki.com address that I set up on the router and with dns as described in the instructions.
Since then, I cannot connect to the server, at home or remotely. Any ideas or thoughts?
Thanks!
October 19th, 2011 at 19:26
maybe dyn-dns-wiki.com is not pointing to your server anmore?
or the port-forwardings don’t work anymore (maybe the server changed its own IP address) ?
I guess doing the step by step instructions again is the best way to find the missing link.
October 20th, 2011 at 13:41
Okay thanks, but, what would cause it not to point any longer? Anything in particular?
October 20th, 2011 at 20:47
It’s very hard to diagnose this from the distant. It might be a failure of your router to report the current IP, it might be an error with your dyndns provider maybe having skipped one message. Guess there are multiple other possible reasons.
November 22nd, 2011 at 15:08
I’m having trouble Stefan. On Squeeze Player I get Connection CDMA Invalid Server and Playback Stopped.
I don’t understand what player I’m supposed to be able to control in Squeeze Commander to listen to playback. I only see the players I had before.
As far as I can tell, port forwarding is fine. I can access port 9000 on the device’s browser.
November 22nd, 2011 at 17:48
Hi Michael,
“invalid server” usually means some error in the server url you entered. With high probability you had a spelling error in the dyndns-url, so that the IP could not be resolved.
November 22nd, 2011 at 16:05
Ok, somehow now it’s working. Not sure what I did!
December 3rd, 2011 at 22:30
Does not connect. Android browser gets “Web page not available”.
Help!?
December 3rd, 2011 at 22:41
Hi Vic,
in order to help you, you should give more information.
What server version are you using, and what did you try so far. Please be as detailed as possible – I’m pretty sure you missed some step from the tutorial, we just need to find out which one.
December 4th, 2011 at 17:16
Running SqueezeCenter v. 7.7.0 on Netgear ReadyNAS Duo.
Router is ASUS RT-N12. Ports 9000 & 3483 open to Squeeze Center IP (192.168.15.200)
Dyn-dns set up.
Have a photo web gallery set up via Dyndns (separate URL) on http (port 80) that works fine.
Tried port triggering 9000 & 3483 as well, no difference.
Thanks
December 4th, 2011 at 17:38
If you open up Port 9000 at least the web-interface should be visible via your dyndns-url.
http://myhome.dyndns.org:9000
If that does not work, something isn’t set up correctly either on your router or dyndns.
You say that you have setup a separate DynDNS-URL that works. Are you sure, your router can handle two accounts?
When you ping both Dyndns URLs
ping myhome1.dyndns.org
and
ping myhome2.dyndns.org
do they resolve to the same IP address?
December 19th, 2011 at 00:36
Got everything setup easily and plays great over WIFI. If I turn WIFI off squeeze player will connect over CDMA but when I start the Logitech APP it keeps searching for players and never finds mine. Can you tell me what I’m missing? Thanks!
December 19th, 2011 at 09:46
Hi DeWayne,
while SqueezePlayer is able to connect via CDMA, the Logitech App does not support this.
You’d need to invest into SqueezeCommander to allow remote streaming. In SqueezeCommander (like with SqueezePlayer) you will be able to manually add a server address (your dyndns address) and it then will recognize all of your players (including SqueezePlayer) and allows you to browse your library remotely.
SqueezeCommander is much superior to Logitechs offer anyway. Also without SqueezePlayer it’s worth any penny.
Hope this helps.
Cheers
Stefan
December 19th, 2011 at 23:05
Stefan,
Yes it works great with SqueezeCommander. I setup (long time ago) and use DynDns.org at work but now when I went to set it up at home that it is not free anymore. 🙁 My IP does not change often so hopefully I’ll be OK.
Thanks again,
January 4th, 2012 at 16:59
I just finished setting this up successfully using the free dnsdynamic.org service and my XS4all Fritzbox, connecting from an Android phone with SqueezePlayer to what is now called the the Logitech Media Server. I found the dynamic dns service on this list http://dnslookup.me/dynamic-dns/ that includes more free services. I simply picked the first one on the list and it works.
This totally rocks, it feels like I have my personal Spotify now 🙂
January 6th, 2012 at 18:09
Setting this up on a Galaxy Nexus. What isn’t working on the Nexus as of now? Seems to work on WiFi here.
I cannot connect to my server remote (HSPA). Should it be enough to be able to connect to it on port 9000 through Chrome or is it more to it?
January 6th, 2012 at 22:55
Hi Lobo,
the warning about the Galaxy Nexus was a precaution as I had two users reporting problems.
In the meantime it turned out to be a mix of environment problems and a small bug in the settings of SqueezePlayer that actually affects all devices (when one manually changes the server address, you have to turn playback off and on, before the changes take affect).
I removed the warning from the App description again – a version fixing the minor annoyance (that doesn’t affect many people) will be out soon anyway.
If you cannot connect to your servers website via port 9000 then your port forwardings don’t work correctly yet. This would be a first test if everything is setup right.
SqueezePlayer in addition would also need port 3483 for remote streaming.
January 7th, 2012 at 09:20
I finally wrestled this and it’s working fine now. Had to add Squeeze Commander first, though.
Now I just have to get a grip on Squeeze Commander. Complex application.
Thanks for an awesome program!
January 7th, 2012 at 22:48
Cool! Have a lot of fun with SqueezePlayer!
January 9th, 2012 at 16:29
gibt es irgendwo eine deutsche 3G A-Z für Deppen Installationsanweisung!
von a) wie geb ich einen port frei bei der fritz.box? allein da gibt es ja hunderte Einstellmöglichkeiten.
Portfreigabe aktiv für ?
an Computer ?
an IP ja welche den?
und dann?
January 9th, 2012 at 23:59
Eine deutsche Anleitung mit den Basics gibt es für ‘ne iPhone App hier: http://penguinlovesmusic.de/2011/02/11/coolios-guide-to-remote-playback/?lang=de
Ne exakte Anleitung wie man die Port-Freigabe auf der Fritz-Box einstellt, ist da aber auch nicht enthalten.
Grundsätzlich muss die Portfreigabe für den Computer sein, wo der Squeezebox-Server drauf läuft.
Bei meiner Fritzbox gibt es das Menü “Internet->Freigaben”. Dort eine Freigabe für “andere Anwendungen” erstellen.
Von Port 9000 auf Port 9000 an den Computer wo der Squeezebox-Server läuft, IP-Adresse sollte automatisch ausgefüllt werden.
Dann das ganze nochmal für die 3483.
January 10th, 2012 at 10:05
UMTS connected! aber leider kein Ton über Squeeze Comander (nur bei Radio)! Was könnte die ursache sein?
January 11th, 2012 at 19:12
Hi Jörg,
sorry für die späte Antwort auf deine ursprünglichen Fragen. Ich vermute mal, du hast im SqueezeCommander nicht den SqueezePlayer als aktiven Player ausgewählt?
Grüße
Stefan
January 10th, 2012 at 10:21
Er zeigt zwar Alben usw. an, drück man auf play passiert leider nichts. Hängt das mit dem galaxy nexus zusammen?
January 11th, 2012 at 10:22
Hurra 3G funzt! Habs am laufen auf Galaxy Nexus, Nexus S, Galaxy Note u. htc Flyer!
Nur dumm das der Rechner online sein muss.
January 11th, 2012 at 19:11
Folgende Alternativen gibt es zum Squeezebox-Server auf dem Rechner (von billig zu teurer).
1) SheevaPlug (http://www.globalscaletechnologies.com/p-22-sheevaplug-dev-kit-us.aspx, 75€) + USB-Festplatte: ein bißchen Bastelspaß ist garantiert.
Aber es gibt umfangreiche Anleitungen, wie man das kleine Ding mit Squeezeboxen zu Laufen bringt: http://www.squeezeplug.eu/wiki/index.php/Main_Page
Vorteil: wenig Stromaufnahme – kompletter Squeezebox-Server. Wenn die USB-Festplatte runterfährt auch kein Ton zu hören, wenn man keine Musik hört, weil nirgends ein Lüfter.
2) Touch + USB-Festplatte. Ohne basteln und ähnliche wie #1. Leider nur eine kleine Version des Squeezebox-Server, weil CPU + RAM nur halb so viel sind wie unter #1
3) NAS kaufen (Synology, QNAP oder ReadyNAS) – alle haben Pakete auch für ‘nen Squeezebox-Server.
April 20th, 2012 at 01:48
Stefan,
I have squeezeplayer and squeezecommander. On wifi it works great-no problems.
I have setup an address via dlinkddns and have assigned my port forwarding(hopefully I did it right). I have a dir-655 router
2 android devices: Squeezeplayer connects on 3g. I can control my stand-alone squeeze player. I can direct-connect to my logitech media server using xxx.dlinkddns.com:9000. I cannot connect using my 192.168.ip.
Squeezeplayer just sits there saying trying to connect. Can you point me in the right direction? Thanks
April 20th, 2012 at 01:55
Sorry Stefan
My last comment should have said squeeze commander trying to connect. Squeeze player is connected. Sorry for the confusion.
April 20th, 2012 at 22:13
Hi Johnny,
if you can surf to xxx.dlinkddns.com:9000 via the browser of your mobile and SqueezeCommander is still not able to connect, my best guess is, that you have a typo in the configuration of servers in SqueezeCommander.
It should definitely work when you are able to browse to the servers werbinterface, this is a good proof, that you’ve setup your router correctly.
Kind Regards
Stefan
April 22nd, 2012 at 04:44
Very helpful Stefan-I was putting in the IP instead of the browser name. Once I added the browser name it started working immediately. Thank you so much for your help.
Johnny
May 16th, 2012 at 11:01
Stefan-should I be able to connect across 3G or 4G networks? I can connect fine while in NC(Charlotte area) but while traveling in NYC I could not connect. Wondering if I have something entered incorrectly.
Thanks so much,
Johnny
May 16th, 2012 at 20:03
Johnny,
you should be able to connect through all networks, provided they allow traffic on the corresponding ports of SqueezePlayer/Squeezeboxes.
Cheers
Stefan
May 16th, 2012 at 22:52
ok thanks Stefan. Doesn’t sound like anything I need to check from my end. Thanks for the prompt response.
August 24th, 2012 at 18:12
My Problem is the following:
Although i’m able to surf to my squeeze-server on my Qnap-device with the browser on my mobile (xxxx.myqnapnas.com:9001), it is not possible to use the mobile as player when it is not connected the the WiFi. (works fine if connected to WiFi)
In SqueezePlayer App settings i typed the serveradress manually, the portnumber and login/password. Statusinformation given by your app is: Connection: HSPA connected.
When I turn of WiFi, the app prompts me to turn it on otherwise i wouldn’t be able to do some special setup on my router…
The router is configured to forward the requested ports 9001 and 3483.
Whats did i do wrong?
Thanks for help.
Mobile is LG-P990, Router is an Alice IAD. Squeezeserver is Version: 7.6.1 – r33110 (installed aa QPKG-Package on a QNAP TS-119PII)
August 24th, 2012 at 21:57
Hi Matthias,
when SqueezePlayer says “HSPA connected” everything is fine. You should be able to remote control is (if you use SqueezeCommander or OrangeSqueeze … with the Logitech App its not possible to connect remotely).
You can disable the WiFi warning screen in the settings of SqueezePlayer. I just added it, so that new users don’t expect SqueezePlayer to work, when thay are connected via 3G.
August 25th, 2012 at 00:40
hi Stefan! Many thanks for your answer.
Despite the SqueezePlayer tells it is connected, when i push the button to start the Squeezebox mobile-app the app isen’t able to identify any player anymore. it only identifies the player like my LG P990 or lokal Squeezebox when wifi is turned on.
Maybe that the settings of the port ir dns-server are wrong?
i have no idea …
August 25th, 2012 at 01:02
okay i didn’t noticed that the logitech app won’t work. i just tried to access the squeezeserver on my nas via the browser. there i was able to chose my mobile-phone as player in the drop-down menu. so squeezeplayer has registered my mobile to the server correctly 🙂 playback started and i’m glad now. if only the logitech mobile app won’t work i can live with that. Will try SqueezeCommander and OrangeSqueeze. Many thanks for your help. good night
August 25th, 2012 at 20:44
Hi Matthias,
personally I prefer OrangeSqueeze. It remote controls SqueezePlayer so you can configure two servers (your local + remote one) and SqueezePlayer will connect automatically to the selected one without you ever in need to start SqueezePlayer.
September 7th, 2012 at 15:28
Hi Stefan
Thanks for your great product and the tutorials here! I have been using the software for some months now. I try to use over wifi whenever I can. There are times, however, that this is not possible. Occasionaly when I try to connect over 3G SqeezePlayer says that it is connected. SqueezeCommander and OrangeSqueeze both try to connect but then don’t make it. On other occasions is works fine. Do you have any suggestions as to what could be the problem?
October 19th, 2012 at 21:40
Hi Shozzer,
sorry for the very late answer – for some reason this post was treated as spam by the blog software 🙁
I’m afraid I don’t have a good answer to your question. But when neither OrangeSqueeze and SqueezeCommander are able to connect properly, I guess, that at this moment the internet connection is to slow. As SqueezePlayer is talking on port 3483 with a different protocol and bandwidth it might have a chance to connect, put the other Apps are trying to use port 9000 for their remote control.
October 19th, 2012 at 13:21
Hi,
I was able to connect to my LMS from outside my network via a mobile connection. Squeezeplayer doesn’t register my smartphone as a player. I connot find the reason. Is it possible that because I haven’t enabled transcoding it doesn’t register?
Cheers wgk
October 19th, 2012 at 21:38
Hi wgk,
when SqueezePlayer doesn’t register remotely, this is typically because forwarding port 3483 is not setup correctly.
October 22nd, 2012 at 21:09
Thanx stefan, one should open ones eyes and allways double ckeck settings 😉 It was exactly as you mentioned.
May 1st, 2013 at 20:45
Apologies for the question, im running squeezeplayer on a galaxy s3 when i switch to squeeze commander over 3g no connection can be made. When i switch back to squeezeplayer i see it has disconnected and it reconnects itself to my server. Something is causing the connection to drop when squeezeplayer does not have screen focus. Any help would be greatly appreciated.
May 1st, 2013 at 21:14
Hi Matt,
hhmm – this is really strange. I wouldn’t know why the connection would drop, when you move over to SqueezeCommander.
How do you try to connect via VPN? OpenVPN or SSL-tunnel?
I heard from users, that tried via OpenVPN but then the Apps are fighting over the port they are connecting with (looks like via OpenVPN no two apps can connect via the same port). I’m not that good in networking/VPN stuff to really be helpful with troubleshooting in the case it doesn’t work I’m afraid.
January 7th, 2014 at 20:48
Hi Stefan,
Used this for someting like a year now. Works great!
But now playback stopped working via SSL. Is this app compatible with version Logitech Media Server 7.7.2-007 ???
January 7th, 2014 at 22:18
Hi Jacqueline,
now problem known in SqueezePlayer. As you are saying you are using SSL I’d rather check the connection and router settings.
Kind Regards
Stefan
February 24th, 2014 at 20:59
Hi,
Very strange…
My config : static IP + router with directing port 3483 and 9000 to my Squeezebox server (on windows 7 pro).
I do all the configuration, and in the web access, it’s possible to see the squeezebox server… In the web access server, I see my phone and I can run a playback from the browser to my phone… BUT, from the phone I can’t see all the “player” and I can’t see the list my music.
Have you an idea ?
THX
February 24th, 2014 at 21:54
what controller App are you using?
The free Logitech App cannot connect to a remote server, you’ll need to use either OrangeSqueeze or SqueezeCommander.
Cheers
Stefan
March 1st, 2014 at 11:59
Thanks Stefan !
And now… All my soundtrack are in applelossless standard. I wan’t to keep this quality of sound for all the home player, but for the player over the web, is it possible to reduce the bandwidth to get robust streaming only in this case ?
Have a good day !
March 2nd, 2014 at 22:16
Hi,
you can reduce the bandwidth for a single player, see instructions here:
http://www.squeezeplayer.com/2011/05/3g-part-4-reduce-the-bandwidth-to-get-robust-streaming/
If the same player is used remote and at home then right now there is no automatic switching of the bandwidth limitung.
March 6th, 2014 at 11:27
Hallo,
warum öffnet sich bei jedem Telefonat der Squeezplayer und stellt sich mit Symbol eingeschaltet in die Benachrichtigungsleiste?
Hab ich da was in den Einstellungen übersehen?
LG
Steve
March 6th, 2014 at 22:35
Hi Steve,
das ist ein Bug in OrangeSqueeze, welches SqueezePlayer automatisch starten kann.
SqueezePlayer selbst wertet Telefongespräche nicht aus.
Grüße
Stefan