Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NSOSStatusErrorDomain -9829 #642

Closed
hanche opened this issue Aug 22, 2020 · 1 comment
Closed

NSOSStatusErrorDomain -9829 #642

hanche opened this issue Aug 22, 2020 · 1 comment
Assignees

Comments

@hanche
Copy link

hanche commented Aug 22, 2020

It seems that every time I leave home, work, or some other place with wifi access (or possibly everytime my network connection changes), OwnTracks loses its connection to the server, a badge count starts going up on the app icon, and the status is shown as:

idle NSOSStatusErrorDomain -9829 The operation couldn't be completed. (OSStatus error -9829.) { "_kCFStreamErrorCodeKey" = "-9829";

Merely going into Settings, not even touching anything there, cures the problem temporarily.

Here is a typical excerpt from the mosquitto log (IP address elided). Most new connections seem to end this way, but as I stated, when I go into Settings, it connects successfully.

20200822_094325: New connection from IP on port 8883.
20200822_094325: OpenSSL Error: error:1417C0C7:SSL routines:tls_process_client_certificate:peer did not return a certificate
20200822_094325: Socket error on client <unknown>, disconnecting.

I am running the latest OwnTracks (13.1.7, 8 months old?) in MQTT mode with TLS enabled.
Exported config file attached (hostname faked and waypoints removed, otherwise, it is the real thing).

config.otrc.txt

Any ideas what could be wrong?

@ckrey ckrey self-assigned this Aug 24, 2020
@ckrey
Copy link
Member

ckrey commented Aug 24, 2020

This is an already known problem #605, which will be probably be solved in the upcoming version (minimum OS requirement is iOS 13). I will send you @hanche an invite to pre-test this version.

Closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants