Please note that this article is considered legacy documentation.
The recently announced deprecation of the Legacy Storm Private Network has prompted several questions, the most frequent of which being: How to upgrade and am I affected? Fortunately this announcement only affects a handful of our thousands of clients, those being customers who started using the Private Networking back in 2013. If you’re not sure, you’re welcome to open a ticket and be certain.
Regarding the upgrade process, we’ve made that as easy as possible and accessible to anyone with access to the manage interface. This how-to will walk you through the steps you need to follow to get detach from the current implementation and get connected to the new, improved version.
Continue reading “Upgrading from the Legacy Storm Private Network”
The Internet Protocol (IP) system designates how networked devices can address one another across the internet. The first major version of IP, IPv4, was deployed to the public ARPANET in 1983. IPv4 uses 4 one byte segments to designate a devices address, this 32-bit address space allows for 232 addresses to be used in total. The next major iteration of IP is called IPv6 and it uses a 128-bit address space allowing for significantly more IP addresses to be assigned. Continue reading “Difference Between ipv4 and ipv6”
localhost is a networking term; it’s the hostname for the loopback network interface of whichever server it’s said in reference to (meaning every server has a ‘localhost‘). The loopback interface bypasses any local network interface hardware, and serves as a method to connect back to the server itself. The term localhost is used often in both networking and in server administration.
The IPv4 address for localhost, or the loopback network interface, is 127.0.0.1.
The IPv6 address for localhost, or the loopback network interface, is ::1.
- These instructions are intended specifically for solving the error: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
- I’ll be working from both Liquid Web Core Managed Ubuntu 12.04 LTS and 14.04 LTS servers, and I’ll be logged in as root.
Continue reading “Error: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 on Ubuntu [SOLVED]”
- These instructions are intended specifically for solving the error: /usr/sbin/ifconfig: No such file or directory
- I’ll be working from a Liquid Web Self Managed CentOS 7 server, and I’ll be logged in as root.
Continue reading “Error: /usr/sbin/ifconfig: No such file or directory [SOLVED]”