Jan-Philipp,

Note: the naming can seem confusing. If you can think up some better
names for each of the following config variables, let us know!

> wave_server_domain = wave.mydomain.tld

Is the pretty name the wave server system uses to refer to itself.

> http_frontend_public_address = wave.mydomain.tld:80

Is the address the server uses if it needs to redirect itself via a
client redirect, since the client can only see the public address. All
HTTP traffic here, must find its way to http_frontend_address
magically.

> http_websocket_public_address = localhost:9898

Is the address/port for the websocket server to bind to. All websocket
requests _must_ go here.

> http_websocket_presented_address = wave.mydomain.tld:80

Is the address/port given to the client for websocket requests to be
sent to. All websocket traffic must find its way to
http_websocket_public_address magically.

> http_frontend_addresses = localhost:9898

Is the address/port for the static files server to bind to. All HTTP
requests _must_ go here ultimately.

Overall, the settings you are presenting above seem ok.

> Like for my D* installation, I use the Cherokee webserver as reverse proxy – 
> so that any request to wave.mydomain.tld is internally converted to 
> localhost:9898 . This, however, doesn't quite work out. I need to add a rule 
> for rewriting the URLs from 127.0.0.1:9898/abcde to wave.mydomain.tld/abcde . 
> Otherwise I am redirected to localhost after logging in.

What do you mean by 'internally converted'? You want to traffic to be
sent directly (unaltered) to localhost:9898 from wave.mydomain.tld:80.
(As if it were a local port forward firewall rule)

> The next problem: When doing this, I remain always offline. Because this is 
> only true when logging in from other computers, I'd guess it's trying to 
> connect to localhost.

Open the chrome developer console and check where the websocket is
attempting to connect to. (Should be http_websocket_presented_address)
Secondly, can Cherokee (specifically, the version you are running)
forward Websocket traffic? Do you need a special rule for it?

> Altering http_websocket_public_address to wave.mydomain.tld:80 results in 
> permission errors and not starting the Apache Wave server.
This is as expected, assuming your hosts file does not override
wave.mydomain.tld to localhost (which it doesn't need to), and that
you are running WIAB as non-root.

Ali

Reply via email to