I'm running into some difficulty getting my SSL cert to work with an Overcast server, wondering if I can get some more info on how to fix.
- I have my domain from godaddy
- Bought a cert for the matching domain
- Set up overcast with second/third level domains
- Associated the dns with the correct nameservers
- Followed either of the guides below to do a csr, submit to godaddy, then generate the jks from the cert
- Upload jks to server and restart
No matter what I do I keep getting "This site can’t be reached" when going to domain:8443. Everything works for domain:8080/admin/ but I can't seem to get any errors or logs telling me what is going on with the cert.
http://docs2x.smartfoxserver.com/Gettin ... yptography
http://docs2x.smartfoxserver.com/Gettin ... eb-sockets
Unable to get SSL running with Overcast
-
- Posts: 7
- Joined: 19 Apr 2021, 15:30
Re: Unable to get SSL running with Overcast
Hi SilverMonkey,
for these sort of issues we prefer to help via email, so that personal info/data is not shared on the forums.
I'd recommend to send us a message to our support@... email box with a reference to this discussion.
In the mail please specify the address and domain name of the server you're having problem with, so we can go and take a look.
Also, have you tried to connect to the server using the public IP address, such as https://<public-IP>:8443
Naturally, if you do so, you'll get a browser warning saying that there's no certificate (as the SSL cert is matched to the domain name, not the ip addr.) but still it would confirm whether or not a connection can be established.
We'll wait for your email.
Cheers
for these sort of issues we prefer to help via email, so that personal info/data is not shared on the forums.
I'd recommend to send us a message to our support@... email box with a reference to this discussion.
In the mail please specify the address and domain name of the server you're having problem with, so we can go and take a look.
Also, have you tried to connect to the server using the public IP address, such as https://<public-IP>:8443
Naturally, if you do so, you'll get a browser warning saying that there's no certificate (as the SSL cert is matched to the domain name, not the ip addr.) but still it would confirm whether or not a connection can be established.
We'll wait for your email.
Cheers
Who is online
Users browsing this forum: Bing [Bot] and 139 guests