search

carlonluca / docker-mldonkey

Project to build a docker image containing the mldonkey service.
GNU General Public License v3.0
11 stars 3 forks source link

mldonkey-next gui doesn't connect to the core when accessing through a reverse proxy #11

Open luke-70it opened 1 week ago

luke-70it commented 1 week ago

Hi, I've just found your version of mldonkey, and i'm very interested in a modern responsive web gui. I've stopped my previous container (logicwar/mldonkey) and I deployed yours, using same ports and added new ones specific for your version. From my LAN it works flawless both using old gui (port 4080) and "next" gui (port 4081).

To connect from Internet, I use Swag container as reverse proxy. It listen on port 443 for a specific FQDN and translate to internal ip on port 4081. In this scenario I can't connect to mldonley-next gui, but only to old gui.

4002 port is exposed, but something is missing in my configuration to make it works in a reverse proxy environment.

Can you help me to solve this problem?

Thank you! Luca

carlonluca commented 1 week ago

Using a proxy for the new GUI should be no different from doing it for the old GUI. If the webapp is not downloaded, you'll probably want to check the logs of your reverse proxy first. Please note that the webapp will also need to connect to port 4002 to communicate with the mldonkey core.

luke-70it commented 1 week ago

Is 4002 port accessed using http protocol? If i add to reverse proxy configuration for the same server_name a section for port 4002 and try to connect to http://server_name:4002 i see the text "upgrade required" Is this the expected behaviour? Telnet to port 4002 worked even before this nginx configuration, but new gui still can't connect to core. If i expose 4081 port an bypass reverse proxy it works, but i prefer https connection on 443 port.

carlonluca commented 5 days ago

4002 is used for the WebSocket server. WebSocket is somehow compatible with HTTP and may be used with a reverse proxy, however this is not something I tried.

So I guess you know can download the new GUI through the reverse proxy. If you see the "can't connect to core" error, it means you still need to make the WebSocket server available somehow.

raulfg3 commented 1 day ago

002 is used for the WebSocket server. WebSocket is somehow compatible with HTTP and may be used with a reverse proxy, however this is not something I tried.

So I guess you know can download the new GUI through the reverse proxy. If you see the "can't connect to core" error, it means you still need to make the WebSocket server available somehow.

sorry but I do not know how make webSocket server available, I use option in NPM image but Do not work as expected, perhaps you can test NPM, is a docker really easy to install: https://hub.docker.com/r/jc21/nginx-proxy-manager

on github: https://github.com/NginxProxyManager/nginx-proxy-manager

As I say previosly , I can reverse proxy mldonkey, but not mldonkey-next , allways show "not connected to the core" that is the main problem