Status Page

Maintenance completed.

Due to an issue with a software install requiring an operating system update, the server may go down during this maintenace period. Other affected services includes the status page API, comments API, and some non-important APIs and services.

Most of the systems have been moved over many weeks ago, so this incident will now be closed. The few systems that still need to be moved over will be moved at a later date.

I am currently in the process of changing from ndt3.me to truewinter.dev. Some services may go down during this process.

The host has confirmed that the migration is complete.

At this time, it seems like the migration is complete. I am still waiting for official confirmation.

The server migration is still in progress.

Scheduled maintenance is in progress.

The hosting provider has rescheduled the migration due to some issues.

One of my hosting providers will be moving some of their servers to a different datacenter to improve uptime and performance. This is scheduled for 16:00 - 21:00 on 9 July (GMT). During this time, the client panel will be down to allow for staff to transfer VMs to the relocated server and to configure networking for the new datacenter.

The additional IP address was successfully added to the server, and necessary changes to configuration files were made.

I am currently adding an additional IP address to the Web-01 server. During this time, some services hosted on this server may experience downtime.

This issue has been resolved.

The new login system has been pushed to production. As it is a new system, there may still be a few bugs. The analytics page does not currently work due to an issue with the hosting provider, but I'm hoping to work with them to find a solution.

As the client panel will be kept online until it is ready to be migrated, I have started pushing the auth system changes to production.

The new auth system is complete, and will be pushed to production after the scheduled maintenance.

While I'm unable to find the cause of the timeouts, I have started working on a different auth system that does not rely on an external service.

Attempting to access the client panel may result in a timeout and an error. Due to lack of clients using the panel, it is currently low priority and a fix is dependent on getting more clients. When enough funding can be obtained, this panel will be moved to a different server and there is a possibility of a rewrite of the auth system from our current provider to a custom developed system. However, at this point, the client panel may become obsolete.