Continued from Part 3 of the Lock It Down series By now, we should have both of our servers set up to communicate to each other via the Private Network. Our DBServer is on 10.0.2.0/24 and the Webservers are on 10.0.1.0/24, so now we’re left with installing our Database Server […]
Continuation of the Lock it down series. The network configuration is going to be a tricky thing for someone if they’re not use to setting up network interfaces, but knowing how to is the most important thing you can know when dealing with virtual servers like these when you start looking at Cloning, […]
Continuation of Part 1 Intro Summary from the Lock it down series So we’ve laid out the basic fundamentals of what we’re trying to achieve: “Create a Webserver that’s separate from it’s Database, gear it to be scalable, and lock it down as much as possible yet fully functioning. Now, this isn’t a webserver setup […]
So mid-Aug, 1&1 released their VPN feature for the “Next Generation of Cloud Servers” (NGCS), and like many things with the new Cloud Servers, it seems like this new feature is relatively unknown. Hopefully I can explain percisely what it is, and also clear up some misrepresentations of what it’s […]
Finally got around to securing both TimGarrity.me and AIOXperts protected by an SSL. Now for when I start working on my projects and client sites, they’ll follow the naming convention as I always used “client.xxx.aioxperts.com” or “project.xxx.timgarrity.me” and they’ll be locked behind a nice secure SSL.
Continuing from what we learned with LoadBalancing: https://timgarrity.me/load-balancing-with-11/ Previously, we went over the power of using 1&1’s provided Load Balancer to spread the incoming load among servers. One of the design concepts of the LoadBalancer itself is to take an incoming port and map it to a local port, relative of […]