Need a 2024 Topic

[linuxluver]

Great to see the Phereo site is still here and running. But the last post in the forum was 23 November 2023.
Can't leave it like that.....so here is a topic from 2024.

If anyone has any news about the site it would be great to hear it.

Steve Withers / Linuxluver

[bo3b]

You might have seen that phereo went offline in the last couple of weeks. This happened because I'm not a real web admin, and did not finish the job of getting the domain registry in my name. So it was still in the name of the original dev, Denis, who is no longer associated with the project at all. That means none of us except Denis could log in to GoDaddy to update the registration.

For reasons that are not clear to me, GoDaddy took us offline and locked the domain for the last two weeks. This has caused a lot of knock-on effects, like breaking our HelixModBlog images, and breaking the AWS email setup. It's not great.


We are back up now, and should have resolved the GoDaddy problem, although I'm still not clear on exactly what happened. GoDaddy support is practically non-existent, which is why it took two weeks to get ahold of someone to prove we own the site.

In the meantime, I made an alternate site that we can use, that I have full control over with a domain registrar who knows what they are doing. If we get an outage in the future, you can now also use: https://phereo.us to get to the site.


One thing that I'm slowly working through is how to reenable email notification for these forums. Without that, I know these are very hard to use. Once I get it running, I'll send out a notice by posting here. I will also likely send a notice to all prior registered users, as I expect a lot of the older folks don't know that it is still running.

[bulkinav]

So it was still in the name of the original dev, Denis, who is no longer associated with the project at all. That means none of us except Denis could log in to GoDaddy to update the registration.

Hi bo3b. Tell me, please, has this problem been solved yet? You already have access to Phereo account on GoDaddy? Or maybe you have already moved the domain to another place? Is there anything I can do to help?

I also see that the Phereo site is now closed. Does it have anything to do with this situation?

[bo3b]

Still having some knock-on effects of this. Permanently broke some of our hosting for HelixMod. I still don't have access to the GoDaddy account, so I can't fix anything when DNS goes wrong.

Should be able to get this improved for phereo.com in a week or so.

In the last few days, GoDaddy broke the site by somehow forcing on a default 'coming soon' web page. I talked them into putting the IP back, and so DNS should resolve properly after a day or so.


You should be able to always see the site via https://phereo.us and https://forums.phereo.us because I'm running that domain name with a registrar that is not as lame as GoDaddy.

The backend servers on AWS are running the same as always and are not presently a concern.