Open griefer05 opened 8 months ago
jlesage
commented
8 months ago Updates from JDownloader itself often fix these kind of problem. If restarting the container never fixes the issue, you could try this: https://support.jdownloader.org/Knowledgebase/Article/View/fix-jdownloader-installation/
elbim
commented
7 months ago jlesages hint fixed the issue. Stop the container Go to your jd2-config folder an delete the file Core.jar and the folder tmp and update Start the container and wait for the last update to finish I had to reconnect my instance with my jD-Account once, because it lost it's connection.
rusterboy77
commented
7 months ago jlesages hint fixed the issue. Stop the container Go to your jd2-config folder an delete the file Core.jar and the folder tmp and update Start the container and wait for the last update to finish I had to reconnect my instance with my jD-Account once, because it lost it's connection.
I had the same issue and I couldnt fix with this solution. I' ve tried twice but still saying "no connected JDownloader found". I can connect via myIP:5800 but not with my JDownloader Dashboard or apk.
DaStivi
commented
6 months ago
Current Behavior
First I started the Docker Container. Then I connectet to it via VNC and Chrome and on both the following was shown.
So I pressed "OK" in the "Synthetics License Warning" Box because it was the only thing I could press besides the "X"
Then I was able to press the "Error details" button on the "Exception occured" box and it showed me the following.
After that I pressed the "OK" button and the following popped up, so I pressed the "Close" button the "JDownloader Updater" Box and again was only now able to interact with the box.
On that I pressed the "Error details" button and the following massage was shown.
After that I pressen on the "OK" button and then there was only black. Shortly after that the Docker Container stopped.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Container creation
Container log
Container inspect
No response
Anything else?
Context: I had to shut down my Synology NAS and then the Container didn't work anymore, I didn't know I just had to update the image and restart the Container, so I deleted the old Container and tried to create a new one using the now updated image but then I ran into these problems.