SSL not working on Serverpilot

ssl

#1

Hi everyone,

Anyone had this issue?

I have a SSL certificate (not from Cloudflare) installed on my server. I’m using Serverpilot.

Cloudflare support tells me the server isn’t accepting HTTPS. I checked, and port 443 is open by default on Serverpilot.

What’s going on here?


#2

If you :grey: (bypass) cloudflare on the DNS page, does your site work?

It’s possible your SSL certificate expired. What does it say on your Domain’s SSL page at Serverpilot? It’s been a while since I’ve used that Serverpilot feature, but it did get broken from time to time when behind Cloudflare.


#3

sdayman, whether I bypass it or not, https never works (http always does).

My SSL is valid until Oct. 2018.

I’m on Serverpilot’s free plan, so nothing shows up there. I installed the SSL certificate via PuTTy. It’s a Comodo SSL. I asked them and they tell me it’s active.

I have no clue what’s going on.

BTW, here’s a screenshot that shows port 443 is listening.

2018-05-01_18-35-15


#4

Serverpilot’s Free Plan doesn’t support SSL…unless you jump through a bunch of hoops and manually set it up.

So…your firewall is open but it doesn’t necessarily mean your server is listening on 443.

Plus, if you bypass Cloudflare and your server’s not responding to HTTPS, then it’s an issue on your server’s end.


#5

That makes sense, the issue could be on the server.

Cloudflare already has port 443 open by default: https://serverpilot.io/community/articles/firewall-rules.html

How do I manually open port 443/HTTPS via PuTTy? I’m not sure if that’s the issue but I’m willing to give it a try.


#6

You’re going to have to leave Serverpilot alone (unless you’re into serious server tweaking) and set Cloudflare’s SSL to Flexible. This way, your visitors can use HTTPS, but your server can still use HTTP.


#7

It’s a shame because I have a valid SSL and have to resort to Flexible. Chrome shows that the connection isn’t entirely safe.

I don’t know what the heck to do with this. I’ll have to quit. Cloudlfare didn’t help and Serverpilot “we don’t offer SSL support on the free plan”.


#8

Sometimes the connection isn’t “entirely safe” due to a mixed content issue:


#9

I have some images that are still in HTTP, but it doesn’t explain why the whole site in HTTPS doesn’t work. I may have to go to shared hosting again.


#10

Mixed content kills the SSL security rating. What’s the domain?


#11


(BTW it shows both error 521 and error 502 one after the other)


#12

Earlier, you said if you bypass, your site still wouldn’t work with HTTPS, but HTTP was ok.

Do you now have SSL set to Flexible?

You also said you still had images still in HTTP. Right now, nothing works, so how were you seeing images in HTTP?


#13

Wether I bypass it or not, only HTTP works. It doesn’t matter if in the DNS tab I choose DNS only or DNS and HTTP (CDN). Only the http works.

I’m using Full (Strict) in the Crypto tab for SSL.

Images in the HTTP website show up ok for me. Is the HTTP version of joaoalexandre.com down for you?


#14

Don’t use Full. Without Serverpilot’s SSL support, you need to set it to Flexible.

Ok, the HTTP version works. So “Flexible” should be a good start for getting SSL working for you.


#15

:confused:

Right.

That defeats the purpose of having my own SSL though :slight_smile:


#16

Yes, but Free Serverpilot isn’t set up for any SSL. Bummer, but that’s how they configure it.


#17

Hmm are you sure? You can install a Let’s Encrypt certificate in Serverpilot even with the free plan.

That also didn’t work for me though.


#18

That’s the bunch of hoops I referred to earlier. And since it didn’t work for you, you, you’ll have to go with Flexible SSL. Or dig in and do some troubleshooting to get that SSL script to work


#19

This topic was automatically closed after 14 days. New replies are no longer allowed.