Error establishing SSL connection

any idea why firefox works and chrome doesnt?

alright trying to setup ssl now, when i use manual mode for certbot on domain and place the acme challenge i now get a connection fetch error :S

“connection refused”

Checking your raw ip -

Domainname Http-Status redirect Sec. G -2 3.624 V
ConnectFailure - Unable to connect to the remote server -2 3.626 V
ConnectFailure - Unable to connect to the remote server

Looks like a blocking firewall.

Same with the port 6060 -

oh server is down right now doing some stuff

okay managed to get cert etc from certbot now… started a https server listening on 5050 with the credentials, but when i try to connect with wss:// i get a timeout

Are you sure?

that server is not using a valid certificate

I don’t, I get HTTP/1.1 101 Switching Protocols

can you check if its valid now?

the cert should be issued to

note that these certs where generated by certbot and i moved them from my raspberry pi to my actual desktop for testing before i deploy the server on my raspberry hence the port change from 6060 to 5050

and my client is running with force https if thats of any importance

it is.

% curl --include \
     --no-buffer \
     --header "Connection: Upgrade" \
     --header "Upgrade: websocket" \
     --header "Host:" \
     --header "Origin:" \
     --header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==" \
     --header "Sec-WebSocket-Version: 13" \
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: qGEgH3En71di5rrssAZTmtRTyFk=

Warning: Binary output can mess up your terminal. Use "--output -" to tell 
Warning: curl to output it to your terminal anyway, or consider "--output 
Warning: <FILE>" to save to a file.
1 Like

so you have no issues going on with https now?

because im getting timeouts, both in chrome and firefox…

this is the error i get: connector.js:6 WebSocket connection to ‘wss://’ failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT

i can see in my server logs that one successfully managed to get userlist from server… And https is forced by my client host so https seems to work, no idea how that person managed to get it working though

okay im going insane, people on my world of warcraft guild can apperently access the site with https without any issue but I cant

had TWO separate ppl connect to it without issues and https working :S

is this because the server is running from the same IP that im trying to access it through?


THIS IS INSANITY, i have multiple guild members logging on without any problems, with HTTPS