Issue with Websocket support

[aolg-gith]

Hello,
I have a fresh installation showing the following issue when running onedrive --monitor.

D-Bus message bus daemon is available; GUI notifications are now enabled
Using IPv4 and IPv6 (if configured) for all network operations
Attempting to contact the Microsoft OneDrive Service
Successfully reached the Microsoft OneDrive Service
Configuring Global Azure AD Endpoints
Attempting to enable WebSocket support to monitor Microsoft Graph API changes in near real-time.
ERROR: Microsoft OneDrive API returned an error with the following message:
  Error Message:       HTTP request returned status code 400 (Bad Request)
  Error Reason:        Operation not supported
  Error Code:          notSupported
  Error Timestamp:     2026-02-07T08:47:06
  API Request ID:      86cedea1-1fe1-426f-8b3d-c5ac4efbf726
ERROR: Unable to configure WebSocket support to monitor Microsoft Graph API changes in near real-time.
OneDrive synchronisation interval (seconds): 300
Initialising filesystem inotify monitoring ...
Performing initial synchronisation to ensure consistent local state ...
Attempting to contact the Microsoft OneDrive Service
Successfully reached the Microsoft OneDrive Service
Starting a sync with Microsoft OneDrive
Fetching items from the OneDrive API for Drive ID: b!-bVRjpTsbEC3g59Tbb6i3QwEL2H2DK5Nvo9lJAc73qtk6A7dcFxsRaX5SQ715X7k .. 
No changes or items that can be applied were discovered while processing the data received from Microsoft OneDrive
Performing a database consistency and integrity check on locally stored data . 
Scanning the local file system '~/OneDrive' for new data to upload .. 
Performing a last examination of the most recent online data within Microsoft OneDrive to complete the reconciliation process
Fetching items from the OneDrive API for Drive ID: b!-bVRjpTsbEC3g59Tbb6i3QwEL2H2DK5Nvo9lJAc73qtk6A7dcFxsRaX5SQ715X7k . 
No changes or items that can be applied were discovered while processing the data received from Microsoft OneDrive
Sync with Microsoft OneDrive is complete
Due to a termination signal, internal processing stopped abruptly. The application will now exit in a unclean manner.

As far as I can understand the monitoring process indeed dies at the end. Running --sync seems to work fine in turn. Do you know how I can fix it?
Thanks a lot! :)

[abraunegg]

@aolg-gith
Please follow the basic troubleshooting steps as outlined in the readme.md

[aolg-gith]

Hi,
thanks. I confirm that I am running the latest release. Following points 2,3,4 of the troubleshooting guide didn't change the behavior. I am running onedrive on Ubuntu 25.10. Unfortunately my understanding is not quite high-level enough to confidently building the client from scratch. Running with --verbose, it seems like the error occurs around here

DEBUG: Attempting to enable WebSocket support to monitor Microsoft Graph API changes in near real-time.
DEBUG: Read token from appConfig
DEBUG: Authorised State: true
DEBUG: Request a Socket.IO Subscription Endpoint: https://graph.microsoft.com/v1.0/me/drive/root/subscriptions/socketIo
DEBUG: HTTP get request to URL: https://graph.microsoft.com/v1.0/me/drive/root/subscriptions/socketIo
DEBUG: Microsoft OneDrive OAuth2 Access Token Valid Until (Local): 2026-Feb-07 11:44:32.0023144
DEBUG: response.statusLine.code: 400
DEBUG: response.statusLine.reason: Bad Request
DEBUG: actual curl response: Curl debugging: 
< get https://graph.microsoft.com/v1.0/me/drive/root/subscriptions/socketIo
< 400 Bad Request (1.1)
> splogid: 3c9af4a1-60e0-0000-b04b-42f522cf651d
> strict-transport-security: max-age=31536000
> x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"Italy North","Slice":"E","Ring":"3","ScaleUnit":"002","RoleInstance":"MI3PEPF000001B7"}}
> transfer-encoding: chunked
> date: Sat, 07 Feb 2026 09:37:49 GMT
> client-request-id: 2f5a0c7a-bdf5-46de-8db1-cb7878005195
> request-id: 2f5a0c7a-bdf5-46de-8db1-cb7878005195
> cache-control: no-store, no-cache
> content-type: application/json
Curl response: 

----
{"error":{"code":"notSupported","message":"Operation not supported","innerError":{"date":"2026-02-07T09:37:49","request-id":"2f5a0c7a-bdf5-46de-8db1-cb7878005195","client-request-id":"2f5a0c7a-bdf5-46de-8db1-cb7878005195"}}}
----

DEBUG: Handling a OneDrive API exception:
DEBUG: Curl debugging: 
< get https://graph.microsoft.com/v1.0/me/drive/root/subscriptions/socketIo
< 400 Bad Request (1.1)
> splogid: 3c9af4a1-60e0-0000-b04b-42f522cf651d
> strict-transport-security: max-age=31536000
> x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"Italy North","Slice":"E","Ring":"3","ScaleUnit":"002","RoleInstance":"MI3PEPF000001B7"}}
> transfer-encoding: chunked
> date: Sat, 07 Feb 2026 09:37:49 GMT
> client-request-id: 2f5a0c7a-bdf5-46de-8db1-cb7878005195
> request-id: 2f5a0c7a-bdf5-46de-8db1-cb7878005195
> cache-control: no-store, no-cache
> content-type: application/json
Curl response: 

