BLYNK
HOME       📲 GETTING STARTED       📗 DOCS       ❓HELP CENTER       👉 SKETCH BUILDER

Letsencrypt auto generation fail in Version 0.41.14 but it works in 0.41.13

I recently upgraded my blynk local server to 0.41.14, and then I needed to change the domaim name, so I removed the old certificate files and tried to get the blynk server to generate new certificates on its own, but it never worked, the message is as follows:

   Loaded: loaded (/etc/systemd/system/blynkserver.service; disabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-12-14 10:46:09 CST; 2min 18s ago
 Main PID: 6865 (java)
    Tasks: 24 (limit: 2182)
   CGroup: /system.slice/blynkserver.service
           └─6865 /usr/bin/java -jar /mnt/dietpi_userdata/blynk/blynkserver.jar

Dec 14 10:46:43 PisgahIotServer java[6865]:         at cc.blynk.server.acme.AcmeClient.requestCertificate(AcmeClient.java:66)
Dec 14 10:46:43 PisgahIotServer java[6865]:         at cc.blynk.server.SslContextHolder.regenerate(SslContextHolder.java:91)
Dec 14 10:46:43 PisgahIotServer java[6865]:         at cc.blynk.server.SslContextHolder.generateInitialCertificates(SslContextHolder.java
:108)
Dec 14 10:46:43 PisgahIotServer java[6865]:         at cc.blynk.server.launcher.ServerLauncher.start(ServerLauncher.java:114)
Dec 14 10:46:43 PisgahIotServer java[6865]:         at cc.blynk.server.launcher.ServerLauncher.main(ServerLauncher.java:73)
Dec 14 10:46:43 PisgahIotServer java[6865]: Caused by: java.lang.ClassNotFoundException: org.bouncycastle.asn1.isara.IsaraObjectIdentifie
rs
Dec 14 10:46:43 PisgahIotServer java[6865]:         at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java
:581)
Dec 14 10:46:43 PisgahIotServer java[6865]:         at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.j
ava:178)
Dec 14 10:46:43 PisgahIotServer java[6865]:         at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
Dec 14 10:46:43 PisgahIotServer java[6865]:         ... 9 more

Later I downgraded the server version back to 0.41.13, it successfully generated new credentials, report the problem here