Troubleshooting running a Sonobus/aoo-compatible aooserver

[paulreimer]

I am attempting to run an additional aooserver to aoo.sonobus.net, mostly as a learning exercise but also to further develop various AOO clients -- and hoping to keep everything compatible with all existing Sonobus clients.

I would like to know the aooserver version/git commit currently running on aoo.sonobus.net; I am able to use Sonobus 1.6.1 with a locally compiled aooserver from the master branch as well as aoonew, but not aoonewest/aoonewester.

In an AOO client I hacked together (iOS), I am able to use aoo.sonobus.net, but for some reason it won't work with any aooserver that I have compiled myself -- I get client_endpoint: connection was closed errors; still trying to investigate more about this. But I'm hoping to start from an identical aooserver to what is running on aoo.sonobus.net, since that does work very well.

[essej]

Correct, do not attempt to use aoonewest or aoonewester, that is future research and development using a new version of the AOO lib, and the protocol has changed there... just stick to the develop branch (or main).

[actionless]

i've built it from master branch but same result - it starts and clients connect to it, but nothing happens,

only from time to time it writes aoo_server: not an AOO NET message!

with (aoo.sonobus.net it also works fine, same as for original issue reporter)

also when using direct connection

UPD: my bad - i was trying to connect specifying port manually, but it worked when specifying only IP address