For the last few days, I had noticed that the site was giving me an SSL error somewhat like the one I remember ignoring in front of @cmloegmcluin; however, instead of the cert just being out of date, it was for a completely different website I had never heard of, and clicking the ignore button actually sent me *to* that website. I thought of contacting @Dave Keenan, but then I realized I couldn't...
I'm... confused, and was also worried for those few days...
Did... something happen?
- volleo6144
- Posts: 81
- Joined: Mon May 18, 2020 7:03 am
- Location: Earth
- Contact:
Did... something happen?
I'm in college (a CS major), but apparently there's still a decent amount of time to check this out. I wonder if the main page will ever have 59edo changed to green...
- Dave Keenan
- Site Admin
- Posts: 2180
- Joined: Tue Sep 01, 2015 2:59 pm
- Location: Brisbane, Queensland, Australia
- Contact:
Re: Did... something happen?
Hi volleo. I'm so sorry to have put you (and unknown others) through that. I'll email you so you have my gmail address in case anything like that happens again.
Yes. Something happened.
We had to upgrade the operating system of the Sagittal web-server (a Virtual Private Server or VPS). The OS was so old (Ubuntu 16.04, April 2016) that it stopped being supported in April this year. In theory, we should have been able to upgrade it in-place, by upgrading first to 18.04, then to 20.04. But in practice multiple attempts to do this, failed. So then we just paid for a new VPS running 20.04 and started moving things there. But still there were enormous numbers of problems in getting the web sites up again. And they are still not completely resolved. e.g. you may find that you get a security warning when you use https://forum.sagittal.org, but not when you use https://sagittal.org/forum. The two should be equivalent. I'm working on it.
The virtual private server that the Sagittal website and forum runs on, is shared with my personal website and some other sites run by a friend of mine (Eddie Matejowsky). Being on the same VPS, they all share the same IP address. Eddie started the server, and so his oldest site (with the "eternal flame" GIF) is the default site for the server's IP address http://103.1.186.221. I assume that's the unfamiliar site that (understandably) confused and worried you, over a couple of days when I had limited time available to work on the problem. I should have switched the sagittal.org domain back to the old server during that time, sorry. But one keeps thinking the next thing one tries is going to fix the problem. In the end it was Eddie who got Sagittal and the forum working again.
Yes. Something happened.
We had to upgrade the operating system of the Sagittal web-server (a Virtual Private Server or VPS). The OS was so old (Ubuntu 16.04, April 2016) that it stopped being supported in April this year. In theory, we should have been able to upgrade it in-place, by upgrading first to 18.04, then to 20.04. But in practice multiple attempts to do this, failed. So then we just paid for a new VPS running 20.04 and started moving things there. But still there were enormous numbers of problems in getting the web sites up again. And they are still not completely resolved. e.g. you may find that you get a security warning when you use https://forum.sagittal.org, but not when you use https://sagittal.org/forum. The two should be equivalent. I'm working on it.
The virtual private server that the Sagittal website and forum runs on, is shared with my personal website and some other sites run by a friend of mine (Eddie Matejowsky). Being on the same VPS, they all share the same IP address. Eddie started the server, and so his oldest site (with the "eternal flame" GIF) is the default site for the server's IP address http://103.1.186.221. I assume that's the unfamiliar site that (understandably) confused and worried you, over a couple of days when I had limited time available to work on the problem. I should have switched the sagittal.org domain back to the old server during that time, sorry. But one keeps thinking the next thing one tries is going to fix the problem. In the end it was Eddie who got Sagittal and the forum working again.
- Dave Keenan
- Site Admin
- Posts: 2180
- Joined: Tue Sep 01, 2015 2:59 pm
- Location: Brisbane, Queensland, Australia
- Contact:
Re: Did... something happen?
AFAIK, Normality Has Been Restored.
https://forum.sagittal.org no longer gives security warnings, and
https://sagittal.org/forum is no longer needed and no longer works.
https://forum.sagittal.org no longer gives security warnings, and
https://sagittal.org/forum is no longer needed and no longer works.