[Bug] JDownloader does not start anymore - Synthetica license outdatet

[Tom-Furrer]

Current Behavior

If you try to start the docker container an error message appears if you try to access it through IP:5800

Expected Behavior

JDownloader starts without error message working fine as some days before.

Steps To Reproduce

Restart docker container - even the newest re-downloaded Version 24.01.1

Environment

• OS: Synology docker
• Version 24.01.1

This container worked fine until a few days ago, seems to be outdatet since April 2024?

Container creation

.

Container log

There is no information about Synthetica license in the log files.

Container inspect

.

Anything else?

[Tom-Furrer]

I found a workround for this issue: in https://github.com/jlesage/docker-jdownloader-2/issues/191#issuecomment-1902548719

1) Stop the container 2) Go to your jd2-config folder an delete the file Core.jar and the folder tmp and update 3) Start the container and wait for the last update to finish 4) I had to reconnect my instance with my jD-Account once, because it lost it's connection.

. 2) I have deleted the Core.jar file and the entire \tmp and \update -folder and theyr content outside the container. They all will be recreated automatically 3) You can watch the update progress with IP:5800, this takes about a minute or so 4) On the running JD2 in IP:5800 in your Browser, go to Settings -> My.JDownloader and re-enter your mail-address and password previously used to connect your MyJDownloader-Browser addon to your local docker container (via the My.JDownloader.org redirector service).

[adocampo]

Thank you @Tom-Furrer !! It worked! On a first glance, it seemed to fail, as the same error about Synthetica license appeared, but I accepted every popup, and after a while with a black screen, jdownloader began to update and after a second black screen during a while, it finally opened! :)

[PEGARifrouf]

Hello @Tom-Furrer it works too for me, after stoping the container, I have deleted the impacted file ans folders with DSM file interface from the container mapped folder. Started again, service was online 2 minutes later.

So more an issue about an update in jdownloader source.

Thanks

[hulleyrob]

Apparently according to the guys who wrote jdownlaoder its cause by

"COPY --from=jd2 /defaults/JDownloader.jar /defaults/JDownloader.jar" github.com/jlesage/docker-jdownloader-2/blob/master/Dockerfile The JDownloader.jar file is replaced by outdated/incompatible file and old JDownloader.jar is not compatible with current version. Any JDownloader.jar file can be used for installation/initial setup, but after update it may not be replaced by older/other version.

so it might actually be able to be fixed here.

[jlesage]

The "default" JDownloader.jar is used/copied only on new installs, i.e. the first time you start the container. On existing install, it is not replaced, unless someone manually removes it from /config. https://github.com/jlesage/docker-jdownloader-2/blob/51c60e71d66959221cf976641892566bc30c7f9d/rootfs/etc/cont-init.d/55-jdownloader2.sh#L10

[hulleyrob]

Hmm thats weird then, as I also had the snytheica message last week and had to delete the usual files after pressing the update button in the app.