FileBot

Posted: **21 Nov 2025, 18:59**

Hi,

I'm having an issue with the Java Installer package on my Synology NAS when it tries to auto-update Java. The package is the one from your repository (FileBot / get.filebot.net), installed via Synology Package Center.

Environment:
- Device: Synology NAS
- OS: DSM 7.x (fully updated)
- Package: Java Installer (from rednoah repository)
- Java update mode: AUTO UPDATE via Package Center (Repair / Reinstall)

Problem:
When I click "Repair" (or when Java Installer tries to update itself), the process fails. The package ends up in a "Repair" state again and cannot complete the installation.

So Filebot can’t work anymore.

Here is the relevant log from `/volume1/@appstore/java-installer/install-java.log`:

Code: Select all

cmp: EOF on /volume1/@appstore/java-installer/get-java.sh.asc which is empty
Fri Nov 21 15:41:51 CET 2025: AUTO UPDATE
gpgv: Signature made Mon Feb  3 08:58:27 2025 CET
gpgv:                using RSA key 27B74F30D08404D1CCA0AF848A17D093B565EAD7
gpgv: Good signature from "imnks.com <[email protected]>"
Download https://ghproxy.cn/https://github.com/adoptium/temurin23-binaries/releases/download/jdk-23.0.2%2B7/OpenJDK23U-jdk_x64_linux_hotspot_23.0.2_7.tar.gz
curl: (6) Could not resolve host: ghproxy.cfd
curl: (6) Could not resolve host: ghproxy.cfd
curl: (6) Could not resolve host: ghproxy.cfd
curl: (6) Could not resolve host: ghproxy.cfd
curl: (6) Could not resolve host: ghproxy.cfd
curl: (6) Could not resolve host: ghproxy.cfd
OpenJDK23U-jdk_x64_linux_hotspot_23.0.2_7.tar.gz: No such file or directory
Expected SHA256 checksum: 870ac8c05c6fe563e7a3878a47d0234b83c050e83651d2c47e8b822ec74512dd
Actual SHA256 checksum: 
ERROR: SHA256 checksum mismatch
removed 'bin/java'
removed directory 'bin'
rm: cannot remove 'include': No such file or directory
rm: cannot remove 'jmods': No such file or directory
rm: cannot remove 'lib': No such file or directory
rm: cannot remove 'conf': No such file or directory
rm: cannot remove 'legal': No such file or directory
rm: cannot remove 'man': No such file or directory
tar (child): *.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

Posted: **22 Nov 2025, 03:53**

Where did you get your Synology Java installer (23) package from? The console output suggests that you're using a package made by some Chinese guy, which is highly concerning if you are working under the assumption that you're using trusted code published by the FileBot team? The official java-installer code notably would be (1) signed by us and (2) not download files via ghproxy.cn and (3) install OpenJDK 21 at the time of writing.

https://get.filebot.net/syno/ is our package repository. You seem to have added a different package from a different package source that uses the same name. You seem to have installed software for the https://spk7.imnks.com/ package repository, which seems to have java-installer packages that are based on our official package but with modifications for users in China.

See Currently having an issue with the Synology Java installer (23) on Synology DSM 7.2.2-72806 Update 5 for additional details.

Posted: **22 Nov 2025, 04:44**

Omg.

The DSM Package Center is confusing. It shows that the package was developed by “rednoah” at install time, even though that’s not the case at all.

I don’t remember why I had this Synopackage.com source configured.

It looks like DSM is mixing their Java Installer with yours.

I removed the Synopackage source and the problem is solved.

Thanks! I didn’t think the two sources could be combined like that on the same package. I thought it would create one package per source, since it’s clearly not the same repository.

Everything is resolved now, thanks again.

Posted: **22 Nov 2025, 04:58**

I see, so https://synopackage.com/repository/spk/All combines many different package sources (including that Chinese one) and then you end up with duplicate packages. Each package source can provide arbitrary metadata for their packages (reuse existing package IDs, use "rednoah" as author, etc) so only add package sources that you trust.

That said, the 870ac8c05c6fe563e7a3878a47d0234b83c050e83651d2c47e8b822ec74512dd hash is correct for OpenJDK23U-jdk_x64_linux_hotspot_23.0.2_7.tar.gz so I guess it's legit at this point in time. The package description (in Chinese) does say that it's modified to install OpenJDK 23 and make that work from inside of China. Presumably, due to the GFW, downloads from GitHub are either blocked or slow, so I guess there's a GitHub mirror inside China that makes things work and work fast by caching things inside China, but also break things when you're not actually in China.

FileBot

[Synology] Java Installer fails to update: ghproxy.cfd DNS error (curl: Could not resolve host)

[Synology] Java Installer fails to update: ghproxy.cfd DNS error (curl: Could not resolve host)

Re: [Synology] Java Installer fails to update: ghproxy.cfd DNS error (curl: Could not resolve host)

Re: [Synology] Java Installer fails to update: ghproxy.cfd DNS error (curl: Could not resolve host)

Re: [Synology] Java Installer fails to update: ghproxy.cfd DNS error (curl: Could not resolve host)