After spending a lot of time with support, i was unable to find someone capable to understand the issue and what i was pointing to... 😞
(...bad support knowledge)
Just a bit astonished that this is not reported since the last www.paypal.com digital security certificate replacement due to expiration; looks like that current certificate does not have www.paypal.me as alternative DNA name and provide only support for paypal.me dns name, thus when the browser redirects the url request from paypal.me www.paypal.me or paypal.me/nickname to www.paypal.me/nickname the browser (any, Edge, Chrome, Firefox, or even FF through TOR) refuse to establish the encrypted https/ssl/tls connections and provide the following message (example from Firefox, incognito mode):
Requested host does not match any Subject Alternative Names (SANs) on TLS certificate [74b4d56ed2e06d02dd22c1d5a2d8e7d09190a081d03bca848020ad09d7a3e18c] in use with this connection.
Visit https://docs.fastly.com/en/guides/common-400-errors#error-421-misdirected-request for more information.
Funny that i have the feeling to be alone to try using paypal.me generated link, because otherwise it should have been already reported so far by many other users...
ANYWAY, I'VE FOUND A POSSIBLE WORKAROUND:
Instead of using the "standard and basic" url generated for paypal.me
https://www.paypal.me/nickname
Use instead this, by adding paypalme to the www.paypal.com url
https://www.paypal.com/paypalme/nickname
(...apologise for using this link, i was not aware that someone has registered "nickname" as a nickname 🙂 )
