Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[custom domains] https shortlinks #18

Open
kze opened this issue Feb 26, 2018 · 23 comments
Open

[custom domains] https shortlinks #18

kze opened this issue Feb 26, 2018 · 23 comments
Labels
enhancement New feature or request

Comments

@kze
Copy link

kze commented Feb 26, 2018

Just an feature request. Currently its only http but https would be nice.

@poeti8 poeti8 added the enhancement New feature or request label Feb 26, 2018
@poeti8
Copy link
Contributor

poeti8 commented Feb 26, 2018

Yep, I'll see what I can do.

@kze kze changed the title https shorlinks https shortlinks Feb 27, 2018
@muratdogan17
Copy link

I've tried and it looks it works pretty good for https link.

@kze
Copy link
Author

kze commented Apr 2, 2018

@muratdogan17 I don't think it works for custom domain.

@muratdogan17
Copy link

@kze oh, okay! I didn't get that you mean for custom domain 👍

@trgwii trgwii changed the title https shortlinks [custom domains] https shortlinks Apr 3, 2018
@MohHeader
Copy link

Can we expect anything soon ? :)

@trgwii
Copy link
Member

trgwii commented Jun 25, 2018

@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

@MohHeader
Copy link

MohHeader commented Jun 25, 2018

--- 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 ?

@trgwii
Copy link
Member

trgwii commented Jun 26, 2018

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?

@xinbenlv
Copy link

I was able to deploy kutt.it on heroku with custom domain at https://new.zgzg.link/ and HTTPS works fine.

@trgwii
Copy link
Member

trgwii commented Oct 18, 2018

This issue is for custom domains using the kutt.it instance, not custom instances

@rakcode
Copy link

rakcode commented Dec 21, 2018

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!

@xinbenlv
Copy link

@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.

@rakcode
Copy link

rakcode commented Dec 21, 2018

@xinbenlv Thanks, I found a solution, used Cloudflare SSL certificate to do it

@rharrison10
Copy link

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!

@poeti8
Copy link
Contributor

poeti8 commented Feb 2, 2019

@rharrison10 I will add an option this week.

@poeti8
Copy link
Contributor

poeti8 commented Feb 8, 2019

@rharrison10 Added the option. You can check the "Use HTTPS" option in setting page:

image

@aksh1618
Copy link

@rharrison10 Added the option. You can check the "Use HTTPS" option in setting page:

image

@poeti8 This option is now visible on kutt.it too, which is a bit misguiding.

@poeti8
Copy link
Contributor

poeti8 commented Jun 2, 2019

@poeti8 This option is now visible on kutt.it too, which is a bit misguiding.

I agree, I'll remove it soon.

@drewbaumann
Copy link

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?

@poeti8
Copy link
Contributor

poeti8 commented Oct 6, 2020

This interests me in particular. Are there any plans to put this in place?

Plans? Yes. Time to do so? Not sure so soon..

@nisutec
Copy link

nisutec commented Aug 11, 2021

I hope really this feature will implemented in the future. It will give the custom domains feature a huge enhancement.

@LeviSnoot
Copy link

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.

@RyanRoberts
Copy link

Is this likely to be implemented? I no longer see that SSL option mentioned above for custom domains.

dpevunov-cp pushed a commit to dpevunov-cp/kutt that referenced this issue Dec 5, 2024
…twork#18)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests