Replying to Avatar Vitor Pamplona

If you are using the following relays, beware that many clients will not connect, upload or download data from them. Amethyst Push Notifications will also not connect to them.

- wss://relay.orangepill.dev certificate has expired

- wss://ca.relayable.org certificate has expired

- wss://nostr.btcmp.com certificate has expired

- wss://nostr.delo.software certificate has expired

- wss://nostr.drss.io Hostname/IP does not match certificate's altnames: Host: nostr.drss.io. is not in the cert's altnames: DNS:nostr.io, DNS:www.nostr.io

- wss://nostr.libreleaf.com certificate has expired

- wss://nostr.mikedilger.com Hostname/IP does not match certificate's altnames: Host: nostr.mikedilger.com. is not in the cert's altnames: DNS:chorus.mikedilger.com

- wss://nostr.onsats.org Hostname/IP does not match certificate's altnames: Host: nostr.onsats.org. is not in the cert's altnames: DNS:onsats.org

- wss://nostr.openordex.org certificate has expired

- wss://nostr.orangepill.dev certificate has expired

- wss://nostr.plebchain.org certificate has expired

- wss://nostr.unknown.place self-signed certificate

- wss://nostr.walletofsatoshi.com certificate has expired

- wss://nostr.zaprite.io Hostname/IP does not match certificate's altnames: Host: nostr.zaprite.io. is not in the cert's altnames: DNS:examplewalk.com, DNS:www.examplewalk.com

- wss://nostr.zebedee.cloud Hostname/IP does not match certificate's altnames: Host: nostr.zebedee.cloud. is not in the cert's altnames: DNS:names-hub.com, DNS:www.names-hub.com

- wss://private.red.gn.net certificate has expired

- wss://relay.nostr.ro certificate has expired

- wss://relay.orangepill.dev certificate has expired

- wss://relayable.org certificate has expired

I just assumed that some of these were no longer maintained, but maybe they'll work without SSL?

Reply to this note

Please Login to reply.

Discussion

No they won't work. The wss bit means it must be a secured socket connection the same way that https requires a secured connection or it will fail.

It has to fail. If the socket can't be encrypted because the encryption certificate isn't correct, you can't just default to having no encryption and continue working because that's more convenient.

what if we specify the same domains with ws⋮// ?

Nope, because wss and ws listen on different ports the same way that http and https listen on different ports 80 and 443 respectively.

Someone would need to have intentionally setup a relay that wasn't encrypted so that anyone using the relay would have their IP address and other details available for the entire world to track.

The only way you can use a non secured socket 'ws' is with a TOR encrypted tunnel which means the socket is still encrypted anyway.