Intermittent connection issues - error -9829 in IOS client after network change

[bdillahu]

Re: Intermittent connection issues - error -9829 in IOS client

I've seen some discussion and bug fixes (as referenced above), but I'm on the newer 9.1.6 client and seem to have a reproducible issue (still?) :-)

I have client certificates set up, custom connection mode on, etc. All seems happy and works fine, until my "method of connection" changes. If I go from WiFi to cell it looses connection and starts getting the 9829 error. I can kill the app (swipe up) and restart it and it immediately connects and will seem to stay connected until I come into WiFi range of a access point I connect to automatically.

When it connects, same thing happens. Again, kill the app and restart and it connects and all happy.

I've turned off client certs for now and after several days, haven't seen it occur with the client cert deactivated (i.e. it will stay connected reasonably).

[kylejohnson]

Any movement on this?
@bdillahu Did the issue continue to not resurface once client certs are turned off? I seem to be hitting the same issue.

[bdillahu]

I never had any more issues with the client certs turned off... I never got back to trying it again with them on.

…

-- Bruce Dillahunty http://brucedillahunty.xyz

On Jan 10, 2017, at 20:47, Kyle Johnson ***@***.***> wrote: Any movement on this? @bdillahu <https://github.com/bdillahu> Did the issue continue to not resurface once client certs are turned off? I seem to be hitting the same issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#408 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB9pRjDZUcctx9zYq9XnHMondiNDI0OVks5rRDSdgaJpZM4JTRPe>.

[denislooby]

I'm seeing this with the 9.72 client.
Seems to happen if I'm in an area where I end up hopping between wifi and mobile net a lot.
I can fix it by just going into connection settings and then back out without changing anything, it tries to connect then and succeeds.

[GitifyMe]

I too see this behavior with the 9.7.2 client.
I observed this when trying to connect to the AWS IoT broker. The broker itself issued the certificate, and I succeeded when connecting using HTTP and client certificate via curl.

I would really like to use OwnTracks with AWS ! I would even buy the MQTTInspector if I could be sure AWS IoT works (preferrably with a bit of guidance).

[ckrey]

@GitifyMe -9892 is the error code you get when you try to connect to a broker which requests a client certificate, but you don't provide one.

But this is not related to the issue here.

If you want to connect OwnTracks to AWS IoT, you can do that based on the docs in the booklet. We do not recommend doing that because the OwnTracks app uses MQTT features which AWS IoT does not support. This limits the functionality of the OwnTracks app.

MQTTInspector is a USD 1.99$ investment. I don't see this related to your attempt to connect OwnTracks to AWS IoT. BTW MQTTInspector does support TLS, but no client certificates. You will not be able to connect MQTTInspector to AWS IoT.

[GitifyMe]

@ckrey Yes, I had meanwhile success with OwnTracks (exactly 6 mins ago!). The issue was for me in essence two-fold: Caused by a company firewall, the WLAN did not let me through --> solved by using mobile data now. Secondly, in AWS you need to attach a policy to the client certificate that permits connections, publishing and subscriptions.
It works now! Thanks Christoph for the fast response and the honest answer regarding MQTTInspector.