Does this work when the gui uses a unix socket?

[Kropatz]

I setup my syncthing to provide the gui as a socket under /synced/gui-socket.
Tried setting that path in the tray application as the "Syncthing URL" and provided the API key, but that didn't work.
Is there a different way to specify the path or does the tray app not support interacting with the socket?

[Martchus]

Syncthing Tray uses Qt's HTTP library so I guess this won't work. Maybe there's a way to workaround it somehow (with minor code changes) but I wouldn't know out of my head.

[Martchus]

Looks like this will make it into Qt 6.8.0 (https://codereview.qt-project.org/c/qt/qtbase/+/550202 has just been merged).

[Kropatz]

I have qt 6.8.0 now, but it doesn't seem to work unfortunately.
Tried http, unix+http and local+http.
Error is "Unable to request Syncthing config: host not found"

[Martchus]

Maybe I'll have to enable it from the application-side as well. However, the diff on Gerrit doesn't look that way. The only documentation I found are unfortunately just the release notes.

The feature might still be buggy. Or it is a simple permission error.

[Kropatz]

Think it might be a bug, works fine when I use curl for example

$ curl --header "X-API-Key: $API_KEY" --unix-socket /synced/gui-socket http://localhost/rest/system/status
{
  "alloc": 34579152,
  "connectionServiceStatus": {
    "quic://0.0.0.0:22000": {
      "error": null,
      "lanAddresses": [
...
...

Added some logging and everything looks fine, but it doesn't work:

Info: Supported schemes: file, qrc, http, unix+http, local+http, https, data
Info: Querying API: GET unix+http:///synced/gui-socket/rest/system/status
Error: Syncthing API error: Host  not found

I'll wait for a new Qt version, or at least until there are some examples/docs 😄

[Martchus]

Despite Qt's generally great documentation I wouldn't wait for a documentation change.

Maybe it is fixed in 6.8.1 which will be release soon. If not, it might be a good idea to come up with a minimum reproducer and file a bug (or maybe there's already an open bug).