Yesterday, I spent the entire day addressing the downtime issue with GoDaddy’s WHM. However, today, the server experienced another outage, indicating that the CentOS system has reached its End of Life (EOL). The specialist advised me to upgrade the system at an additional cost to ensure the server’s continued operation, a solution that I find unsatisfactory.

Considering that the server is still in the testing phase and not yet in production, even a single day of downtime could have significant consequences. Furthermore, GoDaddy’s services are inaccessible in China. Therefore, I have decided to switch to Bluehost.

Upon using the VPS server, I encountered several issues and gained insights:

Firstly, MongoDB was compromised for once, resulting in the loss of all data. This underscores that the management of servers must be very strict to ensure the security of data.

Secondly, I attempted to install GitLab to utilize the VPS as a code host. However, I discovered that the system requirements are high, and maintaining the GitLab codebase is complex. Therefore, it’s advisable not to install unnecessary software when the server is still in the testing stage. GitHub surpasses GitLab in code management and backup capabilities, while the subscription plans can be tailored to lower costs.

We also attempted to install Nginx RTMP live streaming, but due to server instability, we were concerned about the quality of the live stream. Tharu recommended using Twitch live streaming instead. It’s preferable not to rely on third-party tools for live streaming, as they will divert traffic away from our platform and introduce the complexity to user interactions.

To address these challenges, I backed up data from MongoDB, MySQL, the file system, and the codebase. I’ve submitted the refund form and am awaiting a response.