Hello and thanks for the quick reply The console-client is working fine. I now changed some of the settings in my run-config.sh and get the 405 in my local browser too now. However here is my run-config.sh:
#================================================== nikl...@wase:~/wave-protocol$ cat run-config.sh |grep -v \# WAVE_SERVER_DOMAIN_NAME=wase WAVE_SERVER_HOSTNAME=localhost WAVE_SERVER_PORT=9876 WEBSOCKET_SERVER_HOSTNAME=192.168.0.164 WEBSOCKET_SERVER_PORT=9898 FEDONE_VERSION=`grep ^fedone.version= build.properties | cut -f2 -d=` XMPP_SERVER_SECRET=5276 PRIVATE_KEY_FILENAME=wave.key CERTIFICATE_FILENAME_LIST=wave.crt CERTIFICATE_DOMAIN_NAME=$WAVE_SERVER_DOMAIN_NAME XMPP_SERVER_HOSTNAME=wase XMPP_SERVER_PORT=5275 XMPP_SERVER_PING=wavesandbox.com XMPP_SERVER_IP=localhost WAVESERVER_DISABLE_VERIFICATION=true WAVESERVER_DISABLE_SIGNER_VERIFICATION=true http_frontend_hostname=192.168.0.164 http_frontend_port=9898 xmpp_component_name=wave #=============================== Here are some of the configs of my OpenFire-Server: external components port: 5275 external components shared secret: 5276 whitelist subdomain: wave whitelist shared sected: mywave xmpp.domain: wase And some configs from the virtual server: virtual machine: Virtualbox Network adapter: bridget IP-Adress: 192.168.0.164 subnet mask: 255.255.255.0 hostname: wase Ubuntu 10.04 64bit Server. Sun-java6-jre is the only and therefore the standard java runtime environment I have currently installed. The IP of my local (physical) machine is 192.168.0.100, 255.255.255.0 Whe I try to access the webinterface via 192.168.0.164:9898, the Server prints out this to the shell: 2010-08-09 19:49:04.894:DBUG::STARTED org.eclipse.jetty.server.ser...@a0430b6 2010-08-09 19:49:08.649:DBUG::REQUEST / on org.eclipse.jetty.server.nio.selectchannelconnecto...@5fc6e818 2010-08-09 19:49:08.649:DBUG::servlet=org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider $WaveWebSocketServlet-1670109169 2010-08-09 19:49:08.649:DBUG::servlet holder= org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider $WaveWebSocketServlet-1670109169 2010-08-09 19:49:08.649:DBUG::chain= 2010-08-09 19:49:08.663:DBUG::RESPONSE / 405 2010-08-09 19:49:08.729:DBUG::REQUEST /favicon.ico on org.eclipse.jetty.server.nio.selectchannelconnecto...@5fc6e818 2010-08-09 19:49:08.729:DBUG::servlet=org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider $WaveWebSocketServlet-1670109169 2010-08-09 19:49:08.729:DBUG::servlet holder= org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider $WaveWebSocketServlet-1670109169 2010-08-09 19:49:08.730:DBUG::chain= 2010-08-09 19:49:08.731:DBUG::RESPONSE /favicon.ico 405 This is what Chrome will then show: http://www.abload.de/img/screenshot-error405httqasi.png Thx for you patience (I know it's very probably my fault!) and the help! On Aug 9, 8:31 am, Lennard de Rijk <[email protected]> wrote: > Hi Niklaus, > > > > > > On Sun, Aug 8, 2010 at 9:19 AM, bash.vi <[email protected]> wrote: > > Does anyone have a link to a howto that can be understood by a > > beginner? > > > I got FedOne working on a virtual Ubuntu 10.04 server. The console- > > client is running. > > I have the files from the installationsguide (http://code.google.com/p/ > > wave-protocol/wiki/Installation) in /home/myusername/wave-protocol > > I did the following to get the webclient running, but I think I missed > > some steps :( : > > cd /home/myusername/wave-protocol > > hg clonehttps://io2010.wave-protocol.googlecode.com/hg/ > > dist-server compile_gwt > > ./run-server.sh > > > compiling with "ant dist-serverant" ends successful. > > When I'm accessing the webinterface with a browser from my physical > > machine via "http://192.168.0.164:9898/"; it will tell me that it can't > > access the page. > > When I access the Server with x-forwarding and then start a Chromium > > Browser to access "http://localhost:9898"; Chromium tells me "http > > error 405. Problem accessing /. Reason: HTTP method GET is not > > supported by this URL". > > > What am I doing wrong? > > Have you tried running the console client and see if the server actually > worked (./run-client.sh test)? Don't forget to update to the latest head so > that the websocket connection actually works again :). > > If the server works could you please give more information about your setup? > What does your config file look like? > > Greetings, > Lennard -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
