One device, first device, is fine. Others show generic errors

[moshin34]

So not my first rodeo, but this one is odd.

How can I trouble shoot, where to look?

New install on docker, first device registered fine, and pushes fine.

Device 2, and 3, cannot login at all. "Logging in please wait" hangs around for awhile, before it shows "unknown server error"

[Frenzie]

The server logs will tell you if the request is arriving at all. My first guess would be that it's not.

[moshin34]

thanks for your response.

pass the health check just fine, but on device I can't seem to register or login. Im losing my mind. Every other time ive done this, its been a 10 second container stand up.

user@workstation:/mnt/docker/stacks/book-stack$ docker logs kosync *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 9 May 19 15:13:04 d51a429eb54a syslog-ng[18]: syslog-ng starting up; version='3.5.6' May 19 15:17:01 d51a429eb54a CRON[36]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 19 16:17:01 d51a429eb54a CRON[39]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 19 17:17:01 d51a429eb54a CRON[42]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 19 18:17:01 d51a429eb54a CRON[45]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 19 19:17:01 d51a429eb54a CRON[48]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nothing useful here, I don't think.

I APPEAR TO PASS THE TEST ON THE DOCKER HOST

user@hostcomputer:/mnt/docker/stacks/book-stack$                                                                                           k
*   Trying 127.0.0.1:7200...acks/book-stack$ curl -k -v -H "Accept: application/vnd.koreader.v1+json" https://localhost:7200/healthcheck 
* Connected to localhost (127.0.0.1) port 7200 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: [NONE]
*  start date: May 29 05:50:01 2017 GMT
*  expire date: May 29 05:50:01 2018 GMT
* using HTTP/1.1
> GET /healthcheck HTTP/1.1
> Host: localhost:7200
> User-Agent: curl/7.88.1
> Accept: application/vnd.koreader.v1+json
< HTTP/1.1 200 OK
< Server: openresty/1.7.10.1
< Date: Mon, 19 May 2025 19:16:11 GMT
< Content-Type: application/json
< Connection: keep-alive
< X-Framework: gin/0.2.0
< Content-Length: 14
* Connection #0 to host localhost left intact
{"state":"OK"}

AND FROM A COMPUTER ON THE LAN OVER THE FQDN

user@their-MacBook-Air ~ % curl -k -v -H "Accept: application/vnd.koreader.v1+json" https://kosync.domain.tld/healthcheck
* Host kosync.domain.tld:443 was resolved.
* IPv6: (none)
* IPv4: 71.105.144.141
*   Trying 71.105.144.141:443...
* Connected to kosync.domain.tld (8.8.8.8) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=kosync.domain.tld
*  start date: May 18 23:29:46 2025 GMT
*  expire date: Aug 16 23:29:45 2025 GMT
*  issuer: C=US; O=Let's Encrypt; CN=R10
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://kosync.domain.tld/healthcheck
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: kosync.domain.tld]
* [HTTP/2] [1] [:path: /healthcheck]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: application/vnd.koreader.v1+json]
> GET /healthcheck HTTP/2
> Host: kosync.domain.tld
> User-Agent: curl/8.7.1
> Accept: application/vnd.koreader.v1+json
> 
* Request completely sent off
< HTTP/2 200 
< content-type: application/json
< date: Mon, 19 May 2025 19:13:14 GMT
< server: openresty/1.7.10.1
< x-framework: gin/0.2.0
< content-length: 14
< 
* Connection #0 to host kosync.domain.tld left intact
{"state":"OK"}% 

Where else can/should I look for an error. Doesn't the above imply I am all in the clear?

[Frenzie]

I meant the logs mounted under -v pwd/logs/app:/app/koreader-sync-server/logs in the sample command.

Where else can/should I look for an error.

You could try a simple ping or Wikipedia lookup from the device where it doesn't work to double check it's properly connecting at all.

[moshin34]

I think it might be related to this.

GeorgeSG/KoInsight#11 (comment)

[Frenzie]

I don't think that's relevant to this project, but it's simple to test with the latest KOReader nightly.

[moshin34]

Noted. Thank you. I will do that too.