@baris Thank you for your help.

Hi, I tried to drag to the appropriate position in the widgets but it failed, this is what I did:https://drive.google.com/file/d/1NNzf2x2_0RsmB7ELMHTJxmJmzZ0N70LR/view?usp=drive_link
May I ask why I can't add it to that page?

@julian
Hi, just now after you switched to CloudFlare the problem no longer occurs, but as far as I can see, now that you have switched the resolution to your source site again, your source site has a normal SSL configuration in an IPV4 environment, but not in an IPV6 environment.

debian@mail:~$ curl -vI https://packages.nodebb.org
*   Trying [2604:a880:cad:d0::4d4:e001]:443...
* Connected to packages.nodebb.org (2604:a880:cad:d0::4d4:e001) port 443 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=otherhome.ca
*  start date: Sep 30 11:40:17 2024 GMT
*  expire date: Dec 29 11:40:16 2024 GMT
*  subjectAltName does not match packages.nodebb.org
* SSL: no alternative certificate subject name matches target host name 'packages.nodebb.org'
* Closing connection 0
* TLSv1.3 (OUT), TLS alert, close notify (256):
curl: (60) SSL: no alternative certificate subject name matches target host name 'packages.nodebb.org'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Please fix this issue as soon as possible.
THX
: )

@julian
https://***.org/confirm/98f65230-0d29-4175-a596-fe9d17d
I've also tested the status of this feature in my community, and it's also not working.

I found that my NodeBB deployment had the problem that users could not modify the mailbox, I tested the user's mailbox modification function, and the results were consistent with my own deployment, and the replacement could not be confirmed by the URL sent to the mailbox. This should be a bug.