"disconnected from chat server" when internet conn is fine

I just started getting this error today - my internet connection seems totally fine on all other apps and Keybase seems to get in a state where it just can't send anything. The failure is immediate, doesn't seem like it even tries to reach anything.

This is the first time I've tried to debug anything, but I figured there was a log or something I could start with.

I ran

```
$ tail -f /Users/nrser/Library/Logs/keybase.service.log
```

and tried to send a message, resulting in the following:

```
2019-09-04T02:03:06.217683+08:00 ▶ [DEBU keybase server.go:1720] 7e2d8 ++Chat: + Server: RetryPost: obr: 8fa0945c14e6103b [tags:chat-trace=HFRGWpmneV-F]
2019-09-04T02:03:06.217896+08:00 ▶ [DEBU keybase outbox.go:390] 7e2d9 ++Chat: | Outbox: resetting send information on obid: 8fa0945c14e6103b [tags:chat-trace=HFRGWpmneV-F]
2019-09-04T02:03:06.218039+08:00 ▶ [DEBU keybase sender.go:1192] 7e2da ++Chat: | Deliverer: force deliver loop invoked [tags:chat-trace=HFRGWpmneV-F]
2019-09-04T02:03:06.218054+08:00 ▶ [DEBU keybase server.go:1744] 7e2db ++Chat: - Server: RetryPost: obr: 8fa0945c14e6103b -> ok [time=372.764µs] [tags:chat-trace=HFRGWpmneV-F]
2019-09-04T02:03:06.218095+08:00 ▶ [DEBU keybase sender.go:1597] 7e2dc ++Chat: | Deliverer: deliverLoop: flushing outbox on new message: uid: 58fd1bb449f2e8160a630bcd8a86c119
2019-09-04T02:03:06.218197+08:00 ▶ [DEBU keybase sender.go:1611] 7e2dd ++Chat: | Deliverer: deliverLoop: flushing 1 items from the outbox: uid: 58fd1bb449f2e8160a630bcd8a86c119
2019-09-04T02:03:06.218227+08:00 ▶ [DEBU keybase sender.go:1653] 7e2de ++Chat: | Deliverer: deliverLoop: failed to send msg: uid: 58fd1bb449f2e8160a630bcd8a86c119 convID: 000010b525c8fa8b0439d66d5e586c38cafce16340b8fcab978d4f020e4c7e7f obid: 8fa0945c14e6103b err: disconnected from chat server attempts: 0 [tags:chat-trace=Ck9Hz5Q6cRqs]
2019-09-04T02:03:06.218248+08:00 ▶ [DEBU keybase sender.go:1311] 7e2df ++Chat: | Deliverer: doNotRetryFailure: not retrying offline failure, disconnected for: 3h18m25.807432739s [tags:chat-trace=Ck9Hz5Q6cRqs]
2019-09-04T02:03:06.218268+08:00 ▶ [DEBU keybase sender.go:1661] 7e2e0 ++Chat: | Deliverer: deliverLoop: failure condition reached, marking as error and notifying: obid: 8fa0945c14e6103b errTyp: OFFLINE attempts: 0 [tags:chat-trace=Ck9Hz5Q6cRqs]
2019-09-04T02:03:06.218445+08:00 ▶ [DEBU keybase activitynotifier.go:55] 7e2e1 ++Chat: + NotifyRouterActivityRouter: Activity(NONE,LOCAL)
2019-09-04T02:03:06.218466+08:00 ▶ [DEBU keybase activitynotifier.go:60] 7e2e2 ++Chat: - NotifyRouterActivityRouter: Activity(NONE,LOCAL) -> ok [time=21.521µs]
2019-09-04T02:03:06.218485+08:00 ▶ [DEBU keybase notify_router.go:923] 7e2e3 + Sending NewChatActivity LOCAL notification
2019-09-04T02:03:06.218727+08:00 ▶ [DEBU keybase notify_router.go:949] 7e2e4 - Sent NewChatActivity notification
```

Any idea what could be going on or where to go from here? Any diagnostics I can run?

Start with /Users/nrser/Library/Logs/keybase.service.log and the logged paths in sender.go and server.go. Trace why the client marks the chat connection offline immediately despite a working internet connection, using the recorded retry and delivery messages. Done means the cause is reproducible and the client either reports actionable diagnostics or sends successfully.

Written by the indexing model from the issue text.