Support

Remember that you downgraded to a version that was working for you but it's no longer working for you. This is proof enough that whatever your problem is it is not related to our code, but something that recently changed in your hosting environment. If it was a change in our code, downgrading would've solved it.

Without a backup log file I can speculate all day about the nature of the problem, but I would just be stabbing in the dark. Maybe your host's PHP is linked against a libcurl which does not support TLSv1.2 which is now required by Microsoft. Maybe you have not entered your Download ID correctly, or at all, which means that anything you use that requires refreshing OAuth2 credentials will eventually fail once the initial access token expires. Maybe it's something else. That's why we always ask you to ZIP and attach the backup log file (the short message you left at the top of your issue). The log file will give us more context.

Statements of fact and an offer to help you beyond what you have paid us to do are indeed an "attitude": a positive one. That's in stark contrast with your abrasive and toxic demeanour throughout this interaction.

In an IT context "upgrade" means installing a newer version than the one currently installed. Its antonym, "downgrade", means installing an older version than the one currently installed.

The fact remains that you did install the older version which was working for you in the past. In fact, you did so in a perfect way: completely uninstalling the newer version, forcing a clean installation of the last known good version. I am happy that you did that, because it proves the point. Even though you installed the last known good to you version, it no longer works. This is a data point: neither the old (9.9.6), nor the new (9.9.10) version work for you now when in the past the older version did.

Before replying to you I installed a new test site with Joomla! 4.4 on PHP 8.1. I installed Akeeba Backup 9.9.6 on it, configured OneDrive, and found that the upload works perfectly. I already have a test site with Joomla! 5.2 on PHP 8.3 with Akeeba Backup 9.9.10 on it, and a backup profile configured with OneDrive. I ran the backup on that site and found it to be working just fine. This is another data point: both the old (9.9.6) and the new (9.9.10) versions work perfectly fine on two different, known good server environments – if you wonder, one is a commercial Rochen server, the other is an Ubuntu Server I set up myself, and they are on completely different networks and hosting infrastructure (AWS and Linode respectively), thereby proving that I don't have a magical environment where everything works.

The combination of the two data points objectively means that the problem comes from something outside our code. This is either a server environment issue, or a hosting environment issue. I cannot know which one it is since they are completely outside our control and I have no information about them.

As I told you, I need the backup log file to help you. You insist you attached it, but it's nowhere to be found. Whether an attachment is present in a ticket or not is objective reality which does not leave room for subjective interpretation. This is a public ticket. Anyone can come to our site and check your posts for an attachment. The objective reality is that there is no attachment.

You claim to have used an "email form". I could assume that you mean the ticket submission form, but I'll take it one step further. The only kind of form on our site which could be even remotely described as an "email form" is our Contact Us form. All submissions to this form are logged into the database, in case email delivery fails. You have not submitted the Contact Us form either. This is also a statement of objective fact.

Therefore, the objective reality is that I do not have your log file. You can claim whatever you want, but the objective and independently verifiable fact remains that I DO NOT have your log file.

Telling me that statements of objective fact are an "attitude" is thoroughly unproductive. I need your log file to narrow down the root cause of your issue. As I very clearly stated in my previous reply, I do have several of the usual suspects in mind. The log file would help me deduce what is actually happening.

Side note: As per our Terms of Service, I am not obliged in any way to help you beyond stating that the problem has to do with your server environment since this was proven by none other than you. I am going beyond what I am supposed to help you with because I bloody care about our clients! If you call that an "attitude" then, by God, it is an attitude alright!

Will you send me the log file so I can help you?