[Pianod] telnet volume

[darren]

Thanks. I tried the web client several times the other day and couldn't get
it to work.  But, it is working now.  I don't know what I've done
differently.  Well, it's working anyway.  I'm going to disable lighttpd for
now.  It should already be stopped.  But, I'll make sure it doesn't restart.

So, where am I supposed to add "-c /usr/local/share/pianod/html"?  Is that
in the pianod.service file?  I guess not because there's already a "-c
/path/to/pianod"

On Tue, Jul 26, 2016 at 3:37 PM, Perette Barella <perette at barella.org>
wrote:

> On 2016年07月25日, at 22:44, darren <1 at crotchett.com> wrote:
>> I actually tried 4446 because I noticed that you had it in your previous
>> email.  But, it redirects me to http://10.0.0.45:4446/pianod/ and then I
>> get a 404.
>>
>>
>> Redirect then 404 means pianod’s HTTP server is up, but it can’t find the
>> client files to serve.
>>
>> Did you do a ‘sudo make install’ after building?  That installs the
>> client files into /usr/local/share/pianod/html on the pi, and the daemon
>> to /usr/local/bin.  You can change that with the -c option, if you need to,
>> such as testing it from your home directory before installation:
>>
>> $ ./src/pianod -c ~pi/pianod2-225/html
>>
> On 2016年07月26日, at 12:05, darren <1 at crotchett.com> wrote:
>
> Yes.  I did sudo make install.
>
> I looked.  The html directory is present in /usr/local/share/pianod/html
> (as are all of the files).  I'm using Firefox.  I might restart the daemon
> and see if that helps.  And, there's always the nuclear option, reboot.
> BTW, I did stop lighttpd, just in case that was interfering with the built
> in web server, but that didn't help.
>
>
> Then it sounds like the daemon configured/compiled with the wrong default
> location for the client files.  In which case, it should work if you run it
> with
> -c /usr/local/share/pianod/html
> to tell it where they actually are.  Huh… I will add compile/configuration
> settings like that to -v or -? option, to make it easier to diagnose things
> like this.
>
> As far as it displaying a client, but then failing to connect when using
> port 80 (unspecified port), it’s attempting to make the websocket
> connection to the lighttpd that you set up because that’s where the client
> can see it was served from.  However, lighttpd has no idea what to do with
> the client’s websocket request, which is how the client communicates with
> the daemon.  It may display the client, but it’s a red herring; the client
> served by a different web server will never be able to connect to the
> daemon.
>
> For testing, you can use the DeviousFish-hosted web client, which prompts
> for the host to connect to:
> http://deviousfish.com/pianod/Client2/index.html
> For server, you’d use 10.0.0.45:4446
> The hazards of the hosted client are that the version it supports may be a
> different pianod version, which could cause snags.  For users, it also
> means dealing with the server input, which is not friendly.  But it's good
> for testing.
>
> Incidentally, the mailing list archives are back up.  My hosting provides
> alleges there was nothing to do, although I observed it being broken too.
> http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/
>
>
>
> _______________________________________________
> Pianod mailing list
> Pianod at lists.deviousfish.com
> http://lists.deviousfish.com/listinfo.cgi/pianod-deviousfish.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/attachments/20160726/77e18edc/attachment-0002.htm>