Problem renewing cert - using GoDaddy DNS

I am using Tableau on a Windows OS and the DNS provided by Godaddy . Certificate expired. How can I renew.. Please help. tableau.healthdataroof.io I got one cert from Cloudflare which is not getting binded to the domain, so, I had to come back here. Currently the site shows cloudflare cert which is not secure

I've moved your post to its' own topic.
Please take the time to provide us enough information to help you.


Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

4 Likes

I cant provide much information on how to install the LetsEncrypt cert in Tableau, but perhaps this can help you.

First: I recently posted a detailed writeup of how to get LetsEncrypt certificate files manually using CERTBOT. If that is of help for you to get updated certs, then please use it! (it is for a linux environment as I wrote it). Alternately, just use the manual certbot process (without scripts) to do the same - it desnt matter WHERE you run this from if you are doing DNS Authorization and can get the files from wherever you run the certbot command.
The goal in this first step is to get the certificate files (all will be .PEM files).

Second: using the Tableau documentation, install the certs.
This often trips people up because the documentation will ask for different file types/names based on other certificate processes.
Please try using the following information as a way to "convert" filenames from the Tableau instructions so you can use the LetsEncrypt files:

KEY - privkey.pem is the "key" file.

CRT - fullchain.pem is your "crt" file.

cert.pem - cert.pem contains ONLY your certificate 0 this is generally not used as is.

chain.pem - chain.pem is the intermediary signed authority, signed by the root authority

CRT/KEY Bundle
If you are asked for a "bundle" file, then you would need to create a bundle.pem using:
cat fullchain.pem privkey.pem > bundle.pem
... for a Windows environment, this simply means to put the contents of BOTH files in a single file.... you can even use Notepad to do this typically

This information was stolen by me from another post and edited used here.. :slight_smile:

Here SSL Checker
shows " Chain Issues: close The chain doesn't contain any intermediate certificates"
Also "Issuer Common Name ZeroSSL RSA Domain Secure Site CA"

And here Hardenize Report: tableau.healthdataroof.io
shows "Certificate chain is incorrect"

And SSL Server Test: tableau.healthdataroof.io (Powered by Qualys SSL Labs) shows
"Chain issues Incomplete" for both IPv4 Addresses

https://chainchecker.certifytheweb.com/ shows

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.