Closed orderorder closed 2 months ago
If the regular UI is working properly, I'd check the logs with docker logs.
docker logs mldonkey
/usr/lib/python2.7/dist-packages/supervisor/options.py:461: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2024-06-30 16:35:35,368 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2024-06-30 16:35:35,369 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing Unlinking stale socket /var/run/supervisor.sock 2024-06-30 16:35:35,688 INFO RPC interface 'supervisor' initialized 2024-06-30 16:35:35,688 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2024-06-30 16:35:35,688 INFO supervisord started with pid 8 2024-06-30 16:35:36,690 INFO spawned: 'mldonkey-next' with pid 11 2024-06-30 16:35:36,692 INFO spawned: 'mldonkey' with pid 12 WebSocket server listening on port: 4002 HTTP server listening on: http://localhost:4081 2024-06-30 16:35:38,003 INFO success: mldonkey-next entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2024-06-30 16:35:38,004 INFO success: mldonkey entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
This seems correct. I see no connection attempt though. What value is assigned to the key gui_port in downloads.ini?
gui_port = 4001
What logs do you see if you try to load the page?
You'll also need to expose port 4002. That is the port used by the websocket server.
Thanks, now it works. Thanks for this solution to bring mldonkey to modern systems. I like the new interface (mldonkey-next). In my opinion, you should update the information on how to run and install the application with the ports configured, because it is an interesting project and users who are not familiar with Dockers, like me, may have problems running mldokey this way. Anyway I hope my problem with the configuration helps other people.
Yes, I agree some info is missing. I'll add some more. Thanks.
I added more info about the installation in the docker image repo. If you feel something is still missing, feel free to open an issue.
I am a beginner in installing through Docker, I searched for tutorials on the web and followed these steps. The classic web interface over port 4080 works fine, but the new interface over port 4081 says "Not connected to the core" and login doesn't work.
sudo systemctl enable docker sudo systmeclt start docker
sudo groupadd docker
sudo usermod -aG docker ${USER}
docker pull carlonluca/mldonkey
docker create --name mldonkey --restart=always \ -p 4080:4080 -p 4081:4081 -p 4000:4000 -p 4001:4001 \ -p 20562:20562 -p 20566:20566/udp -p 16965:16965/udp \ -v "/media/data:/var/lib/mldonkey" \ carlonluca/mldonkey
docker start mldonkey