@natvps_uk said:
We have disabled vswap for instances users on the UK nodes, this was being heavily abused by people creating 64MB instances and forcing everything into swap. As this node is on HDDs it was impacting the limited disk performance fairly substantially.
Instances should be provisioned with the amount of resources that you require and not intentionally underspec'd.
Ubuntu 22.04 apt update command crashes on 64MB without swap, even if I stopped everything.
I think it should be acceptable to use some swap during installation and upgrades, but not during normal operation.
I deleted UK instance and created Germany instances, which has swap.
There's no way to modify a loadbalancer, so I have to delete and re-create it too.
This causes downtime because TLS certificate isn't provisioned on the new loadbalancer right away.
In an attempt to reproduce the apt update failure, I created another UK instance but it has swap again.
Does this mean the UK SSD node has arrived?
Having the same problem. Not able to install security updates.
Createt a ticket a while ago... still no reply :-(
@natvps_uk said: We have disabled vswap for instances users on the UK nodes, this was being heavily abused by people creating 64MB instances and forcing everything into swap.
Maybe you should offer 280MB ram as minimum. locale-gen will fail because of OOM in 256MB VPS.
@natvps_uk said: We have disabled vswap for instances users on the UK nodes, this was being heavily abused by people creating 64MB instances and forcing everything into swap.
Maybe you should offer 280MB ram as minimum. locale-gen will fail because of OOM in 256MB VPS.
Or you may limit the OS to alpine.
It’s down to the user to decide how much ram they want. We originally limited it to 128MB and we got complaints so reduced it 64MB.
Users can upgrade their resources at anytime for VPS clients they just need to open a ticket and we will invoice accordingly. For instance users they just need to reprovision their instance with the resources that they require.
Keep in mind that all locations other than our UK nodes come with 256Mb Vswap as standard.
@Ympker said:
I am running 2x128mb vps ubuntu 20.04. No issues
It's not only about running, and I'm sure your vps are running stably with 128MB.
Some installations or updates need more ram than just running the service.
I wish there could be something like ram burst, which temporarily assigns more ram from host, say 256MB more ram for 1 minute, and only once weekly (to prevent abuse).
@bliss said:
Some installations or updates need more ram than just running the service.
I wish there could be something like ram burst, which temporarily assigns more ram from host, say 256MB more ram for 1 minute, and only once weekly (to prevent abuse).
Yes, that's the instance editing feature they is coming soon™.
The resources would come from your credit.
The idea is keeping a portion of your credit(s) unallocated, so that you can add the reserve resources to one instance at a time during upgrades.
Still not enough?
Buy more credits!
This is already better than most other VPS providers.
@natvps_uk said:
Loadbalancer and instance editing is coming very soon.
This will allow you to add additional RAM to an instance for maintenance then remove it afterwards.
if I install WG on 64MB ram just for simple web browsing/ YT streaming (total of 5 hours per day at most) and ssh to my other vms, will it be abusing the server? can it handle the task?
if that's a problem then i would re-create it with 128MB
@yoursunny said:
There's no way to modify a loadbalancer, so I have to delete and re-create it too.
This causes downtime because TLS certificate isn't provisioned on the new loadbalancer right away.
It's been 8 hours and the new loadbalancer still hasn't provisioned TLS certificate.
$ curl -i https://summer-host-storage.yoursunny.dev/robots.txt
curl: (60) SSL: no alternative certificate subject name matches target host name 'summer-host-storage.yoursunny.dev'
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
if I install WG on 64MB ram just for simple web browsing/ YT streaming (total of 5 hours per day at most) and ssh to my other vms, will it be abusing the server? can it handle the task?
if that's a problem then i would re-create it with 128MB
I am running ovpn+wg on a 128mb ram vps just fine. 64mb would probably work just as well for wg
@AuroraZero said:
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
What the hell did I do wrong?
Just checked and its working as expected.
You need to either point a cname record to your endpoint or ping the endpoint, grab the IP and point your hostfile at it.
@AuroraZero said:
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
What the hell did I do wrong?
Just checked and its working as expected.
You need to either point a cname record to your endpoint or ping the endpoint, grab the IP and point your hostfile at it.
@AuroraZero said:
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
What the hell did I do wrong?
Oh, you pointed DNS at the node rather than the loadbalancer. That explains why its not working!
@AuroraZero said:
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
What the hell did I do wrong?
Oh, you pointed DNS at the node rather than the loadbalancer. That explains why its not working!
@AuroraZero said:
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
@AuroraZero said:
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
What the hell did I do wrong?
Oh, you pointed DNS at the node rather than the loadbalancer. That explains why its not working!
No DNS just a subdomain or won't that work?
That’s fine, just set the target to the endpoint address. You need to use a cname record.
@AuroraZero said:
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
@AuroraZero said:
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
What the hell did I do wrong?
Oh, you pointed DNS at the node rather than the loadbalancer. That explains why its not working!
No DNS just a subdomain or won't that work?
That’s fine, just set the target to the endpoint address. You need to use a cname record.
@yoursunny said: Yes, that's the instance editing feature they is coming soon™.
This is now live for RAM only, disk will follow soon.
Currently only enabled for UK and CA although all other nodes will follow in the coming days.
I tried the editing in Beauharnois.
RAM hotplug without reboot works like magic.
Looking at top, it's 64MB one second and 320MB the next second.
Capacity of /run/shm is half of RAM during boot.
It does not change upon resizing.
If I fill 160MB into /run/shm and change to 64MB RAM, the excess gets dumped into swap.
Looks reasonable.
A minor bug: right now we can get big container with small credits:
Create 320MB container in Limburg.
Open /upgraderam?id=<> endpoint and change RAM to 64MB.
The change succeeds, 256MB credit is freed up and can be used to create other containers, but the Limburg container stays at 320MB.
I consider this minor bug because as soon as the RAM editing is fully deployed, the pending changes would be processed and oversized containers would return to configured size.
@yoursunny said:
I consider this minor bug because as soon as the RAM editing is fully deployed, the pending changes would be processed and oversized containers would return to configured size.
This is hotfixed now, any servers with wrongly allocated ram will be corrected when the worker is started for the remaining locations later today.
We're setting up a new UK node currently. This will be very low stock and only available for VPS customers.
Would anyone be interested in the following:
Single Core Xeon E3 V2
1GB RAM
60GB SSD Cached Storage
Gigabit Port 1000mbps upload 1000mbps download
NAT IPV4 (20 Ports)
Unmetered Bandwidth (Fair Use)
/48 IPv6
Location Coventry UK.
£13 per year.
I realise this isn't as cheap as out other offerings although this is not hosted in OVH, comes with a /48 and is on a Gigabit port with no restrictions. If there is no interest we will split it up further and push our our usual deals.
@natvps_uk said:
We're setting up a new UK node currently. This will be very low stock and only available for VPS customers.
Would anyone be interested in the following:
Single Core Xeon E3 V2
1GB RAM
60GB SSD Cached Storage
Gigabit Port 1000mbps upload 1000mbps download
NAT IPV4 (20 Ports)
Unmetered Bandwidth (Fair Use)
/48 IPv6
Location Coventry UK.
£13 per year.
I realise this isn't as cheap as out other offerings although this is not hosted in OVH, comes with a /48 and is on a Gigabit port with no restrictions. If there is no interest we will split it up further and push our our usual deals.
Comments
DM me the ticket number, I’ll take a look.
Maybe you should offer 280MB ram as minimum.
locale-genwill fail because of OOM in 256MB VPS.Or you may limit the OS to alpine.
MicroLXC is lovable. Uptime of C1V
It’s down to the user to decide how much ram they want. We originally limited it to 128MB and we got complaints so reduced it 64MB.
Users can upgrade their resources at anytime for VPS clients they just need to open a ticket and we will invoice accordingly. For instance users they just need to reprovision their instance with the resources that they require.
Keep in mind that all locations other than our UK nodes come with 256Mb Vswap as standard.
I am running 2x128mb vps ubuntu 20.04. No issues
Ympker's VPN LTD Comparison, Uptime.is, Ympker's GitHub.
It's not only about running, and I'm sure your vps are running stably with 128MB.
Some installations or updates need more ram than just running the service.
I wish there could be something like ram burst, which temporarily assigns more ram from host, say 256MB more ram for 1 minute, and only once weekly (to prevent abuse).
MicroLXC is lovable. Uptime of C1V
Yes, that's the instance editing feature they is coming soon™.
The resources would come from your credit.
The idea is keeping a portion of your credit(s) unallocated, so that you can add the reserve resources to one instance at a time during upgrades.
Still not enough?
Buy more credits!
This is already better than most other VPS providers.
HostBrr aff best VPS; VirmAche aff worst VPS.
Unable to push-up due to shoulder injury 😣
genuinely asking:
if I install WG on 64MB ram just for simple web browsing/ YT streaming (total of 5 hours per day at most) and ssh to my other vms, will it be abusing the server? can it handle the task?
if that's a problem then i would re-create it with 128MB
wg uses next to nothing, I used to run 60 wg tunnels on 256MB machines.
Free NAT KVM | Free NAT LXC | Bobr
It's been 8 hours and the new loadbalancer still hasn't provisioned TLS certificate.
HostBrr aff best VPS; VirmAche aff worst VPS.
Unable to push-up due to shoulder injury 😣
I am running ovpn+wg on a 128mb ram vps just fine. 64mb would probably work just as well for wg
Ympker's VPN LTD Comparison, Uptime.is, Ympker's GitHub.
Micronode 1.3.4 Released!
Changelog
Added:
Changed:
Fixed:
This is now live for RAM only, disk will follow soon.
Currently only enabled for UK and CA although all other nodes will follow in the coming days.
Ok someone explain to me this load blanacer. I created one pointed the backend to my vps and connection refused. Disabled the firewall same thing.
What the hell did I do wrong?
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
Just checked and its working as expected.
You need to either point a cname record to your endpoint or ping the endpoint, grab the IP and point your hostfile at it.
DM me if you get stuck
The first half of this Knowledge base article covers the setup: https://clients.natvps.uk/index.php?rp=/knowledgebase/5/Installing-Wordpress-on-Micronode-Instances.html
Oh, you pointed DNS at the node rather than the loadbalancer. That explains why its not working!
No DNS just a subdomain or won't that work?
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
That’s fine, just set the target to the endpoint address. You need to use a cname record.
Thank you man sorted
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
I tried the editing in Beauharnois.
RAM hotplug without reboot works like magic.
Looking at
top, it's 64MB one second and 320MB the next second.Capacity of
/run/shmis half of RAM during boot.It does not change upon resizing.
If I fill 160MB into
/run/shmand change to 64MB RAM, the excess gets dumped into swap.Looks reasonable.
A minor bug: right now we can get big container with small credits:
/upgraderam?id=<>endpoint and change RAM to 64MB.I consider this minor bug because as soon as the RAM editing is fully deployed, the pending changes would be processed and oversized containers would return to configured size.
HostBrr aff best VPS; VirmAche aff worst VPS.
Unable to push-up due to shoulder injury 😣
This is hotfixed now, any servers with wrongly allocated ram will be corrected when the worker is started for the remaining locations later today.
Do you still offer the http/https proxy services or is everything through the load balancer service?
Load balancer all the way!
HostBrr aff best VPS; VirmAche aff worst VPS.
Unable to push-up due to shoulder injury 😣
I bought one today
nice vps
Oh no. you're taking away our resources
Stop it...
We're setting up a new UK node currently. This will be very low stock and only available for VPS customers.
Would anyone be interested in the following:
Single Core Xeon E3 V2
1GB RAM
60GB SSD Cached Storage
Gigabit Port 1000mbps upload 1000mbps download
NAT IPV4 (20 Ports)
Unmetered Bandwidth (Fair Use)
/48 IPv6
Location Coventry UK.
£13 per year.
I realise this isn't as cheap as out other offerings although this is not hosted in OVH, comes with a /48 and is on a Gigabit port with no restrictions. If there is no interest we will split it up further and push our our usual deals.
YABS:
fio Disk Speed Tests (Mixed R/W 50/50):
iperf3 Network Speed Tests (IPv4):
nice offer.
i am tempted.
Me too
✨🎁 Low end deals Telegram tracker: https://t.me/lowendweb
Will 128-nat-uk be available？