On 15 July 2016 at 05:40, Mathieu Lonjaret <[email protected]> wrote: > On 14 July 2016 at 18:39, Gergely Imreh <[email protected]> wrote: >> Hi, > > Hi, > I don't know much about http/2, so please bear with me while I try and > help debugging that. > >> I'm trying out camlistore, using the tip of the master branch, and run into >> an issue with http/2, not letting me to connect to the server on the command >> line, while the browser UI connection works fine. >> >> I'm packaging up camlistore as a Docker container to run on the resin.io >> platform, basically being easily deployed to single board computer devices >> (such as Raspberry Pi, Beaglebone, Intel Edison, etc...) The repo of the >> container source is here: >> https://github.com/resin-io-playground/camlistore-server >> >> On resin, the devices can be accessed over the net through a public device >> URL. The address "https://<UUID>.resindevice.io" is proxied over VPN to the >> device, to port 80. Thus I've set listen:":80" and >> baseURL:"https://<UUID>.resindevice.io" in server-config.json. Over the web >> UI I can connect, upload, change settings, everything. >> >> When using command line tools, on the other hand, I run into this error, for >> example in the case of "camput file SOMEFILENAME": >> Error putting file: Get https://<UUID>.resindevice.io: http2: unexpected >> ALPN protocol ""; want "h2" >> >> That https proxy indeed does not have http/2 / ALPN enabled, does that mean >> the command line tools cannot connect anymore? > > I don't see why we couldn't make the CLI tools work if the web UI can, > especially since http/2 is pretty well supported on Go. So let's not > lose hope just yet. :-) > >> Looks like using the 0.8 release command line tools can work with the same >> server just fine (server compiled either from 0.8 or master branch). Also, >> using the master branch, can successfully use localhost dev server fine. >> >> Any ideas how to deal with this? > > Is there any way you can give me the address (privately, if you > prefer) of your server, so I can try and hit it and see for myself?
Cheers for the feedback! I've put online a device, reachable at https://0fb549fe00f9a9c4ba96a45f349b525c4e36498835dc0533b202606bd43d81.resindevice.io/ I can't guarantee how long it will be running, but try to keep it online until this issue is debugged. Auth is userpass:alice:secret, nothing sensitive is on it, feel free to use as you like for this task (to the extent of space it has, not too much, it's a BeagleBone Green Wifi). Let me know if it helps! It's entirely possible that the resin.io proxy is doing something not-quite-correct, but have no idea what to debug at the moment. I've tried adding a second proxy in front of this (nginx + http/2 + alpn). That way the CLI seems to work (run into other issues with Websockets, but that's for another time) Cheers, Gergely > > Cheers, > Mathieu > -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
