Page 1 of 2

HTTPS enabled and forced for andorstrail.com

Posted: Wed Nov 19, 2014 11:12 pm
by sdevaney
Hello all,

For those that wish to use it you can now access the forums through a secured HTTPS connection by going to https://andorstrail.com

Re: HTTPS enabled for AT.com

Posted: Fri Dec 12, 2014 7:04 am
by Covenant
Muchly appreciated. Let me know if still want to take up my offer of paying for a year of SSL, I'd be happy to take a CSR from you and pay for Thawte to sign it. Keep in mind when it's up for renewal next year.

Re: HTTPS enabled for AT.com

Posted: Fri Dec 12, 2014 12:30 pm
by Zukero
Thanks Moerit.
By next year, mozilla and the EFF will have launched their "Let's encrypt " free CA, so I think we'll be using it.

Re: HTTPS enabled for AT.com

Posted: Mon Jun 06, 2016 2:34 pm
by rijackson741
I guess the obvious questions are:

Which domains are you keeping?
What is the other domain that you do not intend to renew, and what is happening to it?
Do you have any data on how many redirects currently come from andorstrail.net?

Re: HTTPS enabled for AT.com

Posted: Mon Jun 06, 2016 7:55 pm
by Melarec
Does this mean the forum is getting iced?
I am confuse...

Re: HTTPS enabled for AT.com

Posted: Mon Jun 06, 2016 8:42 pm
by rijackson741
The forum is at andorstrail.com. Andorstrail.net just redirects here, so getting rid of it might affect some peoples bookmarks, but that's all.

Re: HTTPS enabled for AT.com

Posted: Mon Jun 06, 2016 10:36 pm
by rijackson741
Now I'm confused :?

You have, and intend to keep, andorstrail.org. However, that redirects to andorstrail.com, so someone must have control of that.

The reason I asked is that maybe I'm willing to take control of the andorstrail.net domain, but only if there's a good reason to do so (and of course if the annual fees are not too high). That's why I asked about the number of redirects. If nobody is using it I don't see much of a need to keep it.

Re: HTTPS enabled for AT.com

Posted: Tue Jun 07, 2016 3:45 am
by Melarec
These comments have been very enlightening.
Thank you.

Re: HTTPS enabled for AT.com

Posted: Tue Jun 07, 2016 11:18 am
by Zukero
Just a quick note:

http://www.andorstrail.com and http://andorstrail.com are both the same thing.

Use https://www.andorstrail.com or https://andorstrail.com to get the secure version.
It stopped working at some point but it is back thanks to sdevaney.

The forum is not getting iced, or frozen, or killed or whatever so far. sdevaney supports it with his own money, and I am thankful that he keeps doing so. I also help in the administrative part of it.
There are no feature downgrades or anything in this regard either, phpBB is often upgraded to its latest version to help prevent security issues so there may be changes here and there (most notably, the theme changed a while back, due to phpBB's decision to change the theming engine to a more responsive design). I am not aware of any plans to change this situation, quite the contrary.

Indeed, the activity is slow these days, sometimes to the point where two weeks will pass without a post. I attribute this to the long (way too long) delay since the last update. I do keep working on Andor's Trail to the best of my ability, and try to keep up with the forums (spam cleanup, answers to questions I can answer, so typically, I avoid all "gaming help" posts because I'm not a good player, nor do I know all the content perfectly).

I am thankful to ctnbeh13 for his help and monetary involvement in keeping the cybersquatters out of our lawn, but cannot afford to take ownership of any domain name. The rest of this will be addressed in a more private manner.
By the way, I have no idea how much redirects come from .net or .org or other extensions.

Re: HTTPS enabled for AT.com

Posted: Wed Jun 08, 2016 10:56 pm
by rijackson741
Just to let everyone know, andorstrail.net is back up, and will forward to https:\\andorstrail.com. At the time of writing this actually does not work, but it will take a little time for the DNS servers to sort themselves out, so be patient.

Edit, 6:58 PM: a very little time for the DNS servers to sort them selves out. It now works.