To be kicked

At present, the blog is running on a HK virtual host. I have no desire to be stable enough, so I haven't changed it. I wanted to change it before, because it was unstable for a period of time, and I often couldn't open it. I was a little angry. Later, it also stabilized. In addition, CloudCone, which wanted to change to overseas, had been playing tricks all the time. The promotion was the same as no promotion. I hated it so much that I didn't buy it (in the final analysis, I didn't want to spend more money on it. It was not useless, it was too stingy).

At the end of February, the blog unexpectedly failed to open, which also showed a 403 error, and the panel was unable to log in. After contacting the management, it was found that the traffic was exceeded, so it could be opened manually by adding traffic.

The day before yesterday, the blog was also 403, which could not be opened, and the panel could not be logged in. Last night, I contacted the management, and this time I added traffic, which is added every month. Thank you.

I didn't have time to watch it at night, so I ignored it. But before I went to bed, I looked at it on my mobile phone and found a strange situation. Why is my blog IP always accessing me crazily, leading to insufficient traffic.

This is your stupid fork

Why do you visit your own traffic? There is no reason why your blog is hacked, and hacked is not your own.

It suddenly occurred to me that I did a silly operation. I made a feed to read sub sites on the blog home page. Because of real-time reading, no cache was added, each page was refreshed once, and the feed was requested once, wasting the traffic.

What a stupid fork!!!