This has been happening for a few weeks, now, after several years of (almost) flawless service.
The Squeezebox Boom tells me that it cannot connect to mysqueezebox.com.
I've done everything I can think of, for example turning off my wireless router / DSL modem, turning off the Boom, turning the router back on and then the Boom. Turning off all other devices while this is happening. Sometimes, rebooting the router and the Boom work. But for the past eighteen hours or so, none of that fixes the problem.
I can ping mysqueezebox.com and get a response, but I can't do a tracepath to it (maybe it is amazon's cloud that prevents that).
$ nslookup -sil mysqueezebox.com
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: mysqueezebox.com
Address: 46.137.90.12
Name: mysqueezebox.com
Address: 79.125.18.68
Name: mysqueezebox.com
Address: 79.125.18.91
Name: mysqueezebox.com
Address: 79.125.111.32
Name: mysqueezebox.com
Address: 176.34.103.98
Name: mysqueezebox.com
Address: 176.34.103.114
$ tracepath mysqueezebox.com
1: saturn.home 0.101ms pmtu 1500
1: livebox.home 20.044ms
1: livebox.home 19.232ms
2: no reply
3: no reply
4: no reply
5: no reply
^C
$ ping mysqueezebox.com
PING mysqueezebox.com (46.137.90.12) 56(84) bytes of data.
64 bytes from ec2-46-137-90-12.eu-west-1.compute.amazonaws.com (46.137.90.12): icmp_req=1 ttl=79 time=46.4 ms
64 bytes from ec2-46-137-90-12.eu-west-1.compute.amazonaws.com (46.137.90.12): icmp_req=2 ttl=79 time=45.3 ms
64 bytes from ec2-46-137-90-12.eu-west-1.compute.amazonaws.com (46.137.90.12): icmp_req=3 ttl=79 time=45.6 ms
^C
--- mysqueezebox.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 45.367/45.818/46.445/0.519 ms
Any idea what I can do next, to try to fix this?
The Squeezebox Boom tells me that it cannot connect to mysqueezebox.com.
I've done everything I can think of, for example turning off my wireless router / DSL modem, turning off the Boom, turning the router back on and then the Boom. Turning off all other devices while this is happening. Sometimes, rebooting the router and the Boom work. But for the past eighteen hours or so, none of that fixes the problem.
I can ping mysqueezebox.com and get a response, but I can't do a tracepath to it (maybe it is amazon's cloud that prevents that).
$ nslookup -sil mysqueezebox.com
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: mysqueezebox.com
Address: 46.137.90.12
Name: mysqueezebox.com
Address: 79.125.18.68
Name: mysqueezebox.com
Address: 79.125.18.91
Name: mysqueezebox.com
Address: 79.125.111.32
Name: mysqueezebox.com
Address: 176.34.103.98
Name: mysqueezebox.com
Address: 176.34.103.114
$ tracepath mysqueezebox.com
1: saturn.home 0.101ms pmtu 1500
1: livebox.home 20.044ms
1: livebox.home 19.232ms
2: no reply
3: no reply
4: no reply
5: no reply
^C
$ ping mysqueezebox.com
PING mysqueezebox.com (46.137.90.12) 56(84) bytes of data.
64 bytes from ec2-46-137-90-12.eu-west-1.compute.amazonaws.com (46.137.90.12): icmp_req=1 ttl=79 time=46.4 ms
64 bytes from ec2-46-137-90-12.eu-west-1.compute.amazonaws.com (46.137.90.12): icmp_req=2 ttl=79 time=45.3 ms
64 bytes from ec2-46-137-90-12.eu-west-1.compute.amazonaws.com (46.137.90.12): icmp_req=3 ttl=79 time=45.6 ms
^C
--- mysqueezebox.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 45.367/45.818/46.445/0.519 ms
Any idea what I can do next, to try to fix this?