STM32CubeIDE is not connecting to the internet.

[ADaxa.1]

I had several versions of the IDE installed on my machine but none of them could connect to the internet to update or load code. I keep getting the error message "In order to benefit from best experience a network connection is required. Do you want to set connection parameter now?". At first I thought it was because Norton was blocking the the applications through the firewall but I uninstalled Norton and installed the IDE again but that didn't fix the problem. I installed the IDE on my brothers machine which doesn't have Norton and it worked fine on there. I also have used different networks in the past 2 months so that cant be it. Can anyone please help?

[Clyde_S]

I had the same problem and solved it by changing Active Provider to Direct.

[skink91]

I am having a connection issue from my new company laptop, and no settings seem to work for me (same problem in both CubeMx and CubeIde). I should also note that I have NO problems working off the same (home) network from my personal PC.

I looked in the CubeIde .log file and found the following java exception, but not sure if it means that I have an issue or ST has a certificate issue.  The log contained this:

ENTRY org.eclipse.equinox.p2.transport.ecf 4 1002 2024-09-20 10:35:42.036
!MESSAGE Unable to read repository at https://sw-center.st.com/stm32cubeide/updatesite1/content.xml.
!STACK 0
javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:378)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:321)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:316)
at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(CertificateMessage.java:1351)
at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.onConsumeCertificate(CertificateMessage.java:1226)
at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.consume(CertificateMessage.java:1169)
at java.base/sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:396)
at java.base/sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:480)
at java.base/sun.security.ssl.SSLEngineImpl$DelegatedTask$DelegatedAction.run(SSLEngineImpl.java:1277)
at java.base/sun.security.ssl.SSLEngineImpl$DelegatedTask$DelegatedAction.run(SSLEngineImpl.java:1264)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:712)
at java.base/sun.security.ssl.SSLEngineImpl$DelegatedTask.run(SSLEngineImpl.java:1209)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.net.http/jdk.internal.net.http.common.SSLFlowDelegate.lambda$executeTasks$3(SSLFlowDelegate.java:1118)
at java.net.http/jdk.internal.net.http.HttpClientImpl$DelegatingExecutor.execute(HttpClientImpl.java:157)
at java.net.http/jdk.internal.net.http.common.SSLFlowDelegate.executeTasks(SSLFlowDelegate.java:1113)
at java.net.http/jdk.internal.net.http.common.SSLFlowDelegate.doHandshake(SSLFlowDelegate.java:1079)
at java.net.http/jdk.internal.net.http.common.SSLFlowDelegate$Reader.processData(SSLFlowDelegate.java:484)
at java.net.http/jdk.internal.net.http.common.SSLFlowDelegate$Reader$ReaderDownstreamPusher.run(SSLFlowDelegate.java:268)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$LockingRestartableTask.run(SequentialScheduler.java:205)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:149)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:230)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:439)
at java.base/sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:306)
at java.base/sun.security.validator.Validator.validate(Validator.java:264)
at java.base/sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:285)
at java.base/sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:144)
at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(CertificateMessage.java:1329)
... 21 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at java.base/sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:148)
at java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:129)
at java.base/java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297)
at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:434)
... 26 more

[sg1312]

Hello, I am also experiencing issue trying to connect to the Internet(version 1.16 of the CubeIDE on Windows11). I tried all suggested actions but without success. I also tried using an Internet cable which allows connection to Internet from the IDE on other PC - which should eliminate the possibility to have incorrect internet/proxy settings on mine. From the ide.log , when trying to login I get: UserAuth:417 - Internet connection configuration mode: 2

[KHe.1]

I would like to give an update on this. 

First of all, the main issue that I had is my company's firewall policy blocks STM32CubeIDE accessing to the websites. As soon as our IT whitelisted:

.st.com/
.eclipse.org/
It took care the majority of the issue. Then I just need to change the Active Provider in Network Connections to "Direct" as other people mentioned here. 

However, before our IT whitelisted the websites, I had been doing a way around it, which is changing the "Connection Mode" in "Preference->Firmware Updater" to "Off Line Mode" and downloading the firmware package needed from the ST website manually. 

Then save it to 

C:\Users\<your username>\STM32Cube\Repository

Then unzip and change the folder name to match the format like the other firmware packages in the repository. 

I also run into missing "crdb.zip" issue during the process. I basically just download it myself from ST website too. And save it to:

C:\ST\STM32CubeIDE_<version#>\STM32CubeIDE\plugins\com.st.stm32cube.common.mx_<version#>\resources

No need to unzip.

[TarunKumaar]

If you don't mind, could you share how you manually install the firmware packages, is it just the stm32 and patch zip file that you need to add to the repository and everything works fine??

[KHe.1]

Yes, to do the "Off Line Mode", you just need to download the firmware from ST.com, unzip, and rename the unzipped folder to match their naming format. Then when you create a new STM32 project, the software should find it and start installing and create the project. 

To download, go to https://www.st.com/en/embedded-software/stm32cube-mcu-mpu-packages/products.html Find the chip family of yours and download the version you need. 

Save the firmware to here: C:\Users\<your username>\STM32Cube\Repository. You can find your exact firmware location in your STM32CubeIDE "Firmware Updater" too: 

To unzip and rename: 
In the screenshot, you can see below are the zip files downloaded from ST. Above are the unzipped folders. Make the folder name like "STM32Cube_FW_<chip family>_V<version number>"

When unzip, make sure the folder structure is correct, like this: 

At this step, it is possible that every case is a little different.

Sometimes you may need to install some older versions in order to install the latest version. For example, when I tried to install F4_V1.28.1, I had to install V1.28.0 first, because V1.28.1 is a patch to V1.28.0.

Or the naming format maybe different in other chip family. If you have an older version already existed in the repository folder, you can use its naming format as a reference. For me, I had V1.27.1 already installed by the software a long time ago, so I know that format is what the software looks for and I changed the new firmware folder format to match that. 

I would suggest you read their revision document and try a few ones to find the one that works. And you may take a few tries. 

When it works, the STM32Cube software should start installing the firmware package when you create a new STM32 project. If you still see errors about code generation like picture below, that means something is still not setup correctly with your firmware folder, and the software doesn't recognize / couldn't find the offline firmware package you put there.