Support

I can see that the line being referenced in the error message has been removed since February 4th, 2016. There's no way that you were restoring a backup taken with Akeeba Backup 7.1.3, a version 4 years newer than the removal of that line. It doesn't even look like an SSL issue. It looks like your server or your browser were caching files from a very, very long time ago OR you first tried to restore a backup taken with a version that's more than 4 years old.

I am a software engineer. I don't make allegations. I make observations based on facts and the information you provided. None of the information you provided supports your claim that this was an SSL issue. It only proves that the problem is that your browser somehow ended up executing a file from at least 4 years ago. That's the statement – NOT allegation – I made. The rest of my reply was a quick note on how it could have possibly happened but I think you are missing some context. I apologize for not providing it previously. Please let me explain what I did to come up with my previous reply and provide the missing context.

The error message you volunteered states there's an unknown call to a jQuery method .modal() on line 97 of the file databases.js. The only file with that name in the ANGIE restoration script lives in installation/angie/js/database.js and its line 97 currently reads

databaseThrottle     = Math.max(databaseThrottle, 60000);

Therefore your error message does not reference a current version of that file, as shipped with Akeeba Backup 7.1.3.

I also known for a fact that I removed jQuery modals a long time ago, when I switched ANGIE from Bootstrap 2 and jQuery to Akeeba FEF and plain vanilla JavaScript. I know that as the developer who first wrote this backup software almost 14 years ago and has been maintaining it as an active lead developer ever since :)

At this point it was clear to me that your assertion that this is an SSL issue is at the very least inaccurate.

My next step was trying to determine when was the last time the line referenced in the error message had content which could conceivably trigger that error. I went to our private GitHub repository and started looking at older versions of the file until I found when line 97 contained a call to .modal(). I saw that the line first got removed by yours truly on February 23rd, 2016 at 09:45 EEST. The oldest commit we have with that line in place is from February 4th, 2016 at 17:13 EEST when we moved the ANGIE installer from the Akeeba Backup repository to its own repository. No public release of Akeeba Backup was made between these two dates. Therefore we can safely conclude that the code referenced by your error message is older than February 4th, 2016 at 17:13 EEST.

Claiming that an SSL issue can somehow cause a 4 year old file which does not ship with Akeeba Backup 7.1.3 be delivered to your browser and fixing the SSL issue would conversely make the up-to-date code to be delivered is extremely unlikely but not outright impossible. That's why I said that if this is indeed what is going on it must be some really odd caching issue. It is very unlikely because of the temporal distance between the two file versions: more than 4 years.

I can NOT tell you within any degree of certainty why your browser loaded a version of the file that's 4 years old and why fixing the SSL fixed that problem for you. I can think of possible reasons but I cannot KNOW.

Trying to restore a backup from a long time ago earlier on that domain using the same browser is a plausible reason. Do not that this doesn't necessarily mean that you took a backup of the site 4 years ago. Many template developers ship quick start packages of Joomla and their template as backup archives taken with Akeeba Backup. That was the implied context of restoration of an old backup.

Another possibility is that the broken SSL issue somehow caused your server to respond with file belonging to a different site which happened to have an ANGIE installation script from 4 years ago. That's insanely unlikely but not outright impossible. That's why I talked about an odd caching issue.

Again, I can NOT know exactly WHY you were served an ancient file in your browser. All I can tell you with absolute certainty is that the error message is caused because your browser was trying to execute an old version of the file from at least 4 years ago and that this version of the file is not shipped with Akeeba Backup 7.1.3.

I hope that this clarifies what I wrote and you can see that I am not accusing you of lying. I am only saying that you are very likely misdiagnosing the issue, I can tell you what the real issue is but I cannot possibly tell you why it happens.