Safenetwork.io doesn't have https

I just noticed that maidsafe.org now goes to https://safenetforum.org, but if you go straight to https://safenetwork.io, nothing shows up. It seems that you forgot to get a certificate for the landing site, I know it’s not that big of a deal, but you should get one for it anyways. :wink:

I’m getting redirected to safenetforum.org immediately from safenetwork.io so no problem over here :smiley:.

1 Like

I get:

Firefox can’t establish a connection to the server at safenetwork.io.

I’ll notify @frabrunelle then :smiley:

1 Like

http://www.safenetwork.io or http://safenetwork.io should work fine. But if you put https instead of http, it won’t work because the SSL certificate I bought can only work on 1 subdomain (in this case, safenetforum.org).

I can always get a wildcard SSL certificate that supports multiple subdomain later. Or should I get it now?

In any case, there is no point in accessing safenetwork.io directly at this point because it’s not ready yet. Please participate in the next safenetwork.io weekly meeting if you would like to talk about what safenetwork.io should look like.

2 Likes

Any reason you don’t want to use Cloudflare’s free service? It includes free SSL.

Or the mozilla service once it launches

https://letsencrypt.org/

1 Like

True, except…

So I would much rather have end-to-end encryption between safenetforum.org and DiscourseHosting.

Discourse recommends to “go to namecheap or some other SSL cert provider and purchase a SSL cert” and that’s exactly what I did.

It’s also what DiscourseHosting recommended I do when I asked them:

Hi Francis,

I think it’s the most easy to do it as follows:

  • make sure safenetforum.org points to your forum’s IP (107.170.46.8)
  • buy the cert and send the cert and the key for us
  • we’ll install it and take care of the migration from there

PositiveSSL will be fine.

So now the only thing I need to do is purchase a wildcard certificate at some point in the future.

1 Like

Yup, I agree about the Full SSL issue. But the immediate issue is about redirection from the homepage to the forums. I don’t think you need full SSL for a simple redirect :smile:

1 Like

I just read from a user in the maidsafe subreddit that apparently chrome thinks the new site safenetforum.org is compromised.

At least in chromium I couldn’t reproduce the error, but I think this is something that should be looked into.

No problems here with Chrome Version 41.0.2272.89 m

2 Likes

You could, but it might be more cost-efficient to just buy another certificate for safenetwork.io instead of getting a wildcard cert. It depends on if you want to have more something.safenetwork.io addresses or not.

1 Like

Yes, wildcards are quite dear if you just want one more subdomain.

I have a few sites on cloudflare and though it looks good at first site it has many issues.

I was really hoping that they would be a good solution but unfortunately that is not the case. Their site and APIs are often down. And their free SSL is, as @frabrunelle pointed out, lacking. Which means it’s a false sense of security.

Just get a wildcard cert and done…

https://safenetwork.io gives a website not available response.

You are doing a redirect from http://safenetwork.io/ to https://safenetforum.org/

Why can’t you do a redirect from https://safenetwork.io/ to https://safenetforum.org/ also? That seems a bit more professional than allowing an error.

1 Like

this is now resolved: https://safenetwork.io and https://www.safenetwork.io are successfully redirecting to https://safenetforum.org.

sorry for taking so long. I had no experience with cloudflare but I was able to slowly figure it out.

thank you @eblanshey for your helpful suggestion :smiley:

I also started using cloudflare ssl for some of my other sites!

5 Likes