85

Add HTTPS support for custom domains.

HTTPS support (allow uploading certificates for custom domains)

58 comments

  • 2
    Avatar
    Jay Stansell

    After 2 years I cannot believe this is still an open issue. 

    The cloudflare support article has been killed. "Happiness Officer" told me it's because cloudflare had a security bug. I found that ironic. We are talking about our customers entering credit card details on an unsecure, on a strikingly hosted site.

     

     

  • 0
    Avatar
    Brad Grier

    Me either Jay. It's beyond frustrating. I'm about to launch another sire and doubt I will on strikingly because of this. They did help me setup with Cloudflare and didn't know about this security bug. 

  • 0
    Avatar
    Aleksandra Jezewski

    So... i'm discovering that it seems there's no chance i get a certificate through Strikingly. It was so obvious to me that there was no question to get one easily from a hosting service where the site creation is so easy and where i can build a shop site... Well, i'll use the trial period to re-build my site somewhere else...

  • 1
    Avatar
    Sean Young


    This issue is becoming acute. Clients have started asking,"why do visitors get this Security warning page??!?". I may not have any choice but to begin migration of sites away from Strikingly if this is not handled with urgency.

    Here is a Jan 2017 article on Google's latest move to shame the internet into full SSL compliance. It appears to be working.

    https://nakedsecurity.sophos.com/2016/09/09/google-to-slap-warnings-on-non-https-sites/

    My clients are forwarding me stuff like this:


     

     

     

     

  • 0
    Avatar
    Roopesh Shenoy

    yes please, a customer here, and we're looking to move to full SSL as well. We have our domain name from before we used strikingly - so we'd love to get https for that as well. 

    It's big enough for us to leave strikingly if that's the only way we can do https.

    Thanks.

  • 1
    Avatar
    Javy

    Same here. Please provide a solution to this issue. Otherwise, we will be forced to move as well.

  • 1
    Avatar
    Brad Grier

    For what it's worth, Strikingly helped me set SSL up with Cloudflare after some trail and error of me doing it myself. I've got the lock symbol and the secure site. A hassle but it's done. I agree this needs to be done in house if Strikingly wants to grow. 

    Secondly, it would be nice if someone from Strikingly would respond in this forum. It's the right thing to do for the customers that are threatening to leave. 

  • 1
    Avatar
    Ray

    Hi,

    Same here, https is really needed.

    Best regards,

    Ray

     

  • 0
    Avatar
    Tim

    Can you use the SSL for SaaS solution to allow secure CNAME?

  • 0
    Avatar
    Mark

    We have just really started selling on our site and I was alarmed to see this is not in place.

    We currently use you for six sites and will have to migrate away if not solved.

    Can you please issue an update...

  • 0
    Avatar
    Patrick Kosiol

    We have the same need.

    Paid or free (via Letsencrypt), somehow Strikingly needs to allow us to serve HTTPS. Otherwise, this service will have a really hard time to survive as most websites hosted here will get down-ranked by Google. Besides the fact that our customers are running away because the site is not secure.

    Please address this Strikingly team.

  • 1
    Avatar
    Dave Weatherall

    Hey, any update on this from the Strikingly team?

    I am a big fan of Strikingly but this has been disappointing. I would like some clarity.

    Are you working on a solution coming soon?

    If not, what else can we do? For example, do something with Cloudflare? At the very least, switch our domain/s to you guys (not ideal but I guess it might work)...

  • 0
    Avatar
    Raf

    Need this ! Pleaaaassseeee

  • 0
    Avatar
    Martin Akerman

    We need this too

  • 0
    Avatar
    Joarley de Moraes

    No update on this ? :(

  • 0
    Avatar
    Tim

    This is solvable with Cloudflare SSL for CNAME, which is what we need.

    It is hurting to not have SSL for our custom domain names, and the solution is available.  Can we just execute on this?

  • 0
    Avatar
    Patrick Kosiol

    @Tim: so that means, we need to buy an additional service just because Strikingly is not able to implement a standard HTTPS service with 3rd party issued certificates? It's not rocket science folks!

  • 0
    Avatar
    Patrick Kosiol

    Just FYI in regards to Cloudflare:

    "Also, we used to offer CloudFlare for domains registered outside Strikingly. But due to a recent security bug encountered by CloudFlare, we stopped offering it."

    So even that is not possible anymore. 

  • 0
    Avatar
    David Stamp

    Has this been resolved for Strikingly hosted sites now/

  • 1
    Avatar
    Happiness Officer

    We have a beta program for SSL, David. Send me the domain that you want to setup with SSL and I'll add you in! 

  • 0
    Avatar
    Tommy Berretz

    By activating SSL, is there a noticeable difference in website load times? Is it slowing it down?

     

  • 1
    Avatar
    Happiness Officer

    Hi, Tommy! There shouldn't be. But since we're still on beta program, we're continually improving the experience. Would you like to try it out?

  • 0
    Avatar
    Tommy Berretz

    Yes, I would like to give it a shot. What do you I need to do to get started? And, if for whatever reason I need to reverse it, can I? 

  • 0
    Avatar
    Happiness Officer

    Hi, Tommy! We'll reach out to your via email :) 

  • 0
    Avatar
    Jonathan

    THANK YOU!

  • 0
    Avatar
    Brad Grier

    What do you recommend for people who set the free SSL through Cloudfare? I would like to integrate inside Strikingly if possible. 

  • 0
    Avatar
    Happiness Officer

    Hello, Brad! If you have SSL via CloudFlare, we can also move you to our beta program. You can chat with us here or send your domain via email here. We can help you figure it out. 

    And @Jonathan, you're welcome! 

  • 0
    Avatar
    Dylan Robertson
    • The https:/domain.com pattern won't connect. 
    • Even your CEO's website isn't accessible via this combination: try accessing https://haishachen.com - it doesn't work...

    I created a thread about this issue here.

Please sign in to leave a comment.