You can host two SSL websites for Windows XP computers or Android 2.0 smartphones.
These platforms do not support SNI (Server Name Indication), so that each website must be hosted on a separate IP address.
Despite being on the same server you could run 2x NS servers (because you have 2x diff IPs) then you can setup your domains to use them~. Talking about this: some registrars do not care if the IPs are different (they just want different hostnames), while others will check if they resolve to the same IP address.
The other use case I encountered was to avoid a throttle per IP address, with an additional IP your APP can switch to use the first IP, then the second one, then the first, etc.
Potentially you could also run another container with the full TCP ports range [1-65535] without NAT/port mapping (so you can use SSH on port 22 on that other IP as if it was a completely different server).
There's some upcoming changes I'd like to unofficially communicate here first. I'm listing them in their probable order. None of them have been fully confirmed, it's possible plans may change.
LAX - LAXA030 and LAXA031 will be physically moved and also have IPv4 addresses changed.
NYC - NYCB011 and NYCB017 are likely going to be retired and will move elsewhere.
AMS - We have some servers sharing 1x /24 per two and then when Frankfurt got moved in, the servers kept 1x /24 per server. We're going to try to change it to where it's three servers per 2x /24. The focus will be on keeping everyone's IP address the same so what will happen is there will be some migrations.
NYC & LAX - If you purchased a special with multiple IP addresses, a few of you may be moved around (nothing crazy.) If your IP is on a /25 then the IP address may change or may move (or it might not move or change, but the gateway might change to a /26.)
CHI - CHIZ001, CHIZ002, CHIZ003, and CHIZ004 will have a series of migrations and potentially IP changes. If possible, they'll first be consolidated to two servers (then if not, IP changes.) CHIZ004 is going to be retired.
TYO - A lot will happen here. We're going to be adding in at least another network switch, and bring the other new servers online. There will likely be a physical migration to another datacenter to address the inbound connectivity issue (@tulipyun) as well as some other things, and I'll likely attempt to make another visit there. Some migrations (between servers) and we'll try to avoid any IP changes. We'll also be trying to wrap up all the other Tokyo things we talked about in the past.
ATL - Likely will have more servers sent out to this location to fill it out. We might also make a small little storage server, but it might just end up being for our own backups. I'll likely be visiting and organizing everything. No current planned shuffling. Less than zero percent chance that we might instead close out this location instead and open a new one nearby. But close to zero.
SJC - This location needs to be completely re-racked/organized. I'll have to visit. We had to make it work with whatever Dedipath left us and I'm not happy with how none of the original San Jose servers have their original rails anymore. There's a high likelihood of IPv4 addresses requiring another set of changes so if that's the case I'll try to line everything up together, but as it stands there's no planned IP change here.
LAX/SJC - There will likely be an expansion in one of these locations. We're also looking at bringing back one other location.
Comments
FTFY
Deal or no deal
Virmach Deals
You can host two SSL websites for Windows XP computers or Android 2.0 smartphones.
These platforms do not support SNI (Server Name Indication), so that each website must be hosted on a separate IP address.
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
What's so good about SJ?
I don't have one over there before.
It looks like @VirMach finally fixed Looking Glass, but the SSL certificate for https://nyc.lg.virmach.com/ is wrong.
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
It is close to Google/YouTube servers~ (Silicon Valley)
Despite being on the same server you could run 2x NS servers (because you have 2x diff IPs) then you can setup your domains to use them~. Talking about this: some registrars do not care if the IPs are different (they just want different hostnames), while others will check if they resolve to the same IP address.
The other use case I encountered was to avoid a throttle per IP address, with an additional IP your APP can switch to use the first IP, then the second one, then the first, etc.
Potentially you could also run another container with the full TCP ports range [1-65535] without NAT/port mapping (so you can use SSH on port 22 on that other IP as if it was a completely different server).
tokyo looks good now
I bench YABS 24/7/365 unless it's a leap year.
There's some upcoming changes I'd like to unofficially communicate here first. I'm listing them in their probable order. None of them have been fully confirmed, it's possible plans may change.
LAX - LAXA030 and LAXA031 will be physically moved and also have IPv4 addresses changed.
NYC - NYCB011 and NYCB017 are likely going to be retired and will move elsewhere.
AMS - We have some servers sharing 1x /24 per two and then when Frankfurt got moved in, the servers kept 1x /24 per server. We're going to try to change it to where it's three servers per 2x /24. The focus will be on keeping everyone's IP address the same so what will happen is there will be some migrations.
NYC & LAX - If you purchased a special with multiple IP addresses, a few of you may be moved around (nothing crazy.) If your IP is on a /25 then the IP address may change or may move (or it might not move or change, but the gateway might change to a /26.)
CHI - CHIZ001, CHIZ002, CHIZ003, and CHIZ004 will have a series of migrations and potentially IP changes. If possible, they'll first be consolidated to two servers (then if not, IP changes.) CHIZ004 is going to be retired.
TYO - A lot will happen here. We're going to be adding in at least another network switch, and bring the other new servers online. There will likely be a physical migration to another datacenter to address the inbound connectivity issue (@tulipyun) as well as some other things, and I'll likely attempt to make another visit there. Some migrations (between servers) and we'll try to avoid any IP changes. We'll also be trying to wrap up all the other Tokyo things we talked about in the past.
ATL - Likely will have more servers sent out to this location to fill it out. We might also make a small little storage server, but it might just end up being for our own backups. I'll likely be visiting and organizing everything. No current planned shuffling. Less than zero percent chance that we might instead close out this location instead and open a new one nearby. But close to zero.
SJC - This location needs to be completely re-racked/organized. I'll have to visit. We had to make it work with whatever Dedipath left us and I'm not happy with how none of the original San Jose servers have their original rails anymore. There's a high likelihood of IPv4 addresses requiring another set of changes so if that's the case I'll try to line everything up together, but as it stands there's no planned IP change here.
LAX/SJC - There will likely be an expansion in one of these locations. We're also looking at bringing back one other location.
Yeah that's what i was working on right before I fell asleep a day or two ago. Should be good now.
Boo. (Hopefully this won't jinx things!) CHIZ001 has been one of, if not the, most reliable VPS that I have.
That's only low 'cos of a reboot for a kernel update.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)