<n​ull:unsilence.net> i'm running my own node with ssl which is terminated at the reverse proxy in front of it. i'm pretty sure it's configured correctly since i'm running various other services with ssl configured, but the monero gui client doesn't seem to be able to connect to it. i think it's not correctly using ssl because the reverse proxy can't use the sni (server name indication) to route the tr<clipped message>

<n​ull:unsilence.net> affic. is there something i need to enable to to use ssl with a remote node from the gui client or does it not support it?

<j​effro256:monero.social> Monero Support

<n​ull:unsilence.net> i dunno if you're directing me to that room but i get 403 when i try to join. in any case this seems like a fairly developer-level question. does the monero gui client support ssl or not?

<n​ull:unsilence.net> found this discussion monero-project/monero #7089

<o​frnxmr:xmr.mx> Does `node.sethforprivacy.com:443` work for you in GUI?

<o​frnxmr:xmr.mx> ∅ sent you an invite to monero-support

<n​ull:unsilence.net> image.png

<n​ull:unsilence.net> Thanks, but I still get 403 ☹️

<o​frnxmr:xmr.mx> please hold

<o​frnxmr:xmr.mx> In the meantime, is your node reachable at `domain.com:port/get_info`

<n​ull:unsilence.net> it does, that's enough info for me to know it's some issue with my node setup. thanks!!

<n​ull:unsilence.net> no, i believe requests aren't getting routed correctly in the reverse proxy due to not have sni info set in the ssl/tls handshake. i'll try terminating ssl in the node itself

<n​ull:unsilence.net> well, i got it working after some messing with my routing rules. thanks for the help 🙂

<o​frnxmr:xmr.mx> Cheers