Hi,
Rather embarassingly, I figured out what was causing the SqueezePlay issues
a few minutes after posting this!
Recently I've set up a VPN, so that I can connect from my work machine to
home using that. This time I'd started up SqueezePlay while the VPN was
connected, and that seems to have confused it, despite the 'public' IP
address of my server being used for the connection, not the VPN one.
Will have a look when I get home to see if it's had any bearing on the rest
of the issue.
In article <cdmackay.5sggso (AT) no-mx (DOT) forums.slimdevices.com>,
cdmackay<cdmackay.5sggso (AT) no-mx (DOT) forums.slimdevices.com> wrote:
> Doesn't help much, but just a data point to say I've always run SB
> unstable (now 7.8) on Debian unstable, and all has been working
> perfectly for years.
>
> You might want to confirm which OS/distro you're using, in case that's
> relevant (to others). I've seen issues raised before other distros...
I think I was on 7.8 before, but it hadn't updated in a long time (I
previously had 'testing' listed as a source, not unstable.
The distro is Debian Stable, but I plan to upgrade as soon as the next
stable Debian release is made.
Will report back if the Boom issue is still happening.
Any suggestions for any logging I might enable if it is still an issue?
Andy
Rather embarassingly, I figured out what was causing the SqueezePlay issues
a few minutes after posting this!
Recently I've set up a VPN, so that I can connect from my work machine to
home using that. This time I'd started up SqueezePlay while the VPN was
connected, and that seems to have confused it, despite the 'public' IP
address of my server being used for the connection, not the VPN one.
Will have a look when I get home to see if it's had any bearing on the rest
of the issue.
In article <cdmackay.5sggso (AT) no-mx (DOT) forums.slimdevices.com>,
cdmackay<cdmackay.5sggso (AT) no-mx (DOT) forums.slimdevices.com> wrote:
> Doesn't help much, but just a data point to say I've always run SB
> unstable (now 7.8) on Debian unstable, and all has been working
> perfectly for years.
>
> You might want to confirm which OS/distro you're using, in case that's
> relevant (to others). I've seen issues raised before other distros...
I think I was on 7.8 before, but it hadn't updated in a long time (I
previously had 'testing' listed as a source, not unstable.
The distro is Debian Stable, but I plan to upgrade as soon as the next
stable Debian release is made.
Will report back if the Boom issue is still happening.
Any suggestions for any logging I might enable if it is still an issue?
Andy