Support

I am a bit confused about your description of what is going on. You said “If I make a backup now, the upload does not work. When I make a backup now Akeeba uploads this to Onedrive”. So, which one is it? Can you or can you not upload to OneDrive?

If you can upload to OneDrive its credentials will stay put and your problem cannot possibly occur.

If you CAN NOT upload to OneDrive there is a set of conditions where repeated failures would indeed make your OneDrive credentials be removed from the configuration.

If the authentication to OneDrive works BUT uploading to it through Akeeba Backup doesn't the problem is most likely a firewall or proxy your host put between your server ("server" here can mean a physical or virtual machine) and the Internet. We've seen many cases where a firewall was blocking all outbound access from the server or a misconfigured caching proxy was returning misleading information, ignoring the fact that it should never cache the results of POST and PUT requests per the standard.

You might wonder why setting up OneDrive would work in this case. It happens entirely through your browser. No information is sent from your server to the outside world or vice versa.

Moreover, you might see that the very first backups – taken within 3600 seconds of authorising OneDrive – work but subsequent backups fail. This has to do with how OneDrive works. When you authenticate you get an access token valid for 3600 seconds and a refresh token. When the access token expires your server needs to contact our server (www.akeeba.com) which acts as a mediator between your site and OneDrive for the purposes of authentication as detailed in the documentation. If that connection fails due to a server firewall / proxy, or you have not entered your Download ID, or the Download ID is invalid, or the Download ID is for an expired subscription then the renewal of the access token with the refresh token fails. Therefore the upload fails. After three retries the refresh token is considered invalid and removed from your configuration.

However, before passing judgement I need you to a. tell me if you can or cannot upload to OneDrive after setting up its connection in the Configuration page and b. ZIP and attach the backup log file from this first backup attempt and the next backup attempt. The two backup attempts need to be at least one hour apart for me to draw any useful conclusions.

First of all, I see that you are using the OneDrive legacy option. Please do not use that. This is an old version of the API which is no longer maintained and might fail. Try with the "Upload to Microsoft OneDrive or Microsoft OneDrive for Business" which is the new API version.

If the credentials keep disappearing after the first backup I will need you to ZIP and attach the log file of the backup you perceive as successful but results in the credentials disappearing.

Sorry, I do not see how your backup upload could have possibly worked given the log file I am seeing here. Trying to start the multipart upload fails repeatedly and Akeeba Backup reports that it will not remove the non-processed (therefore: not uploaded) file. In fact, this is why your authentication tokens disappear. If the upload fails repeatedly – even after refreshing the tokens – we assume that your setup is wrong and we remove your connection information. There's a good reason behind this. We don't want you to consume our server resources to refresh the OneDrive tokens for a backup that is doomed to fail.

Looking at your log file I see something troubling. When we try to start the multipart upload we do NOT receive a valid result from OneDrive. We receive the value "1" which has no meaning and cannot come from OneDrive. It also comes too fast. Way too fast. As if the request never made it to OneDrive, really.

Based on our experience we know what this means: your host is running a caching proxy server in front of your web server, catching all outbound requests and returning cached results for them. However, the Internet standards (RFCs) expressly state that caching proxies MUST NOT cache PUT and POST requests like the ones we are sending to OneDrive. In a nutshell, the problem happens because your host has misconfigured their server.

You need to contact your host. Show them my reply here so they have an idea what to look for. Please note that you will most definitely have to escalate your issue past their first level support. First level support would neither know if they are running a caching proxy nor what its configuration is. You will need to talk to one of their network engineers to resolve this.