To follow-up on https://github.com/neuropoly/spinalcordtoolbox/pull/2814#issuecomment-669163684, the site spinalcordtoolbox.com shows "Parts of this page are note secure". As pointed out by @Drulex, it is possibly related to the forum badge which points to a domain (spinalcordmri.org) that doesn't use SSL.
How is spinalcordmri.org hosted? We can simply generate the SSL certificate and change the webserver config. I can help with that.
How is spinalcordmri.org hosted?
spinalcordmri.org redirects to https://spinalcordmri.github.io/, so it's a github page. Does that answer the question?
This page has some info (see step 8 particularly): https://docs.github.com/en/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site.
Let's see if this is enough (I don't think the ssl cert name will match the domain, but maybe github does some magic under the hood).
ok done-- i guess we have to wait a few hours now
As I suspected:
.
There are two options:
cname was setup since when visiting https://spinalcordmri.org the domain name stays the same instead of changing to spinalcordmri.github.io.spinalcordmri.org (matching the domain name).I couldn't find info about the second option, I think 1 is simpler.
does this look good?
on namecheap: i replaced cname by URL redirect:

on github: i removed the "custom domain"

it might take some time to take effect
ok, i think i screwed up, and now neither spinalcordmri.org nor our SCT forum http://forum.spinalcordmri.org/c/sct are available.
so yes, i wouldn't mind some help @Drulex. I'll send you the credentials to namecheap and will make you admin of the GH site.
After looking at how http://spinalcordmri.org is setup I understand why the above didn't work.
spinalcordmri.org is hosted by github pages at spinalcordmri.github.io. The domain spinalcordmri.org uses a cname entry to point at spinalcordmri.github.io. Apparently Github pages serves both SSL and non-SSL (can be accessed via https://)spinalcordmri.github.io is configured with custom domain via CNAME entry making it point to spinalcordmri.org.forum.spinalcordmri.org is hosted on a DigitalOcean droplet that is running the Discourse forum.In our case we are ok with the github pages server, but whatever is running the Discourse forum is not configured for SSL.
Any SSL-enabled website pointing to the forum will have the warning described in this issue. It is the case for the docs, but also for the main page of spinalcordmri.org: https://spinalcordmri.org/.
So basically the only thing we need to do is to serve the forum via https.
Certificate I got while visiting https://spinalcordmri.org/software/ :

It would also be a good idea to force only SSL connections, but as we saw earlier today that didn't work (https://github.com/neuropoly/spinalcordtoolbox/issues/2830#issuecomment-669462412) and github switched to serving with a different certificate..
@Drulex @jcohenadad I could configure the ssl certificate on the discourse forum as explained here. I just need to rerun ./discourse-setup
@jcohenadad Did you change the configuration in namescheap for spinalcordmri.org ? I cannot see the subdomain for the forum as it should be. Info here
@jcohenadad Did you change the configuration in namescheap for spinalcordmri.org ? I cannot see the subdomain for the forum as it should be. Info here
It's there, maybe you need to press "show more" because there are multiple entries.
@Drulex @jcohenadad I could configure the ssl certificate on the discourse forum as explained here. I just need to rerun
./discourse-setup
Sure if you feel comfortable doing it. At the moment the mapping of the forum domain to the correct IP isn't working for some reason. It think we should open a ticket with Namecheap as it's been like this since yesterday.
Agree, cause the configuration is correct.

The http://159.89.119.65/ seems to work correctly, it might be on the DNS side.
I'll open a ticket.
I'll open a ticket.
Ok, for context the record was changed yesterday pm and reverted to the original setting while experimenting.
so they told me to change the host to forum and remove the domain and keep the same value. I changed it we'll have to wait 30 min.
Here is the chat:
17:23 Lilia Semerenko: The thing is that the domain name itself should not be included to the Host field.
17:23 Lilia Semerenko: It means that you need to add only forum as a Host value. This is a system requirement.
17:24 Alexandru Foias: even if we want to have a subdomain forum.spinalcordmri.org?
17:25 Lilia Semerenko: Yes, you just add the subdomain itself to the host field without the domain name.
17:26 Alexandru Foias: okay, and how long does the update take to be propagated ?
17:27 Lilia Semerenko: Normally, the changes should take effect within 30 minutes.
working now 馃帀
I re ran the setup for discourse, now it should be secured. The only issue is the DNS that we still have to wait for.

It seems like now they create a chrome app from discourse which is cool. you can see on top at the address bar.
yay! working now. thanks @alexfoias !
hum, this guy is still unsecured:

Looking at the requests:

It's the mailing list badge img request that is unsecure: http://img.shields.io/badge/mailing%20list-development-green.svg?style=flat
Seems to be the last non-https request that the page makes.
Looking at the requests:
how do you do that?
It's the mailing list badge img request that is unsecure
maybe we could find badge from somewhere else, e.g. herokuapp. The weird thing is that other badges are using img.shield.io, e.g. https://img.shields.io/discourse/status?label=forum&server=http%3A%2F%2Fforum.spinalcordmri.org
if you replace the badge img with this seems to be secured
thanks @alexfoias ! let me try that
how do you do that?
On Firefox: Developer tools -> network monitor -> network request details.
https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor/request_details
It's similar if you are using chrome. I think you can press F12 -> Network.
yay!

closing because fixed
Most helpful comment