On Sun, Jan 31, 2010 at 4:32 PM, deefactorial <[email protected]> wrote: > Hello Wave Protocol Group, > > I am having difficulty getting my wave server to federate with > wavesandbox.com, I am not receiving a ping from wavesandbox.com. > I've followed the installation instructions, I have a server > certificate from startssl.com and my ./check-certificates.sh is > verifying correctly. > I have the ejabberd server running and configured to for port 5275 and > can telnet into it remotely. > {5275, ejabberd_service, [ > {access, all}, > {shaper_rule, fast}, > {host, "wave.nomadicdomes.com", [{password, > "*****************"}]} > ]}, > I also concatenated my certificates to the ejabberd.pem certs. > > I have my DNS configured for port 5275 > deefactor...@resonance:~$ dig +short -t SRV _xmpp- > server._tcp.wave.nomadicdomes.com > 0 0 5275 wave.nomadicdomes.com. > deefactor...@resonance:~$ dig +short -t SRV _xmpp- > server._tcp.nomadicdomes.com > 0 0 5275 wave.nomadicdomes.com. > > run-config.sh > # Domain name of the wave server > WAVE_SERVER_DOMAIN_NAME=nomadicdomes.com > > # Host name and port the wave server's client frontend listens on > WAVE_SERVER_HOSTNAME=wave.nomadicdomes.com > WAVE_SERVER_PORT=9876 > > # The version of FedOne, extracted from the build.properties file > FEDONE_VERSION=`grep ^fedone.version= build.properties | cut -f2 -d=` > > ### Server-specific variables > ### > > # These will probably need to be changed > XMPP_SERVER_SECRET=*************** > PRIVATE_KEY_FILENAME=${WAVE_SERVER_DOMAIN_NAME}.key > > # The order of certificates is important. Place intermediate certs > # after "${WAVE_SERVER_DOMAIN_NAME}.crt". Please refer to > # http://code.google.com/p/wave-protocol/wiki/Certificates > # for more details. > CERTIFICATE_FILENAME_LIST=$ > {WAVE_SERVER_DOMAIN_NAME}.crt,sub.class1.server.ca.pem > > # These should be okay to leave alone > CERTIFICATE_DOMAIN_NAME=$WAVE_SERVER_DOMAIN_NAME > XMPP_SERVER_HOSTNAME=$WAVE_SERVER_DOMAIN_NAME > XMPP_SERVER_PORT=5275 > XMPP_SERVER_PING=wavesandbox.com > > # Set XMPP_SERVER_IP to localhost if the XMPP and FedOne servers are > # running on the same host > #XMPP_SERVER_IP=$XMPP_SERVER_HOSTNAME > XMPP_SERVER_IP=127.0.0.1 > > # Set true to disable the verification of signed deltas > WAVESERVER_DISABLE_VERIFICATION=false > > # Set true to disable the verification of signers (certificates) > WAVESERVER_DISABLE_SIGNER_VERIFICATION=false > > > > output from ./run-server.sh > 31-Jan-2010 9:24:49 PM > org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl <init> > INFO: Wave Server configured to host local domains: [nomadicdomes.com] > 31-Jan-2010 9:24:49 PM org.waveprotocol.wave.examples.fedone.ServerMain > $RpcInetSocketAddressFactory <init> > INFO: Starting client frontend on host: wave.nomadicdomes.com port: > 9876 > 31-Jan-2010 9:24:49 PM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > initialize > INFO: initializing with JID: localhost > 31-Jan-2010 9:24:49 PM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > start > INFO: connected to XMPP server with JID: wave.nomadicdomes.com > 31-Jan-2010 9:24:49 PM > org.waveprotocol.wave.examples.fedone.federation.xmpp.XmppDisco > sendDiscoItemsGet > INFO: Trying to discover remote server: wavesandbox.com > 31-Jan-2010 9:24:49 PM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: sent XMPP packet: > <iq type="get" id="6864-0" to="wavesandbox.com" > from="wave.nomadicdomes.com"> > <query xmlns="http://jabber.org/protocol/disco#items"/> > </iq> > 31-Jan-2010 9:24:49 PM > org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent > sendPacket > INFO: key for this error is org.xmpp.packet.IQ:wavesandbox.com:6864-0 > 31-Jan-2010 9:24:49 PM > org.waveprotocol.wave.examples.fedone.ServerMain run > INFO: Starting server >
All of that looks good. When I start my FedOne server and try to add a user from your domain I get: <iq type="get" id="1252-3" to="nomadicdomes.com" from="wave.bitworking.net"> <query xmlns="http://jabber.org/protocol/disco#items"/> </iq> Feb 1, 2010 8:35:43 AM org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent sendPacket INFO: key for this error is org.xmpp.packet.IQ:nomadicdomes.com:1252-3 Feb 1, 2010 8:35:44 AM org.waveprotocol.wave.examples.fedone.federation.xmpp.WaveXmppComponent processPacket INFO: received XMPP packet: <iq type="error" to="wave.bitworking.net" from="nomadicdomes.com" id="1252-3"> <error type="cancel"> <remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> </error> </iq> So it looks like it's not able to find the Wave service or the Disco service. Can you look at the ejabberd logs and see if it successfully finds the FedOne server? > > I'm at a loss of where to go from here. Is there any logs that I can > look at to find out what is going on ? > I noticed that the wavesandbox.com requires that I disable chat on my > XMPP server, how do I do that in ejabberd ? You only need to do that if nomadicdomes.com is a Google Apps domain. If it was then you disable Chat by visiting the Google Apps dashboard, which would be located at http://google.com/a/nomadicdomes.com Thanks, -joe -- Joe Gregorio Developer Relations, Google Wave -- 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.
