Call to download server failed (HTTP error code: 403).

The installer for a compiled (using R2015b) app, that has been distributed to many customers for several years, is suddenly (noticed in last couple of days) throwing the above exception. This has happened from multiple sites, domestic and international. The installer is set up to download the MCR from MathWorks.

Is anyone aware of any MathWorks, Windows (10, 11) updates that might be causing this?

Thanks! It's a bit urgent!!

[Yongtao Liu]

Did you solve this problem?

[Walter Roberson]

I wonder if this is related to TLS1.2 support? Did you specifically build the executable with the appropriate java.opts file?

https://www.mathworks.com/matlabcentral/answers/401291-using-tlsv1-2-with-webread#answer_321261

https://www.mathworks.com/matlabcentral/answers/2022232-http-error-code-12029-when-trying-to-install-compiled-app#answer_1312182

[Dave Watson]

Yongtao, not yet. MathWorks are looking into the issue.

Walter, thank you for the comment. I will check that but the build hasn't changed in three years - it just stopped working one day a couple of weeks ago.

UPDATE I tried adding the java.opts file to my startup folder. ML sees it but there is no improvement. Good idea, though, thanks.

[Parker]

Hi all, I am having the same problem with an App compiled with 2015b. Have not resolved the issue yet, so I'm following along here as well.

[Dave Watson]

Parker, MathWorks are investigating this. Will keep you inflormed as I am. The story, so far, is that it's likely not you/us. Thanks for adding your name.

[Dave Watson]

Received this update from MathWorks support yesterday: "I have received an update from the devs that the issue has been successfully reproduced (yay!), now they are now in the process of fixing it. I will keep you posted on this issue."

[Parker]

Great News Dave. Thanks for the update! Happy they've been able to dig into it. I'm distributing a standalone installation as a work around for now, but sounds like this will be back relatively soon.

[Dave Watson]

Parker, here's a temporary work-around from MW. It's not the best for our offsite customers but it's a big help for internal users.

Assuming you are using Windows 10,11, add an environment variable MW_INTERNAL_INSTALL_AGENT_URL to your system and set the value to http://ssd.mathworks.com/supportfiles/downloads/R2015b/deployment_files/R2015b/installagent/win64/InstallAgent_R2015b_win64_installer.zip

I tried this and it works. They are still looking at a permanent fix. Hope that helps.

If you are using Linux they provided instructions for that too which I can forward.

[Parker]

Awesome, thanks for relaying the workaround, Dave. Most of us are on Windows 10 or 11 so this should be workable

[Dave Watson]

Received just now from The MW:

"Good news, the developers have announced that the issue has been fixed, you no longer need the environment variable and should be able to run your compiled installer again.

So, please try deleting the environment variable and running the installer to see if you still encounter the same issue."

2025.01.30 I tried installing our compiled app (the one that asks for a download of the MCR if not alreay installed) and it worked fine after deleting the env variable. Seems we're back in business.

Answer 1

[Olivier]

I encounter the same error with an application built with matlab R2019a...

I recompile the application with R2023b and there is no problem with this version.

[Dave Watson]

Thanks, did this just start happening? We believe it started sometime after 11/26?