So I now finally gave my buddy box (which was running fine in my local network for weeks) to my brother.
I set up port forwarding for his box in his network. He has a dyndns address via xxx.myfritz.net. I can successfully ssh to xxx.myfritz.net:55055 from my syncosync box to his (but not login with password of course). So I think everything is set up correctly.
Still, my syncosync box, using that myfritz.net address in the synch configuration, continues to show an “issue with remote host” icon. Even after a reboot.
On his side everything works fine (green icon). I use another dyndns provider.
I even restarted the key exchange, and that worked fine (with him leading).
What could be the problem? Where can I possibly find information on what is going wrong?
Ok, it is definitely a problem with DNS resolution. When I put the IPv4 address, synch works fine and icon becomes green. When I put back the xxx.myfritz.net address, synch icon becomes red again.
But the name resolution should work just fine. I can ping and ssh to that address from the command-line of my syncosync box.
that sound really strange.
All UI action - and even more - is possible via command line:
After you have configured the remote host, you can check with: sudo remotehost.py -v DEBUG -c
what is happening… remotehost.py -h
gives you all possible actions…
As almost every sos admin action needs root privileges, I do all this while being root on the syncosync box.
I think I will put an auto generated command line reference in the manual, could be a nice hack anyways
sosadmin@tims-syncosync:~ $ sudo remotehost.py -v DEBUG -c
[04-12 10:34:49.06] [ soscore] [ remotehost:67 ] [D] keyfile: /etc/syncosync/sshkeys/syncosync
[04-12 10:34:49.17] [ soscore] [ remotehost:95 ] [E] socket error: [Errno 13] Permission denied
RemoteUpStatus.NO_REPLY : Remote host is not reachable (this is no reply on this port from this host) , uuid:
So indeed not reachable - but why? Looks like some parsing is going wrong!?
With the --get option I see that the settings are correct. I wanted to play with the --other option but do not know how to pass the json configuration to it?
I sent you the xxx.myfritz.net address by PM so you can test with the --other option yourself what is going wrong there?
Ok, this was a genuine bug where the connection check tried to connect to the buddy box via IPv6 while everything else goes via IPv4. Stevie provided me with an ad-hoc fix which will make it into the next update.
Looks like some parsing is going wrong!?