FileBot

rednoah wrote: ↑14 Dec 2025, 18:10 You could try to modify /var/packages/java-installer/target/get-java.sh and replace:

Shell: Select all

	curl -fsSL -o "$JDK_TAR_GZ" --retry 5 "$JDK_URL"

with:

Shell: Select all

	curl --insecure -fsSL -o "$JDK_TAR_GZ" --retry 5 "$JDK_URL"

Then restart the NAS to trigger the auto-update on start.

Linus wrote: ↑14 Dec 2025, 20:28 Thank you
Unfortunately, it didn't work out...

Linus wrote: ↑20 Dec 2025, 10:45 That's the curl output:

Console Output: Select all

~# curl -v -I 'https://download.bell-sw.com/java/21.0.9+11/bellsoft-jdk21.0.9+11-linux-arm32-vfp-hflt.tar.gz'
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: unable to get local issuer certificate
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

The gist of my previous post is that adding the --insecure option to the curl command will make curl ignore certificate errors. Your most recent post shows a curl command without the --insecure option, and also isn't the output of the (now modified as instructed above) /var/packages/java-installer/target/get-java.sh script as it is running and either succeeding or failing, after being triggered and run on reboot.


You'll want to modify the /var/packages/java-installer/target/get-java.sh script as instructed above, then reboot the NAS, then look at the log file.