kutt
kutt copied to clipboard
thedevs-network
[custom domains] https shortlinks
@MohHeader probably not straight away, this is a tricky problem to solve.
Should we generate certs per custom domain? Should we allow user-uploaded certs? etc... Lots of difficult-to-tackle questions
--- Edit 2 : https://webmasters.stackexchange.com/questions/87163/do-bitly-branded-short-domains-support-https
--- Edit 1 : Bitly also supports custom certificates. If your company does not want to use LetsEncrypt and has it's own custom SSL certificate, please email your Customer Success Manager or [email protected] for more details.
https://support.bitly.com/hc/en-us/articles/231139148-How-do-I-enable-https-for-my-Branded-Short-Domain-bsd- That's how Bit.ly do it : Bitly has already secured SSL certificates for all branded domains through LetsEncrypt.
So the best available current solution is just to self-host Kutt ?
Alright, I guess we could do LE certs for custom domains. I can try to write a script for this that the app can call.
@poeti8 any ACME client preferences?
I was able to deploy kutt.it on heroku with custom domain at https://new.zgzg.link/ and HTTPS works fine.
This issue is for custom domains using the kutt.it instance, not custom instances
I was able to deploy kutt.it on heroku with custom domain at https://new.zgzg.link/ and HTTPS works fine.
can you please tell me how to setup https for the custom domain!
@RakeshDL I use heroku, I didn't do any thing specific other than just follow heroku domain name instruction. Please note this is a separate instance of kutt, not redirecting to http://kutt.it.
@xinbenlv Thanks, I found a solution, used Cloudflare SSL certificate to do it
For our deployment of Kutt I've placed Apache with mod_proxy in front of Kutt so it can handle all of the https communication. The only thing I need the ability to do is to have my custom domains return a link with https instead of http when creating new short urls.
I understand that most of the discussion in this thread is related to how the Kutt.it site will handle procuring and installing certs for custom domains but there is a much simpler use case for self hosted Kutt deployments where the administrators can handle certificate management outside of the application. We simply need to have our shortened links have https instead of http in the address.
Thanks!
@rharrison10 Added the option. You can check the "Use HTTPS" option in setting page:
@rharrison10 Added the option. You can check the "Use HTTPS" option in setting page:
@poeti8 This option is now visible on kutt.it too, which is a bit misguiding.
@poeti8 This option is now visible on kutt.it too, which is a bit misguiding.
I agree, I'll remove it soon.
Alright, I guess we could do LE certs for custom domains. I can try to write a script for this that the app can call.
@poeti8 any ACME client preferences?
This interests me in particular. Are there any plans to put this in place?
This interests me in particular. Are there any plans to put this in place?
Plans? Yes. Time to do so? Not sure so soon..
I hope really this feature will implemented in the future. It will give the custom domains feature a huge enhancement.
This would be very useful indeed. Remember, many people now use HTTPS Everywhere which will stop them in their tracks if they're visiting a kutt link.
Is this likely to be implemented? I no longer see that SSL option mentioned above for custom domains.
