Connection Timeout

[vfandrea]

onedrive is not able to connect to Microsoft OneDrive Login Service

running

onedrive --monitor --verbose

I get this output

Reading configuration file: /home/username/.config/onedrive/config
Invalid value for key in config file - using default value: monitor_interval
Configuration file successfully loaded
Using 'user' configuration path for application config and state data: /home/andrea/.config/onedrive
WARNING: Configured 'threads = 8' exceeds available CPU cores (2).
         This may lead to reduced performance, CPU contention, and instability. For best results, set 'threads' no higher than the number of physical CPU cores.
D-Bus message bus daemon is available; GUI notifications are now enabled

WARNING: Your cURL/libcurl version (8.5.0) has known HTTP/2 bugs that impact the use of this client.
         Please report this to your distribution, requesting an update to a newer cURL version, or consider upgrading it yourself for optimal stability.
         Downgrading all client operations to use HTTP/1.1 to ensure maximum operational stability.
         Please read https://github.com/abraunegg/onedrive/blob/master/docs/usage.md#compatibility-with-curl for more information.

Using IPv4 and IPv6 (if configured) for all network operations
Attempting to contact Microsoft OneDrive Login Service

Cannot connect to Microsoft OneDrive Service - Network Connection Issue: Timeout was reached on handle 5AFAA16E4710

ERROR: Microsoft OneDrive API returned an error with the following message:
  Error Message:       Timeout was reached on handle 5AFAA16E4710
  Calling Function:    testInternetReachability()



Unable to reach the Microsoft OneDrive API service at this point in time, re-trying network tests based on applicable intervals

this is the output with curl

curl -I --connect-timeout 5 --max-time 5 https://login.microsoftonline.com --ipv4
curl: (28) Connection timed out after 5003 milliseconds

Also increasing the timeout (tested up to 300) I have the same result.
opening https://login.microsoftonline.com with web browser works perfectly.

Here my system info:

System:
Host: hostname Kernel: 6.8.0-86-generic arch: x86_64 bits: 64
compiler: gcc v: 13.3.0 clocksource: tsc
Desktop: Cinnamon v: 6.4.8 tk: GTK v: 3.24.41 wm: Muffin v: 6.4.1 vt: 7
dm: LightDM v: 1.30.0 Distro: Linux Mint 22.2 Zara base: Ubuntu 24.04 noble

[abraunegg]

@vfandrea

Your cURL/libcurl version (8.5.0) has known HTTP/2 bugs that impact the use of this client.
...
Ubuntu 24.04 noble

This is your root issue.

Your base distribution (Ubuntu) provides a broken curl version ...

Options to resolve

1. Change your Linux Mint version to Linux Mint Debian Edition 6 or 7 and use 'backports' to update 'curl' to a much more modern version
2. Use a better distribution that is not based on Ubuntu such as Fedora, Manjaro, Arch, OpenSuSE, Gentoo, FreeBSD
3. Upgrade 'curl' yourself as per How to upgrade of 'curl' package on Debian and Ubuntu systems to fix HTTP/2 bugs #2997

You potentially also have a DNS resolution issue and/or a firewall issue. This I cannot help you solve.

Fix your 'curl' version first

[vfandrea]

@abraunegg
Thank you for your answer.

I have successfully updated curl

curl --version 
curl 8.14.1 (x86_64-pc-linux-gnu) libcurl/8.14.1 OpenSSL/3.0.13 libpsl/0.21.2 nghttp2/1.59.0
Release-Date: 2025-06-04
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp ws wss
Features: alt-svc AsynchDNS HSTS HTTP2 HTTPS-proxy IPv6 Largefile NTLM PSL SSL threadsafe TLS-SRP UnixSockets

But I still have the same problem.

There should not be any DNS issue

nslookup login.microsoftonline.com
Server:		172.31.202.254
Address:	172.31.202.254#53

Non-authoritative answer:
login.microsoftonline.com	canonical name = login.mso.msidentity.com.
login.mso.msidentity.com	canonical name = ak.privatelink.msidentity.com.
ak.privatelink.msidentity.com	canonical name = www.tm.a.prd.aadg.trafficmanager.net.
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 6.6.0.3
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 2603:1027:1:28::c
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 2603:1027:1:28::23
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 2603:1027:1:28::25
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 2603:1027:1:28::20
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 2603:1027:1:28::5
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 2603:1027:1:28::11
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 2603:1027:1:28::7
Name:	www.tm.a.prd.aadg.trafficmanager.net
Address: 2603:1027:1:28::4

Also the firewall is disabled

[abraunegg]

@vfandrea
Firstly, please learn to use 3 x backticks for code output.

Secondly, does your 'browser' require a 'proxy' server to gain access? If yes, then has this been configured for your user at a terminal level?

Lastly, Ubuntu & Linux Mint use AppArmor. You need to investigate your platform now for AppArmor issues:

sudo aa-status
sudo journalctl -k | grep -i apparmor
# or
sudo dmesg | grep -i "apparmor=\"DENIED\""

When AppArmor is denying access you may see deny events for:

• Read to resolver files blocked:

  • /etc/resolv.conf (or the systemd-resolved stub /run/systemd/resolve/stub-resolv.conf)
  • /etc/nsswitch.conf, /etc/hosts

• Access to glibc NSS modules blocked:

  • /lib/x86_64-linux-gnu/libnss_dns.so.2
  • /lib/x86_64-linux-gnu/libnss_files.so.2
  • Network socket use denied (network inet, network inet6).

If you are seeing anything like this, you can try to put the 'onedrive' binary into AppArmor complain mode:

sudo aa-complain /path/to/onedrive_binary

This should then allow the application to operate.

All of this essentially points to a local environment issue. This is not a bug or issue with the client. Please seek further support from your distribution support channels.

[abraunegg]

@vfandrea

I suspect you 100% have a local environment issue going on

Clean Install, testing access via curl

Checking any apparmor issues

Running the 'onedrive' client with updated 'curl' version

Conclusion

My advice is for you to seek support now from your distribution for your issue

In a default state, there is no blocking of the 'onedrive' process and/or its network access for DNS or accessing the respective online platforms.