>Have you tried not listing localhost in each of the http_*_address variables?
Yes, as well as many permutations of commenting and uncommenting each of the four lines. I still got 404s. >What resource is attempted to be accessed that causes a 404? Certainly "/". I remember guessing at a few other resources such as "/index.html" but I didn't check extensively to see if there were any resources that did work. On Wed, May 21, 2014 at 1:30 PM, Ali Lown <a...@lown.me.uk> wrote: > Gareth, > > Thanks for reporting this. Given the revisions you list, this sounds > like a problem caused by the atmosphere addition. > > Have you tried not listing localhost in each of the http_*_address > variables? > > What resource is attempted to be accessed that causes a 404? > > Thanks, > Ali > > On 18 May 2014 23:55, Gareth <gareth....@gmail.com> wrote: > > I don't know if this is the correct channel to post this, but this one > had > > me scratching my head all day so I figured I should. > > > > My config file currently looks like this: > > > > # A comma separated list of address on which to listen for connections. > > # Each address is a comma separated host:port pair. > > # Default value: localhost:9898 > > http_frontend_public_address = 192.168.0.10:9898,localhost:9898 > > > > # A optional host:port address on which to listen for websocket > connections. > > # If no value is set for http_websocket_public_address it defaults to the > > first address specified > > # by http_frontend_public_address. > > # Default value: localhost:9898 > > http_websocket_public_address = 192.168.0.10:9898,localhost:9898 > > > > # An optional host:port address for which the client is told to attempt > > websocket connections. > > # If no value is set for http_websocket_presented_address it defaults to > > http_websocket_public_address > > # Default value: localhost:9898 > > http_websocket_presented_address = 192.168.0.10:9898,localhost:9898 > > > > # Default value: values passed to http_frontend_public_address. > > http_frontend_addresses = 192.168.0.10:9898,localhost:9898. > > > > Where 192.168.0.10 is just my local box's ip address given by ifconfig: > > > > $ ifconfig > > > > eth0 Link encap:Ethernet HWaddr 00:1f:d0:5f:6e:73 > > inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0 > > inet6 addr: fe80::21f:d0ff:fe5f:6e73/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:2207164 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:1020261 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:2855724570 (2.8 GB) TX bytes:132984003 (132.9 MB) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:65536 Metric:1 > > RX packets:23626 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:23626 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:5654690 (5.6 MB) TX bytes:5654690 (5.6 MB) > > > > > > If I access the server via http://localhost:9898 via a browser wave runs > > fine, but if I access it through http://192.168.0.10:9898 I get 404 > errors > > no matter which page I visit. I'm on Ubuntu 12.04 LTS but I was also able > > to observe this behaviour on Amazon EC2 running Ubuntu 14.04 LTS where I > > had to verify http://localhost:9898 was working by using wget. > > > > I observed this behaviour in commit 47cd2e99 but happily it seems to be > > absent from wave-0.4-release. >
