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
The feature should be live soon.
Nice!
What is this error
wrong your options
It looks like I made a typo somewhere. However, it says I am using a vpn, while I am not.
"IPHub VPN detected."
Make sure your VPN is disabled.
Can't check on your request or ip, since rejected requests are deleted once they get rejected.
The problem is, I don't have any VPN installed and iplocation.io also outputs my home IP
Indeed, it was a technical error, will be fixed in the next patch.
Restocked Singapore
c1f0-f345-9dac-59ea
very nice
❤️
🫰🏽
Patchnotes
- Nested Support for Docker and LXC
- Less Strict VPN Check
- Reworked Tasks
- A few smol UI changes
Forgot to mention, that the current numproc limit is 150.
I reckon that could be a issue if you run Docker or another LXC container.
I set it to 500 for new deployments.
If anyone hits the limit lemme know and I up it.
I'm using Tokyo tiny but am considering Singapore...
(I also use FreeVPS.org's Tokyo server, so that's good enough)
Anyone looking for Tokyo?
first of all, thanks a lot!
2e98-f0b4-f41d-63c6
of course I had to mess it up
aa73-14e0-8961-f308
Is the Bandwidth of micro different depending on the node?
Or is every node fixed at 200GB?
It depends on the Package and the Location.
The Default allocation is 200GB.
NL/NO have higher allocations, even a few TB.
JP for example only has 1TB of Traffic.
If you give me the Location and Package, I can check if I can increase it.
I agree. The specs of Asia Note will be tough.
I'm also considering other Nodes.
Asia in general is thin.
Most of Nodes only have 1-2TB of Traffic.
I checked on the allocations the Nodes have, the things I could do out of the box:
If you have a specific Location in mind, I can ask if they would increase our Traffic allocation, so I could increase the Package allocation.
Thank you @Neoon . I moved to Sandefjord Node.
(After Terminate , you will be able to Launch , and at this time you can select a new Node)
To you who saw this. I moved from Tokyo, so you have a chance to launch Tokyo Node..
Hi.
Token: 6fd5-4135-b354-ecd9
I like LXC. Going to use it for some small testing with docker.
When does the bandwidth usage get calculated?
Hourly
Johannesburg had an unexpected reboot, this resulted in the API being offline.
Containers where running, however you could not control them via the dashboard, fixed.
Patchnotes
- Fixed, If a host system had less than 256MB free, the stock system still displayed the 256MB Package despite its not available
- Tasks now shows the correct Information if you got more than one Container or Virtual Machine, was broken since the last update
- Packages are finally sorted by Memory
- Packages with limited quantity are now available
To test this feature, I added a new 777 Package for Singapore.
Its limited to 2 concurrent deployments will restock if the user decides to terminate.
What happens in Norway ?
Routes are flapping, sure @terrahost is already on it.
Nothing I can do here, their NOC has to handle it.
edit: https://terrahoststatus.com/issue/18b32d7b-853c-4c6e-8d0c-37a8e8a8ef85
Would anyone be interested to see microLXC switching to a resource pool based allocation instead of the current slot allocation?
Its done, the buildserver just passed all test with the resource pool change
If you have your quota set to 1, it would be converted to 1024MB.
You would be able to spend the allocation freely, without any limitations, right now, as long the location has stock.
However, we have a few small nodes, which brings up a concern, that these may get hammered.
Hence I probably make them more expensive, so your cost would be times 2, in rare locations.
This would not impact or make the current slot limit worse and incentivize people to not deploy everything in these locations.
I also have considered, a cost increase if you deploy more than 1 container in a location, but I leave that out for now.
Ideas?