SMTP notification test fails. "Lost connection to the socket server"

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn’t find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

When configuring SMTP notification all goes well until I want to perform a test of the connection. This results in the following text showing in a red bar:

Lost connection to the socket server. Reconnecting...

Sometimes (about one in three times) it will also show this after the first one:

Cannot connect to the socket server. [Error: websocket error] Reconnecting...

The notification modal will not progress after this, showing a infinite spinning “save” button:

It’s possible to close the modal with the ❌ at the right top, but when you reopen it, it’s still spinning. Refreshing the page let’s you try again.

Looking in the browser console I see:

Content Security Policy: This site (https://up.example.com) has a Report-Only policy without a report URI. CSP will not block and cannot report violations of this policy. 2
Content Security Policy: The page’s settings observed the loading of a resource at wss://up.example.com/socket.io/?EIO=4&transport=websocket (“default-src”). A CSP report is being sent. vendor.f2e417fe.js:55:57144

I see a similar issue mentioned in #143 so I checked the TLS versions of NodeJS and the server I’m connecting to. For NodeJS I see this uses openssl: '1.1.1m+quic'. This should support TLSv1.3. The mailserver is also offering a TLSv1.3 certificate.

👟 Reproduction steps

I’m not sure what steps were relevant for coming to this result, so I’ll be a bit broad:

• Install uptime Kuma via Yunohost
• create a few monitors
• create a notification based on SMTP
  • (I tried with both security options, and with “ignore TLS error” checked and unchecked.)
• Click test

👀 Expected behavior

A test email gets sent. Or a error is shown explaining what went wrong

😓 Actual Behavior

See description

🐻 Uptime-Kuma Version

1.11.3

💻 Operating System and Arch

Debian GNU/Linux 10 (buster)

🌐 Browser

96.0 (64-bit)

🐋 Docker Version

Unsure, I’m using Yunohost

🟩 NodeJS Version

‘16.14.0’

📝 Relevant log output

No response

[louislam]

Found this in Google: https://forum.yunohost.org/t/ghost-4-20-3-ynh1-broke-all-editing-fixed/17629

[github-actions[bot]]

This issue was closed because it has been stalled for 2 days with no activity.