New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I have a new Canada server, Along with a bunch of new locations coming soon. I just need to get them installed and setup. I will allow people to move to the new server by request. My goal is to let the majority of people request to move or cancel then force the rest of everyone out towards the end of next year. A long but more efficient process on my end due to the way I originally set up my SolusVM master(s). As far as templates on the OVZ6 nodes I don't have plans on adding any new ones as I would prefer to have people move to OVZ7 nodes.
Debian 10 can't run on OpenVZ6, the kernel is way too old.
Just for clarity, "move" meaning ... ? Is there a migration path or is this a backup and re-provision?
Unfortunately, it has to be a backup and re-provision as they both have their own SolusVM Masters. Not too sure what I was thinking when I originally set them up but it wasn't a very good idea to have separate masters. haha.
( chuckle ) That was what it sounded like but wanted to be sure.
Will you put out an email or something when it's time to move?
Yes, I will. I will make an offer post on here when the new locations are available aswell.
Hey' I'm ready to move at any time. Can do a destroy and recreate even (no backup restore needed).
Is there an ETA yet?
Was just about to order some new servers
Haha, I am ~Hoping~ it takes less than 2 weeks. I would like to expect it within the week however, things often come up...
Me too, happy to help test the new setup whenever you're ready, @Cam
I should really say no but I will be happy to try out for any location that is closer to where I am based. Just this morning signed up for MrVM - Singapore loc. (which also completes the NAT trilogy btw).
p.s: loving the BF offer by @cam on web hosting. The $1/year deal :-)
@Cam any hints on the upcoming locations?
How are your experiences with MrVM?
Thought about getting the SGP locations as well
Signed up this morning, waiting for provisioning. Got the 128 MB Plan- haven't kicked the tyres yet so to speak. They have a limited stock (low single digits for both the 128 MB and 256 MB plans though.
US
Agh, was hoping for some EU or APAC love
I like US love! As long as it's West Coast love!
@Cam will Bulgaria get an upgrade to OVZ7 as well?
Eventually yes, however, I don't currently have a new server lined up.
Purchased a NAT VPS with 2$ yearly, the performance is perfect !
Can I run .net core 2.2 webapps on your webhosting?
We only have Linux Webhosting. No Windows.
Don't need Windows to host .net core.
Looks like I am ill-informed, It wouldn't be something that I support.
Works fine - I have a bunch of NAT VPSes powering ping/traceroutes on https://beta.dnstools.ws/, using .NET Core 3.0.
Should work on any Linux distro. I use Debian 10 and followed the instructions at https://docs.microsoft.com/en-us/dotnet/core/install/linux-package-manager-debian10 to add the repo and install the runtime (don't install the SDK as it takes up a bunch of space, just get the runtime)
The other option is to publish your app with a self-contained runtime (
dotnet publish --self-contained -c Release -r linux-x64), then you don't need to install anything on the VPS as everything will be in the publish directory. Just copy over the publish directory usingrsyncor SCP/SFTP and run the appHowever, if you do use .NET Core 3.0, note that there is a bug where it locks up or segfaults on OpenVZ. I posted a workaround here: https://github.com/dotnet/coreclr/issues/27955 and https://github.com/dotnet/coreclr/issues/26873. The bug isn't present in .NET Core 2.2, just 3.0.
Thanks but I was specifically asking for the Webhosting. Setting net core up on a vps is no biggie.
@Cam i think your Guide to host a website on ur nat vps is outdated.
Probably not, but it requires delegating the whole domain to cloudflare, which I didn't want to do, I was fine with serving the website on a high port number.
But please note, if you want ssl with let's encrypt, they need to validate on port 80 or 443 -- and this not a problem, as long as you configure the server to listen on 80 and 443 on ipv6 or use certbot --standalone (don't forget your aaaa record). Once you have your cert, you can serve an ssl encrypted website on whatever ipv4 port you want.
Congrats on your first comment
(You chose a safe username)
You can do DNS validation rather than HTTP validation, then your host doesn't even need to be accessible publicly (so you can use Let's Encrypt for services that aren't exposed to the public internet). You also need to use DNS validation if you want to obtain wildcard certs. I use acme-dns.