Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 12
  1. #1
    Junior Member
    Join Date
    Aug 2008
    Posts
    5

    "Couldn't resolve IP address for: www.mysqueezebox.com" on plugins page

    I am experiencing what appears to be a DNS issue with this software. I have already searched the forums and none of the sultions I have found work.

    I go to the Plugins page. At the top I see:

    Bad repository http://www.mysqueezebox.com/public/plugins/logitech.xml - Couldn't resolve IP address for: www.mysqueezebox.com

    Bad repository http://www.mysqueezebox.com/public/plugins/other.xml - Couldn't resolve IP address for: www.mysqueezebox.com

    Bad repository http://triodeplugins.googlecode.com/svn/trunk/repo.xml - Couldn't resolve IP address for: triodeplugins.googlecode.com

    Bad repository http://www.mysqueezebox.com/public/p...repository.xml - Couldn't resolve IP address for: www.mysqueezebox.com

    DNS works fine on the server. If I click the links in the error I see the XML of the repo. I can log in to MySqueezebox.com with a browser.

    I have re started the service several times.
    I have re started the server several times.
    I have tried various IP configs (DHCP/Static/Open DNS/My ISP's DNS etc) and NOTHING appears to change this behaviour.

    Server is running Linux Mint. I recently re-built, and this was running fine before. Since the re-build, I get this error.

    Does anyone have any ideas what might be wrong?

  2. #2
    Quote Originally Posted by RichKS View Post
    I am experiencing what appears to be a DNS issue with this software. I have already searched the forums and none of the sultions I have found work.

    DNS works fine on the server. If I click the links in the error I see the XML of the repo. I can log in to MySqueezebox.com with a browser.

    I have re started the service several times.
    I have re started the server several times.
    I have tried various IP configs (DHCP/Static/Open DNS/My ISP's DNS etc) and NOTHING appears to change this behaviour.

    Server is running Linux Mint. I recently re-built, and this was running fine before. Since the re-build, I get this error.

    Does anyone have any ideas what might be wrong?
    Hello - my first posting/reply so hopefully I've done it correctly

    It's a minor problem with Linux Mint. I had the same issue with a new install of Mint 13.

    I can't post a link as this is my first post. Google sudo dpkg-reconfigure resolvconf and it's near the top on the Mint Forums

    In summary run sudo dpkg-reconfigure resolvconf in a terminal and reboot should solve the problem

  3. #3
    Thanks a lot, had the same problem and this solved it.
    Here is the link to the Mint forum:
    http://forums.linuxmint.com/viewtopi...03835&p=590881

  4. #4
    Senior Member
    Join Date
    Apr 2006
    Posts
    246

    thanks!

    Quote Originally Posted by Veggen View Post
    Thanks a lot, had the same problem and this solved it.
    Here is the link to the Mint forum:
    http://forums.linuxmint.com/viewtopi...03835&p=590881
    Veggen,

    I had this problem for probably a year. I was ready to ditch my 4 or 5 squeezeboxes. Finally, I found your link to the Mint forums. That fixed it! I am forever grateful. I'm posting the essence of http://forums.linuxmint.com/viewtopi...03835&p=590881 here just in case that post/site ever goes down.


    Code:
    I did an sudo dpkg-reconfigure resolvconf
    I think the idea is to create a /etc/resolv.conf file. Not sure why. But this started a console process. When asked if I wanted to merge the existing contents into the new file, I said no. Not sure if that was the right answer, so far I've had no ill-effects.

    Here's my environment:
    Code:
    Logitech Media Server Version: 7.7.2 - r33893 @ Wed Mar 14 05:46:46 PDT 2012
    Hostname: tv-server
    IP: 127.0.0.1
    HTTP Port: 9000
    OS: Debian - EN - utf8
    Platform: i686-linux
    Perl Version: 5.14.2 - i686-linux-gnu-thread-multi-64int
    Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
    Total Players Recognized: 4
    Restarting logitech media server after boot -- as most people recommend -- had no effect. Moreoever, logitech media server was the only process complaining about DNS problems.

    Thanks!

  5. #5
    Senior Member
    Join Date
    Jan 2008
    Location
    Denmark
    Posts
    215
    I have installed a new server and I got the same problem when trying to listen to Podcasts/Internet radio. I started to compare the 2 servers (Mac Mini's).
    Using mysqueezebox.com I have installed the podcast app (visible on my Squeezebox Radio) but on the new server in LMS there also was a plugin called Podcasts that was listed under active Plugins - this plugin had been disable on the old server.
    As soon as I disabled the Podcast plugin in LMS the problem was solved !!
    Synology DS-409+
    TViX HD M-4000PA / Samsung SpinPoint T133 HD400LD 400 GB
    Sony HX750 HDD recorder

  6. #6
    Senior Member
    Join Date
    Jan 2008
    Location
    Denmark
    Posts
    215
    I just got this issue again (I think after a restart of my Mac mini).
    This time I solved it by enabling the "podcast" plugin from the under Inactive Plugins on LMS !
    Synology DS-409+
    TViX HD M-4000PA / Samsung SpinPoint T133 HD400LD 400 GB
    Sony HX750 HDD recorder

  7. #7
    Junior Member
    Join Date
    Apr 2013
    Posts
    10
    I have the same problem on ubuntu 12.10 32bit.
    The "http://triodeplugins.googlecode.com/svn/trunk/repo.xml" shows up perfect in the browser, but not through LMS 7.7.2.

    Any suggestions how to fix it?
    I did an "sudo dpkg-reconfigure resolvconf", but it dit not fix it

  8. #8
    Senior Member
    Join Date
    Apr 2006
    Posts
    246
    Quote Originally Posted by eMTeaM10 View Post
    I have the same problem on ubuntu 12.10 32bit.
    The "http://triodeplugins.googlecode.com/svn/trunk/repo.xml" shows up perfect in the browser, but not through LMS 7.7.2.

    Any suggestions how to fix it?
    I did an "sudo dpkg-reconfigure resolvconf", but it dit not fix it
    Do you have a /etc/resolv.conf file?

  9. #9
    Junior Member
    Join Date
    Apr 2013
    Posts
    10
    Quote Originally Posted by grimholtz View Post
    Do you have a /etc/resolv.conf file?
    Yes, but I don't know if it was created now, or if it was there from the beginning, anyway, it looks like this:
    (the /etc/resolv.conf is just a link to /run/resolvconf/resolv.conf)
    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 127.0.1.1
    search eMTeaLAN
    Last edited by eMTeaM10; 2013-04-08 at 09:05.

  10. #10
    Senior Member
    Join Date
    Apr 2006
    Posts
    246
    Quote Originally Posted by eMTeaM10 View Post
    Yes, but I don't know if it was created now, or if it was there from the beginning, anyway, it looks like this:
    (the /etc/resolv.conf is just a link to /run/resolvconf/resolv.conf)
    Check the last modified and created timestamps. Mine looks like this:

    Code:
    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 127.0.0.1
    I would try
    Code:
    sudo dpkg-reconfigure resolvconf
    again and again, trying with each option (there aren't many as I recall). Reboot after each and see if it works.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •