I'd also be interested in accessing Plinth from a non-localhost address.<br>With your fix below, I can indeed access it remotely from a browser.<br><br>But as others have noted before, the links in the UI still don't work:<br>
<a href="http://lists.alioth.debian.org/pipermail/freedombox-discuss/2012-April/003688.html">http://lists.alioth.debian.org/pipermail/freedombox-discuss/2012-April/003688.html</a><br>
<br>For example, my Dreamplug is on <a href="http://172.16.0.199:8000/" target="_blank">http://172.16.0.199:8000/</a>, and I can access that just fine.<br>
<br>The links in the UI look like this:<br><a href="http://172.16.0.199:8000/privacy" target="_blank">http://172.16.0.199:8000/privacy</a><br><a href="http://172.16.0.199:8000/sharing" target="_blank">http://172.16.0.199:8000/sharing</a><br>
<a href="http://172.16.0.199:8000/apps" target="_blank">http://172.16.0.199:8000/apps</a><br>
<br>But once I click on them, I get redirected to 127.0.0.1 and never get to the actual page.<br><br>Any idea?<br><br>There seem to be lots of hardcoded references to 127.0.0.1 in the Plinth code, not quite sure where to start..<br>
<br>Markus<br><br><div class="gmail_quote">On Sat, Sep 22, 2012 at 5:07 AM, Nick M. Daly <span dir="ltr"><<a href="mailto:nick.m.daly@gmail.com" target="_blank">nick.m.daly@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>"<a href="mailto:tornow@riseup.net" target="_blank">tornow@riseup.net</a>" <<a href="mailto:tornow@riseup.net" target="_blank">tornow@riseup.net</a>> writes:<br>
<br>
> On Sun, 16 Sep 2012 12:00:23 +0000<br>
</div><div>>> Re: freedombox.img with qemu<br>
><br>
> After a couple of days, and help from another user, the best i could<br>
> find is using chroot and qemu-arm-static, after "unpacking" the img with<br>
</div>> parted and dd...<br>
<div>><br>
> I am not sure if that is of any use, because i couldn't find a way to<br>
> make the chroot act as if it was an external device yet<br>
> (i would like to test freedombox-privxoy and plinth in the local<br>
> browser).<br>
<br>
</div>It might be easier to just change Plinth to answer to public requests so<br>
you can use the more recent VirtualBox image. The following (UNTESTED)<br>
code might fix that. I'll see if I can't fix this properly for both<br>
privoxy and Plinth this weekend. I can't guarantee I'll have the time,<br>
though. Anybody else want to take a crack at it?<br>
<br>
Apply this to Plinth by running ``patch -p1 < public-plinth.diff``,<br>
after you save the below as "public-plinth.diff".<br>
<br>
/--<br>
|<br>
| diff --git a/plinth.py b/plinth.py<br>
| index adab110..fce2700 100755<br>
| --- a/plinth.py<br>
| +++ b/plinth.py<br>
| @@ -116,12 +116,12 @@ def setup():<br>
|<br>
| # Add an extra server<br>
| server = _cpserver.Server()<br>
| - server.socket_host = '127.0.0.1'<br>
| + server.socket_host = '0.0.0.0'<br>
| server.socket_port = 52854<br>
| server.subscribe()<br>
|<br>
| # Configure default server<br>
| - cherrypy.config.update({'server.socket_host': '127.0.0.1',<br>
| + cherrypy.config.update({'server.socket_host': server.socket_host,<br>
| 'server.socket_port': cfg.port,<br>
| 'server.thread_pool':10,<br>
| 'tools.staticdir.root': cfg.file_root,<br>
|<br>
\--<br>
<br>_______________________________________________<br>
Freedombox-discuss mailing list<br>
<a href="mailto:Freedombox-discuss@lists.alioth.debian.org" target="_blank">Freedombox-discuss@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss</a><br></blockquote></div><br><br clear="all">
<br><br>