Posted by Jackson Mitchell on 08/29/2024 (04:59)
Operator
墨,
Your server has been successfully unsuspended and all services are now restored to normal operation.
We kindly request your cooperation in monitoring the usage of your server closely. By keeping a watchful eye on resource utilization, you can ensure that your activities remain within acceptable limits and do not impact other users on the server.
As a responsible member of our hosting community, we encourage you to:
Regularly check your server's resource usage, including CPU, memory, disk space, and bandwidth consumption.
Take proactive measures to optimize your applications and website to minimize resource usage.
Implement any necessary restrictions or limits within your applications to prevent resource abuse.
We value your commitment to maintaining a stable and efficient hosting environment for all users, and your cooperation in this matter is greatly appreciated.
Thank you for choosing us as your hosting provider.
Best regards,
Jackson Mitchell,
Technical Support,
Subject: Request for Details and Reactivation of Suspended VPS
Posted by 墨 尽 on 08/29/2024 (04:30)
Owner
Dear Jackson Mitchell,
Thank you for your explanation and support.
I understand the importance of maintaining optimal performance in the shared server environment. Once my VPS is reactivated, I will immediately review and reduce the CPU load by optimizing the processes and Docker containers running on the server.
I appreciate your assistance in restoring my VPS and will take the necessary steps to prevent any future impact on the server’s performance.
Thank you for your understanding and cooperation.
Best regards,
墨 尽
Posted by Jackson Mitchell on 08/29/2024 (04:24)
Operator
墨,
Your VPS is hosted within a shared server environment. This means that the physical server hosting your VPS also accommodates multiple other virtual servers, all of which share common resources such as CPU, memory, disk space, and network bandwidth. While each VPS has its own isolated operating environment, the underlying physical resources are shared among all users on the server.
Recently, we have noticed that your VPS is placing a higher than usual load on the CPU, which could potentially impact the overall performance of the shared server. To ensure optimal performance for all users, we kindly request that you review and reduce the CPU load on your VPS, if possible. This can be achieved by optimizing resource-intensive processes, managing background tasks, or reviewing any running applications that may be consuming excessive resources.
If you require assistance in reducing the CPU load or need recommendations on resource management, please do not hesitate to reach out to us. We are here to help ensure your VPS continues to run smoothly within the shared hosting environment.
Thank you for your understanding and cooperation.
Best regards,
Jackson Mitchell,
Technical Support,
Colocrossing Cloud
Posted by 墨 尽 on 08/29/2024 (04:13)
Owner
Dear Jackson Mitchell,
Thank you for your prompt response and for bringing this issue to my attention.
Regarding the high CPU load on my VPS, here are the details about the Docker containers currently running on the server:
I have been monitoring the server performance but did not notice any unusual activity that could have caused a significant CPU spike. However, I am open to further investigation and would appreciate any assistance you can offer to identify the specific process or container causing the high CPU load.
Please let me know the next steps for reactivating my VPS as soon as possible, as it is essential for my ongoing projects.
Thank you for your support and understanding.
Best regards,
墨 尽
Posted by Jackson Mitchell on 08/29/2024 (04:01)
Operator
墨,
We regret to inform you that your server has been temporarily suspended due to a detected high load on the CPU. This suspension is necessary to prevent any potential degradation in server performance and to maintain the stability and reliability of our hosting environment.
We kindly request that you refrain from any activities on your VPS until further notice. This will help mitigate the impact of the high CPU load on other users sharing the server resources.
In order to address this issue effectively, we need your cooperation in identifying the program or process that may be causing the excessive CPU usage. Could you please provide us with information about the program or applications running on your server? This will help us pinpoint the source of the problem and take appropriate measures to resolve it.
Once again, we apologize for any inconvenience this may cause and appreciate your understanding and cooperation in this matter.
Thank you for your attention to this urgent matter.
Best regards,
Jackson Mitchell,
Technical Support,
Colocrossing Cloud
Posted by 墨 尽 on 08/29/2024 (03:52)
Owner
I hope this message finds you well. I received a notification stating that my VPS (Product/Service: 3GB Black Friday KVM VPS, Domain: linux.fe8871.com) has been suspended due to \"High load on CPU.\"
I would appreciate it if you could provide more detailed information regarding the cause of the high CPU load, including any logs or metrics that could help me identify the source of the issue. Additionally, I would like to know the steps I can take to prevent this from happening again.
Please assist me in reactivating my service as soon as possible, as this VPS is critical for my ongoing work.
Thank you for your prompt assistance.
","content_text":"如果再给我一次机会，我绝对不会贪图小便宜买 COLOCROSSING 的 VPS 了。\n\n\n\n\n\n\n附工单记录\n\n\nVIEW TICKET #545539\n\n\n REPLY CLOSE\n\nPosted by Jackson Mitchell on 08/29/2024 (04:59)\n\nOperator\n\n墨,\n\nYour server has been successfully unsuspended and all services are now restored\nto normal operation.\n\nWe kindly request your cooperation in monitoring the usage of your server\nclosely. By keeping a watchful eye on resource utilization, you can ensure that\nyour activities remain within acceptable limits and do not impact other users on\nthe server.\n\nAs a responsible member of our hosting community, we encourage you to:\n\nRegularly check your server's resource usage, including CPU, memory, disk space,\nand bandwidth consumption.\n\nTake proactive measures to optimize your applications and website to minimize\nresource usage.\n\nImplement any necessary restrictions or limits within your applications to\nprevent resource abuse.\n\nWe value your commitment to maintaining a stable and efficient hosting\nenvironment for all users, and your cooperation in this matter is greatly\nappreciated.\n\nThank you for choosing us as your hosting provider.\n\nBest regards, \n\nJackson Mitchell,\n\nTechnical Support,\n\n\nCOLOCROSSING CLOUD\n\nSubject: Request for Details and Reactivation of Suspended VPS\n\nPosted by 墨 尽 on 08/29/2024 (04:30)\n\nOwner\n\nDear Jackson Mitchell,\n\nThank you for your explanation and support.\n\nI understand the importance of maintaining optimal performance in the shared\nserver environment. Once my VPS is reactivated, I will immediately review and\nreduce the CPU load by optimizing the processes and Docker containers running on\nthe server.\n\nI appreciate your assistance in restoring my VPS and will take the necessary\nsteps to prevent any future impact on the server’s performance.\n\nThank you for your understanding and cooperation.\n\nBest regards,\n\n墨 尽\n\nPosted by Jackson Mitchell on 08/29/2024 (04:24)\n\nOperator\n\n墨,\n\nYour VPS is hosted within a shared server environment. This means that the\nphysical server hosting your VPS also accommodates multiple other virtual\nservers, all of which share common resources such as CPU, memory, disk space,\nand network bandwidth. While each VPS has its own isolated operating\nenvironment, the underlying physical resources are shared among all users on the\nserver.\n\nRecently, we have noticed that your VPS is placing a higher than usual load on\nthe CPU, which could potentially impact the overall performance of the shared\nserver. To ensure optimal performance for all users, we kindly request that you\nreview and reduce the CPU load on your VPS, if possible. This can be achieved by\noptimizing resource-intensive processes, managing background tasks, or reviewing\nany running applications that may be consuming excessive resources.\n\nIf you require assistance in reducing the CPU load or need recommendations on\nresource management, please do not hesitate to reach out to us. We are here to\nhelp ensure your VPS continues to run smoothly within the shared hosting\nenvironment.\n\nThank you for your understanding and cooperation.\n\nBest regards,\n\nJackson Mitchell,\n\nTechnical Support,\n\nColocrossing Cloud\n\nPosted by 墨 尽 on 08/29/2024 (04:13)\n\nOwner\n\nDear Jackson Mitchell,\n\nThank you for your prompt response and for bringing this issue to my attention.\n\nRegarding the high CPU load on my VPS, here are the details about the Docker\ncontainers currently running on the server:\n\n * FreshRSS\n * Gotify\n * Jackett\n * Excalidraw\n * qinglong\n * qiandao\n * Nginx\n * Redis\n * MySQL\n\nI have been monitoring the server performance but did not notice any unusual\nactivity that could have caused a significant CPU spike. However, I am open to\nfurther investigation and would appreciate any assistance you can offer to\nidentify the specific process or container causing the high CPU load.\n\nPlease let me know the next steps for reactivating my VPS as soon as possible,\nas it is essential for my ongoing projects.\n\nThank you for your support and understanding.\n\nBest regards,\n\n墨 尽\n\nPosted by Jackson Mitchell on 08/29/2024 (04:01)\n\nOperator\n\n墨,\n\nWe regret to inform you that your server has been temporarily suspended due to a\ndetected high load on the CPU. This suspension is necessary to prevent any\npotential degradation in server performance and to maintain the stability and\nreliability of our hosting environment.\n\nWe kindly request that you refrain from any activities on your VPS until further\nnotice. This will help mitigate the impact of the high CPU load on other users\nsharing the server resources.\n\nIn order to address this issue effectively, we need your cooperation in\nidentifying the program or process that may be causing the excessive CPU usage.\nCould you please provide us with information about the program or applications\nrunning on your server? This will help us pinpoint the source of the problem and\ntake appropriate measures to resolve it.\n\nOnce again, we apologize for any inconvenience this may cause and appreciate\nyour understanding and cooperation in this matter.\n\nThank you for your attention to this urgent matter.\n\nBest regards,\n\nJackson Mitchell,\n\nTechnical Support,\n\nColocrossing Cloud\n\nPosted by 墨 尽 on 08/29/2024 (03:52)\n\nOwner\n\nI hope this message finds you well. I received a notification stating that my\nVPS (Product/Service: 3GB Black Friday KVM VPS, Domain: linux.fe8871.com) has\nbeen suspended due to \"High load on CPU.\"\n\nI would appreciate it if you could provide more detailed information regarding\nthe cause of the high CPU load, including any logs or metrics that could help me\nidentify the source of the issue. Additionally, I would like to know the steps I\ncan take to prevent this from happening again.\n\nPlease assist me in reactivating my service as soon as possible, as this VPS is\ncritical for my ongoing work.\n\nThank you for your prompt assistance.","date_published":"2024-08-29T08:42:59.447Z","_microfeed":{"web_url":"https://blog-jinmo-com.pages.dev/i/vps-colocrossing-mUGMDdURL1D/","json_url":"https://blog-jinmo-com.pages.dev/i/mUGMDdURL1D/json/","rss_url":"https://blog-jinmo-com.pages.dev/i/mUGMDdURL1D/rss/","guid":"mUGMDdURL1D","status":"published","itunes:episodeType":"full","date_published_short":"Thu Aug 29 2024","date_published_ms":1724920979447}},{"id":"j1s3ex8_Ifl","title":"服务器四面楚歌","url":"https://blog.88208820.xyz/i/simiancg-j1s3ex8_Ifl/","content_html":"在阿里云服务器续费太贵被我放弃之后，我把数据（包括网站）都迁移到我在 colocrossing 的 vps 上了，没想到 colocrossing 直接整了一个大活，我现在已经几天没有连接上我的 vps 了，colocrossing 一点也不管，这就是便宜没好货。
尴尬的是我在 cloudcone 的服务器也过期了，现在已经没有一个可用之服务器了。
","content_text":"在阿里云服务器续费太贵被我放弃之后，我把数据（包括网站）都迁移到我在 colocrossing 的 vps 上了，没想到 colocrossing\n直接整了一个大活，我现在已经几天没有连接上我的 vps 了，colocrossing 一点也不管，这就是便宜没好货。\n\n\n\n\n尴尬的是我在 cloudcone 的服务器也过期了，现在已经没有一个可用之服务器了。","date_published":"2024-07-27T16:38:46.708Z","_microfeed":{"web_url":"https://blog-jinmo-com.pages.dev/i/服务器四面楚歌-j1s3ex8_Ifl/","json_url":"https://blog-jinmo-com.pages.dev/i/j1s3ex8_Ifl/json/","rss_url":"https://blog-jinmo-com.pages.dev/i/j1s3ex8_Ifl/rss/","guid":"j1s3ex8_Ifl","status":"published","itunes:episodeType":"full","date_published_short":"Sat Jul 27 2024","date_published_ms":1722098326708}},{"id":"i3l0CdW4zOi","title":"部署 jellyfin","url":"https://blog.88208820.xyz/i/i3l0CdW4zOi/","content_html":"尝试在 docker destop 中部署 jellyfin ，目的是为了在移动端可以查看媒体库，配合 在docker desktop 中部署的 auto bangumi 实现自动追番。
成功的在 docker destop 中部署了 jellyfin ，但是遇到了不小的问题，主要是 docker desktop 中不太支持 host 模式，导致虽然可以使用 localhost:8096 来访问 jellyfin ，但是无法使用本机 ip 来访问 ，这使得移动端访问成为了天方夜谭。
目前解决方法有通过 wsl 来安装到 Ubuntu 上，或者直接安装到 windows 上，决定还是直接 scoop 安装到 win 上了。
","content_text":"尝试在 docker destop 中部署 jellyfin ，目的是为了在移动端可以查看媒体库，配合 在docker desktop 中部署的 auto\nbangumi 实现自动追番。\n\n\n\n\n成功的在 docker destop 中部署了 jellyfin ，但是遇到了不小的问题，主要是 docker desktop 中不太支持 host\n模式，导致虽然可以使用 localhost:8096 来访问 jellyfin ，但是无法使用本机 ip 来访问 ，这使得移动端访问成为了天方夜谭。\n\n\n\n\n目前解决方法有通过 wsl 来安装到 Ubuntu 上，或者直接安装到 windows 上，决定还是直接 scoop 安装到 win 上了。","date_published":"2024-07-08T08:06:37.388Z","_microfeed":{"web_url":"https://blog-jinmo-com.pages.dev/i/jellyfin-i3l0CdW4zOi/","json_url":"https://blog-jinmo-com.pages.dev/i/i3l0CdW4zOi/json/","rss_url":"https://blog-jinmo-com.pages.dev/i/i3l0CdW4zOi/rss/","guid":"i3l0CdW4zOi","status":"published","itunes:episodeType":"full","date_published_short":"Mon Jul 08 2024","date_published_ms":1720425997388}},{"id":"LCMGZaVo1ER","title":"windows 上与包管理器 scoop 适配的 UI","attachments":[{"url":"https://r2.88208820.xyz/blog-jinmo-com/production/media/image-ba3a5cec775cb8ff469bc4f03020791d.png","mime_type":"image/png","size_in_byte":120879}],"url":"https://blog.88208820.xyz/i/windows-baoguanliqi-scoop-ui-LCMGZaVo1ER/","content_html":"在了解了 WingetUI (will soon become UniGetUI) 项目之后，我感觉这大大提升了在 windows 软件更新和管理的能力。
WingetUI 可以与几乎所有包管理器 （不只是 Scoop、Winget、Chocolatey） 适配并提供 可视化 UI，不再需要记住命令。
项目地址 https://github.com/marticliment/WingetUI
","content_text":"在了解了 WingetUI (will soon become UniGetUI) 项目之后，我感觉这大大提升了在 windows 软件更新和管理的能力。\n\nWingetUI 可以与几乎所有包管理器 （不只是 Scoop、Winget、Chocolatey） 适配并提供 可视化 UI，不再需要记住命令。\n\n项目地址 https://github.com/marticliment/WingetUI","banner_image":"https://r2.88208820.xyz/blog-jinmo-com/production/media/image-ba3a5cec775cb8ff469bc4f03020791d.png","date_published":"2024-05-23T15:53:28.138Z","_microfeed":{"is_audio":false,"is_document":false,"is_external_url":false,"is_video":false,"is_image":true,"web_url":"https://blog-jinmo-com.pages.dev/i/windows-scoop-ui-LCMGZaVo1ER/","json_url":"https://blog-jinmo-com.pages.dev/i/LCMGZaVo1ER/json/","rss_url":"https://blog-jinmo-com.pages.dev/i/LCMGZaVo1ER/rss/","guid":"LCMGZaVo1ER","status":"published","itunes:episodeType":"full","date_published_short":"Thu May 23 2024","date_published_ms":1716479608138}},{"id":"5inVTwGHy7v","title":"网站证书更新","url":"https://blog.88208820.xyz/i/gengx-5inVTwGHy7v/","content_html":"网站证书又到期了，不想一次次的手动更新证书了，于是写了一个 bash 脚本更新证书并移动证书文件到 nginx 的配置文件夹，再写了一个 crontab 任务每两个月执行一遍脚本。
出现错误
-------------------
执行时间: Wed May 1 00:00:01 CST 2024
开始更新证书...
the input device is not a TTY
ACME 更新失败。
解决方法是在使用脚本执行 docker 指令时，需要把 -it 去掉
参考链接
https://blog.csdn.net/sunmingyang1987/article/details/108877902
#!/bin/bash\n\n\n\n\n# 设置域名和路径变量\n\nDOMAIN=\"jinmo.cloud\"\n\nACME_VOLUME_PATH=\"/data/acme.sh/out/\"\n\nNGINX_CONFIG_PATH=\"/data/nginx/config\"\n\nLOG_FILE=\"/usr/local/script/updateCertificat/updateCertificat.log\"\n\n\n\n\n# 在日志文件中记录执行时间\n\necho \"-------------------\" >> \"$LOG_FILE\"\n\necho \"执行时间: $(date)\" >> \"$LOG_FILE\"\n\n\n\n\n# 使用 ACME 容器更新证书\n\necho \"开始更新证书...\" >> \"$LOG_FILE\"\n\ndocker run --rm -v \"$ACME_VOLUME_PATH:/acme.sh\" neilpang/acme.sh --renew -d \"$DOMAIN\" --force &>> \"$LOG_FILE\"\n\n\n\n\n# 检查更新是否成功\n\nif [ $? -ne 0 ]; then\n\n echo \"ACME 更新失败。\" >> \"$LOG_FILE\"\n\n exit 1\n\nelse\n\n echo \"ACME 更新成功。\" >> \"$LOG_FILE\"\n\nfi\n\n\n\n\n# 复制证书文件到 Nginx 配置路径\n\necho \"复制证书文件到 Nginx 配置路径...\" >> \"$LOG_FILE\"\n\n# 记录执行语句\n\necho \"cp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.csr $NGINX_CONFIG_PATH/\" >> \"$LOG_FILE\"\n\ncp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.csr $NGINX_CONFIG_PATH/ &>> \"$LOG_FILE\"\n\necho \"cp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.cer $NGINX_CONFIG_PATH/\" >> \"$LOG_FILE\"\n\ncp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.cer $NGINX_CONFIG_PATH/ &>> \"$LOG_FILE\"\n\necho \"cp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.key $NGINX_CONFIG_PATH/\" >> \"$LOG_FILE\"\n\ncp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.key $NGINX_CONFIG_PATH/ &>> \"$LOG_FILE\"\n\n\n\n\n# 检查复制操作是否成功\n\nif [ $? -ne 0 ]; then\n\n echo \"复制证书文件失败。\" >> \"$LOG_FILE\"\n\n exit 1\n\nelse\n\n echo \"复制证书文件成功。\" >> \"$LOG_FILE\"\n\nfi\n\n# 重新启动 Nginx 容器\necho \"重新启动 Nginx 容器...\" >> \"$LOG_FILE\"\ndocker restart $NGINX_CONTAINER_NAME &>> \"$LOG_FILE\"\n\n\n# 检查重新启动操作是否成功\nif [ $? -ne 0 ]; then\n echo \"Nginx 容器重新启动失败。\" >> \"$LOG_FILE\"\n exit 1\nelse\n echo \"Nginx 容器重新启动成功。\" >> \"$LOG_FILE\"\nfi\n\n\n\n\n# 输出执行完成的消息\n\necho \"证书更新和复制操作已完成。\" >> \"$LOG_FILE\"\n","content_text":"网站证书又到期了，不想一次次的手动更新证书了，于是写了一个 bash 脚本更新证书并移动证书文件到 nginx 的配置文件夹，再写了一个 crontab\n任务每两个月执行一遍脚本。\n\n\n\n\n出现错误\n\n> -------------------\n\n> 执行时间: Wed May 1 00:00:01 CST 2024\n\n> 开始更新证书...\n\n> the input device is not a TTY\n\n> ACME 更新失败。\n\n解决方法是在使用脚本执行 docker 指令时，需要把 -it 去掉\n\n参考链接\n\nhttps://blog.csdn.net/sunmingyang1987/article/details/108877902\n\n\n\n\n\n\n\n#!/bin/bash\n\n\n\n\n# 设置域名和路径变量\n\nDOMAIN=\"jinmo.cloud\"\n\nACME_VOLUME_PATH=\"/data/acme.sh/out/\"\n\nNGINX_CONFIG_PATH=\"/data/nginx/config\"\n\nLOG_FILE=\"/usr/local/script/updateCertificat/updateCertificat.log\"\n\n\n\n\n# 在日志文件中记录执行时间\n\necho \"-------------------\" >> \"$LOG_FILE\"\n\necho \"执行时间: $(date)\" >> \"$LOG_FILE\"\n\n\n\n\n# 使用 ACME 容器更新证书\n\necho \"开始更新证书...\" >> \"$LOG_FILE\"\n\ndocker run --rm -v \"$ACME_VOLUME_PATH:/acme.sh\" neilpang/acme.sh --renew -d \"$DOMAIN\" --force &>> \"$LOG_FILE\"\n\n\n\n\n# 检查更新是否成功\n\nif [ $? -ne 0 ]; then\n\n echo \"ACME 更新失败。\" >> \"$LOG_FILE\"\n\n exit 1\n\nelse\n\n echo \"ACME 更新成功。\" >> \"$LOG_FILE\"\n\nfi\n\n\n\n\n# 复制证书文件到 Nginx 配置路径\n\necho \"复制证书文件到 Nginx 配置路径...\" >> \"$LOG_FILE\"\n\n# 记录执行语句\n\necho \"cp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.csr $NGINX_CONFIG_PATH/\" >> \"$LOG_FILE\"\n\ncp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.csr $NGINX_CONFIG_PATH/ &>> \"$LOG_FILE\"\n\necho \"cp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.cer $NGINX_CONFIG_PATH/\" >> \"$LOG_FILE\"\n\ncp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.cer $NGINX_CONFIG_PATH/ &>> \"$LOG_FILE\"\n\necho \"cp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.key $NGINX_CONFIG_PATH/\" >> \"$LOG_FILE\"\n\ncp ${ACME_VOLUME_PATH}${DOMAIN}/${DOMAIN}.key $NGINX_CONFIG_PATH/ &>> \"$LOG_FILE\"\n\n\n\n\n# 检查复制操作是否成功\n\nif [ $? -ne 0 ]; then\n\n echo \"复制证书文件失败。\" >> \"$LOG_FILE\"\n\n exit 1\n\nelse\n\n echo \"复制证书文件成功。\" >> \"$LOG_FILE\"\n\nfi\n\n# 重新启动 Nginx 容器\necho \"重新启动 Nginx 容器...\" >> \"$LOG_FILE\"\ndocker restart $NGINX_CONTAINER_NAME &>> \"$LOG_FILE\"\n\n\n# 检查重新启动操作是否成功\nif [ $? -ne 0 ]; then\n echo \"Nginx 容器重新启动失败。\" >> \"$LOG_FILE\"\n exit 1\nelse\n echo \"Nginx 容器重新启动成功。\" >> \"$LOG_FILE\"\nfi\n\n\n\n\n# 输出执行完成的消息\n\necho \"证书更新和复制操作已完成。\" >> \"$LOG_FILE\"\n","date_published":"2024-04-18T10:01:31.261Z","_microfeed":{"web_url":"https://blog-jinmo-com.pages.dev/i/网站证书更新-5inVTwGHy7v/","json_url":"https://blog-jinmo-com.pages.dev/i/5inVTwGHy7v/json/","rss_url":"https://blog-jinmo-com.pages.dev/i/5inVTwGHy7v/rss/","guid":"5inVTwGHy7v","status":"published","itunes:episodeType":"full","date_published_short":"Thu Apr 18 2024","date_published_ms":1713434491261}},{"id":"sW5i4DLdNp5","title":"pnpm 设置代理","url":"https://blog.88208820.xyz/i/sW5i4DLdNp5/","content_html":"pnpm config set proxy http://127.0.0.1:7890
pnpm config set https-proxy https://127.0.0.1:7890
","content_text":"设置代理命令\n\npnpm config set proxy http://127.0.0.1:7890\n\n\n\n\n\n检查设置命令\n\npnpm config set https-proxy https://127.0.0.1:7890","date_published":"2024-04-16T14:30:03.334Z","_microfeed":{"web_url":"https://blog-jinmo-com.pages.dev/i/pnpm-sW5i4DLdNp5/","json_url":"https://blog-jinmo-com.pages.dev/i/sW5i4DLdNp5/json/","rss_url":"https://blog-jinmo-com.pages.dev/i/sW5i4DLdNp5/rss/","guid":"sW5i4DLdNp5","status":"published","itunes:episodeType":"full","date_published_short":"Tue Apr 16 2024","date_published_ms":1713277803334}},{"id":"mOrkaYjWNY3","title":"Hey! Kong!","attachments":[{"url":"https://r2.88208820.xyz/blog-jinmo-com/production/media/image-669662523d2a85a20d1238d81fbddf35.png","mime_type":"image/png","size_in_byte":1592}],"url":"https://blog-jinmo-com.pages.dev/i/hey-kong-mOrkaYjWNY3/","content_html":"