----
{"error":{"code":"notSupported","message":"Operation not supported","innerError":{"date":"2026-02-07T09:37:49","request-id":"2f5a0c7a-bdf5-46de-8db1-cb7878005195","client-request-id":"2f5a0c7a-bdf5-46de-8db1-cb7878005195"}}}
----

DEBUG: onedrive.OneDriveApi.obtainWebSocketNotificationURL() - Generated a OneDriveException
DEBUG: 
DEBUG: ERROR: Microsoft OneDrive API returned an error with the following message:
DEBUG:   Error Message:       HTTP request returned status code 400 (Bad Request)
DEBUG:   Error Reason:        Operation not supported
DEBUG:   Error Code:          notSupported
DEBUG:   Error Timestamp:     2026-02-07T09:37:49
DEBUG:   API Request ID:      2f5a0c7a-bdf5-46de-8db1-cb7878005195
DEBUG:   Calling Function:    syncEngine.obtainWebSocketNotificationURL()
DEBUG: Raw Error Data: HTTP request returned status code 400 (Bad Request)
{
    "error": {
        "code": "notSupported",
        "innerError": {
            "client-request-id": "2f5a0c7a-bdf5-46de-8db1-cb7878005195",
            "date": "2026-02-07T09:37:49",
            "request-id": "2f5a0c7a-bdf5-46de-8db1-cb7878005195"
        },
        "message": "Operation not supported"
    }
}
DEBUG: JSON Message: {"error":{"code":"notSupported","innerError":{"client-request-id":"2f5a0c7a-bdf5-46de-8db1-cb7878005195","date":"2026-02-07T09:37:49","request-id":"2f5a0c7a-bdf5-46de-8db1-cb7878005195"},"message":"Operation not supported"}}
DEBUG: 
DEBUG: ERROR: Unable to configure WebSocket support to monitor Microsoft Graph API changes in near real-time.

I have the Snap version 8.18.0 of Curl. Should I provide the full debug file?
Thank you again!

[abraunegg]

@aolg-gith

I am running onedrive on Ubuntu

This will be a contributor to your issue due to packaging policies of the platform and distribution.

I have the Snap version 8.18.0 of Curl

Please do not use snaps ... yes - I know that this is what Ubuntu does ... see my above point. Do not use snaps - they will cause you no end of issues.

Unfortunately my understanding is not quite high-level enough to confidently building the client from scratch

No problem - at this stage there is near zero change in 'master' as to the v2.5.10 release, and doing that step will be tedious for near zero gain.

Please open a bug report, and provide complete debug logs for this issue via email.

My advice for you at the moment however is this:

• Stop using Ubuntu and use a much better distribution
  • If you wish to stay in the 'apt' ecosystem, switch to using the latest version of Debian or Linux Mint Debian Edition. Avoid as much as possible Ubuntu and/or any distribution based on Ubuntu.
  • If you wish to use something better - use Fedora, Manjaro, Arch, Gentoo as a starting point.
• Stop using 'snaps' on your platform - avoid them as much as you can

[abraunegg]

@aolg-gith

I have further reviewed the application output you have provided (both the normal log and the debug snapshot), and based on what is shown, this is the current analysis:

WebSocket configuration failure

The WebSocket setup is failing because the Microsoft Graph API is explicitly returning:

ERROR: Microsoft OneDrive API returned an error with the following message:
  Error Message:       HTTP request returned status code 400 (Bad Request)
  Error Reason:        Operation not supported
  Error Code:          notSupported
  Error Timestamp:     2026-02-07T08:47:06
  API Request ID:      86cedea1-1fe1-426f-8b3d-c5ac4efbf726

This response is being returned by Microsoft Graph for the endpoint:

/me/drive/root/subscriptions/socketIo

This indicates that Microsoft is rejecting the request for this account/drive/tenant, not that the client has crashed or terminated internally. When this occurs, the client correctly falls back to standard polling behaviour and continues normal synchronisation.

There is no evidence in the provided debug output that the monitoring logic “dies” or exits due to this WebSocket error.

Application termination

The line:

Due to a termination signal, internal processing stopped abruptly.

means the 'onedrive' process received an external termination signal (for example SIGTERM or SIGINT). This does not indicate an internal failure or that monitor mode completed on its own.

Common causes include:

• Closing the terminal or SSH session the client was running in
• Pressing Ctrl+C
• systemd stopping or restarting the service
• User session logout, suspend, or shutdown

The debug log you supplied does not show any internal fatal error after WebSocket configuration fails.

Next steps (still required)

I have already asked that you:

1. Generate an applicable debug log using the applicable process
2. Open a bug report with the requested details

At this point, no bug report has been opened, and no additional debug data has been provided beyond what is shown above.

To proceed further, I need:

• A bug report opened using the issue template
• Full debug logs covering:
  • How the client is started (interactive terminal vs systemd service)
  • What happens immediately before the termination signal is received
• Confirmation of whether this is being run under systemd, and if so:
  • The output of systemctl status onedrive or the applicable systemd service
  • Relevant journalctl -u onedrive output around the time it stops

Until that information is provided, there is no evidence that the monitoring process is terminating on its own or due to a client-side fault.

I am waiting for the above details so this can be properly investigated.

[aolg-gith]

Thanks!! I'm opening the bug report right now.