[Loloncio]

Hi,
I am trying to activate the web server so I can connect to emule and manage my downloads from outside my network. I managed to make it work using HTTP but the moment I turn on HTTPS it simply does not work.
I checked with nmap (I also tried to connect with a browser) and when using HTTP it detects the server is running:

PORT STATE SERVICE VERSION
XXXX/tcp open http eMule P2P
But when I enable HTTPS it does not:
PORT STATE SERVICE VERSION
XXXX/tcp closed light

The port is open and I have a ddns with cloudflare. I tried connecting using both the domain name and public IP both work for HTTP but neither works for HTTPS. I also tried using certificates from cloudflare and from emule but they do not work. Finally, the port is open on windows firewall and my antivirus firewall.

This is the conffig from preferences.ini regarding WebServer:

[WebServer]
Password=XXXXXXXXXXXX
PasswordLow=XXXXXXXXXXXXXXX
Port=XXXX
WebUseUPnP=0
Enabled=1
UseGzip=1
PageRefreshTime=120
UseLowRightsUser=1
AllowAdminHiLevelFunc=1
WebTimeoutMins=5
UseHTTPS=1
HTTPSCertificate=XXXXX\cert.crt
HTTPSKey=XXXXX\cert.key
ShowUploadQueue=0
ShowUploadQueueBanned=0
ShowUploadQueueFriend=0
DownloadSortReverse=1
UploadSortReverse=1
QueueSortReverse=1
ServerSortReverse=1
SharedSortReverse=1
DownloadSort=2
UploadSort=3
QueueSort=3
ServerSort=1
SharedSort=2

Any ideas why this is not working?

[fox88]

Can you connect from the same computer where eMule is running? That is, with https: //localhost:XXXXX (whatever port it uses)?

[Loloncio]

fox88, on 09 March 2025 - 05:36 PM, said:

Can you connect from the same computer where eMule is running? That is, with https: //localhost:XXXXX (whatever port it uses)?

No, it does not work, only with http

[fox88]

You should be able to connect locally (at least, Community 0.60d and 0.70b can).
See what is in Log and Verbose log panes, what diagnostics browser gives. Maybe create new certificates.

[Loloncio]

fox88, on 09 March 2025 - 10:43 PM, said:

You should be able to connect locally (at least, Community 0.60d and 0.70b can).
See what is in Log and Verbose log panes, what diagnostics browser gives. Maybe create new certificates.

Ok, this is the output from Verbose log:
10/03/2025 12:07:18: Loaded certificate: e8 90 f8 a0 fd bd 7b 6e 39 cd 67 4a 53 64 b1 be 9d e1 b2 94
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:22: Web Interface handshake failed: SSL - An invalid SSL record was received
10/03/2025 12:07:24: Kad: Request flood detected for opcode 0x34 (0x34) from IP 50.58.238.130 - Dropping packets with this opcode

The Log just says that the server was started.

Seems to be a certificates problem, I tried 3 different ones, the one that I have from cloudflare, one created in eMule with the "Create New Certificate" button and finally a certificate I created with openssl like this:
openssl req -new -x509 -days 365 -nodes -out emule.crt -keyout emule.key
With the last one I at least get an error in the browser, first is the normal warning saying the site is not secure because the certificate is autosigned, I accept the risk and then it says "Secure connection failed. The page you are trying to view cannot be displayed because the authenticity of the data received could not be verified".

This post has been edited by Loloncio: 10 March 2025 - 12:03 PM

[fox88]

Would you please tell bitness and version for OS and eMule?

[Loloncio]

fox88, on 10 March 2025 - 08:41 PM, said:

Would you please tell bitness and version for OS and eMule?

I do not now what bitness is do you mean 32 or 64 bits? in that case it is 64 bits.

For OS I use Windows 10 Pro 22H2 and eMule is v0.70b.

If it is useful the PC specs are this:
CPU: Ryzen 7 5700U
RAM: 32GB DDR4
SSD NVME 500 GB
Integrated GPU
Conected with Ethernet.

I am not sure if I said it before but I tried disabling my firewall just in case but I get the same error.

[fox88]

There seems to be a regression in 32-bit eMule 0.70b.
32-bit 0.60d was doing well.
No such issue here (Intel) with 64-bit eMule with eMule-created certificate and with OpenSSL utility.

[Loloncio]

fox88, on 10 March 2025 - 10:43 PM, said:

There seems to be a regression in 32-bit eMule 0.70b.
32-bit 0.60d was doing well.
No such issue here (Intel) with 64-bit eMule with eMule-created certificate and with OpenSSL utility.

Ok, that was it, I changed to 0.60d and it works, thank you. I also tried 0.70b 64 bits and it does work.

Thank you so much!

By the way, is there a difference in performance or something between 32 and 64 bits eMule? I always used 32 bits because it is the default.

This post has been edited by Loloncio: 11 March 2025 - 06:12 PM

[fox88]

32-bit was the only option in the official.
Differences are not huge, and in any case, everything goes towards 64-bit.

Thanks for reportig the bug.