Bad Certificate when using HTTPS

[Couto]

After setting up my own domain on your instance, I get a bad certificate message since the domains don't match, whenever I try to visit my homepage.

Is this something temporary while you use Let's Encrypt to generate the certificate for my custom domain, or is this a problem?

[Couto]

After some tests, this happens with any link when visiting with https. I thought the service would always redirect http:// to https:// but apparently not.

So any URL like: https://customdoma.in/something will trigger this error since the certificate belongs to kutt.it and not the custom domain itself.

[poeti8]

Yes it currently doesn't handle HTTPS, but it's on my list to add it soon.

[martijnckx]

Do you have an estimate of when this will be implemented?

[poeti8]

I finished refactoring and I'm adding features one by one now, could take couple months. Until then, you can email me ([email protected]) and I can add cert for domains manually.

[w4rner]

Another pre-requisite to use the product is that it supports https. Google is slamming non-https.

[k-allika]

I finished refactoring and I'm adding features one by one now, could take couple months. Until then, you can email me ([email protected]) and I can add cert for domains manually.

Sounds great! Looking forward to it.

In the meanwhile, may I request HTTPS support for my domain. I emailed you the information.

[w4rner]

what if you get free SSL in Cloudflare, can it work with https automatically?

[murka]

what if you get free SSL in Cloudflare, can it work with https automatically?

@w4rner, yep, if you enable proxy, it will work.