It's been a week. The Pi is running for 7 days, and three hours. This is what I've acomplished so far:
- 7 days of uptime
- I got rid of all that apps that shouldn't be found on a server
- I've learned something new about DNS and afraid.org. Afraid.org DNS hosting is cool if you don't have a website that needs to be indexed. The bad thing with afraid.org is that I've sent them an e-mail to enable googlebot indexing for my subdomain like about a week ago and they still didn't respond to it... Their support sucks. I've used free services before and the maximum time I've been on hold was for about 3-4 hours. I really don't know how they have 2000+ premium members if they don't respond to a fucking e-mail within a week. It's not like all 1.6 milion users sent an email on January 11th to support asking them to make their sites visible to search indexes. Geez.
- With the help of an old friend, the DNS queries are now routed via dns.teraforum.ro (I suggest visiting his forum). We hope that this will stop DNS not found error in Google Fetch. (I don't think so)
- Although Google Bot can't reach my site, other bots can. I've seen in the past week a lot of shellcode and suspicious user-agent strings reaching my server. Right now, in the moment of writing this, I can see the following line in logs:
- I've found out that this site has 92/100 points in Google Page Insights and big-bum-s.blogspot.com has only 88/100 points even if it's a blog made with Google.
- I've broken and unbroken my router trying to somehow set a DNS server on it. Good that SSH exists. And backups. Yeah. Backups and SSH. You know the saying: "Safety first".
- nginx directives in locations are like iptables rules: they are respecting the order in which you set them. So if condition A is met, then condition B refering to the aproximatively same condition as A will not be reached. It's hard to understand without having a little experience with iptables, but let me explain you.
Let's assume that you have a webserver but you want to have an IP blocked from reaching your webserver. You open your port for allowing http connections and then you block the IP, like this (this is not the actual syntax):
allow connections from all IPs on port 80 block connections from IP
But this won't work. Why? Because you've just allowed connections from ALL IPs on the port. You first must block connections from the IP, then allow all others to visit your webserver.
block connections from IP allow connections from all IPs on port 80
Something like this. This is also the way nginx works and why I've had some trouble to understand why minify didn't want to work correctly with cache leveraging. (I only got 89 points in Google Insight without cache leveaging, still better than blogger)
- I've learned that I really like making unordered lists