Certificate issues

[jordankrueger]

Is there something I need to configure in Cloudron to fix the cert issue here?

Certificate error when I add a link – and then try and go to the new link – in Kutt:

Your connection is not private

Attackers might be trying to steal your information from mydomain.nu (for example, passwords, messages, or credit cards). Learn more

NET::ERR_CERT_COMMON_NAME_INVALID

This server could not prove that it is mydomain.nu; its security certificate is from get.forkful.app. This may be caused by a misconfiguration or an attacker intercepting your connection.

Proceed to mydomain.nu (unsafe)

[girish]

@jordankrueger do you get this certificate issue on the domain in which kutt was installed? If so, do you see the cert error in other apps as well?

If maybe this is related to custom domain inside kutt , then you have to add an Alias in Cloudron . See https://docs.cloudron.io/apps/kutt/#custom-domains

[jordankrueger]

@girish said in Certificate issues:

@jordankrueger do you get this certificate issue on the domain in which kutt was installed? If so, do you see the cert error in other apps as well?

No. I only see this issue when attempting to utilize the link we've added in Kutt for the custom domain we've purchased for short links.

We set up the domain in the Kutt settings and then also set up the domain in our domain provider's DNS settings.

[girish]

@jordankrueger said in Certificate issues:

We set up the domain in the Kutt settings and then also set up the domain in our domain provider's DNS settings.

You have to add it in Cloudron as well. If Cloudron doesn't know about the custom domain, then it won't set up the reverse proxy accordingly. You have to add the custom domain that you added in kutt as an Domain Alias (see doc link above).

[jordankrueger]

@girish said in Certificate issues:

You have to add it in Cloudron as well. If Cloudron doesn't know about the custom domain, then it won't set up the reverse proxy accordingly. You have to add the custom domain that you added in kutt as an Domain Alias (see doc link above).

So sorry, but I'm still a bit confused.

In the screenshot provided for "domain aliases," the aliases are subdomains of the main Cloudron domain – eg site2.cloudron.club or *.sites.cloudron.club

If Cloudron is installed at my.domain.com and the custom domain I'm using with Kutt is dmn.net, what I'm a putting in the alias box?

Like, even in the screenshot provided for Kutt, it suggests you can use example.com/shortURL, but in the Cloudron docs there's not an example of using example.com in any of the boxes.

[girish]

Those screenshots are not ideal clearly Will fix them during our next review of those.

If Cloudron is installed at my.domain.com and the custom domain I'm using with Kutt is dmn.net, what I'm a putting in the alias box?

You have to put dmn.net into the aliases. Note that, for this, first you have to add the domain into Cloudron in the Domains View. This will help Cloudron get a cert and also set up nginx properly after you add it to the aliases.

Does that help?

[jordankrueger]

This post is deleted!

[jordankrueger]

okay! Once I added it to the Domins & Certs screen, and then went back into Kutt's Cloudron App Settings > Locations and then configured the alias for the shortlink domain (no subdomain in the box) it worked! Thank you!