/apis/siyuan/version returns HTTP 522 while other routes on the same host respond normally

Environment

SiYuan 3.8.1, Windows desktop, official SiYuan cloud, paid subscription (Warrior).
All times below are UTC+2.

Symptom

Since 2026-08-27 08:14 the kernel can no longer reach the version endpoint:

E 2026/08/27 08:14:23 rhy.go:81: get version info failed: Get "https://siyuan-cloud.liuyun.io/apis/siyuan/version?ver=3.8.1": unexpected EOF
E 2026/08/27 08:14:23 updater.go:211: get announcement failed: Get "https://siyuan-cloud.liuyun.io/apis/siyuan/version?ver=3.8.1": unexpected EOF

13 failures between 08:14 and 14:39 that day, no success in between.

Direct probes

Requesting the same URL outside SiYuan returns HTTP 522 (Cloudflare: connection
timed out to origin), then plain timeouts on retry. Nine attempts spread over the
day, zero responses, last checked at 15:15.

Other routes on the same host answer normally at the same moment:

Request Result
GET / 200
POST /apis/siyuan/user 200, {"msg":"Bad request","code":-1}
POST /apis/siyuan/login 200, {"msg":"Wrong password","code":-1,...}
GET /apis/siyuan/version?ver=3.8.1 522, then timeout

The origin behind Cloudflare is therefore up. Only this one route hangs.

Ruled out on the client side

  • DNS resolves and TCP 443 opens normally
  • TLS certificate is authentic (CN=liuyun.io, Google Trust Services), so no
    interception by antivirus or firewall
  • no system proxy configured
  • reproduced from a second, independent network in another country with the
    same result

Impact

Update checks and announcements are unavailable, and the kernel log fills with
the errors above. Data sync itself is not affected.

Question

Is this a known issue on the service side, or is there something left to check
locally?

    Welcome to here!

    Here we can learn from each other how to use SiYuan, give feedback and suggestions, and build SiYuan together.

    Signup About
    Please input reply content ...
    • patsig
      VIP Warrior Author

      Thank you, that solved it.

      I logged out under Settings → Account and logged back in. Sync resumed
      immediately and has been running normally since, with the last successful
      sync a few minutes ago and no errors reported.

      For the record, the /apis/siyuan/version endpoint that was returning
      HTTP 522 yesterday now answers with HTTP 200 as well, so that part has
      cleared up too.

      Thanks again for the quick help.

    • MiscReply
    • 88250

      Please log out and log back in, then observe the situation. Thank you.