I guess this is finished then.

There's no point really. We have mirabeta.org now and there's no point in spending money on betaheze.

In T11280#226737, @Routhwick wrote:

At this writing, though, typing in betaheze.org leads to a blank-slate homepage parker courtesy of IONOS; that much I noted at the Community noticeboard last month (along with the current status of @MirahezeStatus on X/Twitter). Did the departed volunteers abandon it back in June as well, or did someone forget to pay the bills?

At this writing, though, typing in betaheze.org leads to a blank-slate homepage parker courtesy of IONOS; that much I noted at the Community noticeboard last month (along with the current status of @MirahezeStatus on X/Twitter). Did the departed volunteers abandon it back in June as well, or did someone forget to pay the bills?

17:42 <Voidwalker> Looks like cron crashed leading to duplicate services being started repeatedly

rebooted and currently being investigated by @Void CPU use was at 100% and server was inaccessible.

**This is the truth Miraheze is burning like a house and the suppoesed firefighters are sitting relaxing having a coffee instead of helping

Looks like someone has done this.

We can go ahead and drop .ml and .ga from the DNS repo, as I’m dropping the registration, I’m only retaining the .tk and .gq

freenom lost .ga awhile ago, and seems like they may have lost .ml just recently.

The wiki is no longer accessible at the given URL due to this issue.

Alhamdulillah, it's working.
thank you very much.

Please try now. (in ~10 mins)

In T10540#212232, @PiscesKazeMGR wrote:

And I though the tutorial is only apply to subdomain :)

Closed as this is easy as changing some lines of records and we are done...

Let's get this thing end with...

And I though the tutorial is only apply to subdomain :)

If you say so...
And also I have checked the record. The nameserver is now from CF.
Looks like I'm will be fine if I done this as fast as I do.

I don't think we will need to do anything special here. The TLS certificate doesn't care who the authoritative nameserver is, and CNAME flattening doesn't introduce any concerns in terms of TLS. As long as you point the custom domain to mw-lb.miraheze.org, everything should Just Work.

Have you read https://meta.miraheze.org/wiki/Custom_domains#Note_for_CloudFlare_users ?

In T10362#211172, @PiscesKazeMGR wrote:

In T10362#211165, @Reception123 wrote:

I will try to get this done soon but it could be sped up if you would find your wiki in https://archive.org/details/miraheze-wikibackups18122022.

That's if I have access to a personal computer, not having to go to Internet cafe for these technical thingy.
Beside, my wiki has been deleted for a very long time before since this backup has been uploaded. I'm actually uncertain if I can get to it myself or I will have to let you do all of these just to restore a small project that I don't have time to developing before that.

In T10362#211165, @Reception123 wrote:

I will try to get this done soon but it could be sped up if you would find your wiki in https://archive.org/details/miraheze-wikibackups18122022.

I will try to get this done soon but it could be sped up if you would find your wiki in https://archive.org/details/miraheze-wikibackups18122022.

Long time no see! Working on the OG wiki, feels good so far.
How is the restroration progress going 💀

I'll close this as it's not that important for me right now, although I think it would be a good idea to set up cookie blocking across subdomains, so that custom subdomain functionality is available to users with domains.

Let's hope we found them or have me a backup if Alzheimer haven't come to this part yet...