{
  "id": 20121196,
  "title": "Sanyun Cloud Free Cloud Server Test: 14 Months Later, Raising a Work Order, Three Hours and Ten Hours Response Time Recorded",
  "url": "https://urgent.news/2026/11/15/story-20121196",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-15T05:43:18.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/lilika/san-feng-yun-mian-fei-yun-fu-wu-qi-shi-ce-shi-si-ge-yue-hou-zai-ti-gong-dan-san-xiao-shi-he-shi-xiao-shi-de-xiang-ying-du-zhao-shi-xie-1c7k"
  },
  "original_language": "zh",
  "account": "A user of Sanfangyun, a free cloud service provider, recently submitted two support tickets. The first ticket concerned a cron job that wasn't generating files as expected, and the support team responded within three hours, suggesting the user check environment variables and absolute paths in the script. The second ticket was about Nginx not starting after a system reinstallation, and the support team replied in about 10 hours, providing a troubleshooting sequence that helped resolve the issue. The user praises the support team for providing specific and helpful responses. The user also shares their experience with the service, noting that it is suitable for small projects, experiments, and backups due to its simplicity and ease of use.",
  "summary": "In my previous article, I mentioned that \"both work orders were resolved within two hours.\" Looking back, I realize that I glossed over the details. Recently, I submitted two more work orders, and the waiting time was longer than before. The resolution process was also more complicated than I initially thought. I decided to document the response rhythm and troubleshooting path in detail, and at the same time, update the current state of this machine after running for over a year. What is the machine currently running? From the time it was activated to the present, fourteen months have passed, during which I have manually renewed the service over sixty times through the console. The renewal period is 7 days, and I simply log in to the console and click \"Renew\" when it's time, which immediately refreshes the validity period without changing the IP address or disrupting the SSH session. I have set a weekly calendar reminder, and so far, I haven't missed a single renewal. The instance configuration is 1 core and 1G, with the basic system disk capacity. The software running on it has remained unchanged: a Typecho blog + Nginx + an automated backup script that runs at dawn. The script is straightforward: it uses mysqldump to export the database, tar to package the site directory, names the files by date, and keeps only the most recent four backups. The observed data is more stable than I anticipated: the load has consistently been between 0.2 and 0.5, primarily due to Nginx handling requests and the cron job.",
  "key_points": [
    "三丰云 free cloud server tested for 14 months",
    "Two maintenance requests took 3 and 10 hours to resolve",
    "Server suitable for low-demand tasks, not critical data storage"
  ],
  "editors_take": "The platform serves as a reliable testing ground for lightweight tasks, though its lack of high availability makes it an unsuitable choice for managing critical data.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}