@gomi said: and i found that a little bit complicated for beginners
This is is what it looks like at first (especially when looking at the screenshots), but step by step you comprehend it.
yeh,when i get the first one, i found it's more user-friendly than the management interfaces of many VPS providers.
We did have a toggle switch "Easy | Standard | pro" But no one could agree what went in each, different people know different things, we did all agree that Easy should be "Vps Instances, Support, Billing, Account Setting" only and that becomes the default... butthen maybe people dont notice the toggle swicth or never click it and never see the features... so tbh, in the end we just removed it.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try. FREE tokens when you sign up, try before you buy.
@ahnlak said:
If you create a new instance and set your DNS Resolvers to OpenDNS, it seems to break DNS - their resolvers appear to be configured on the VPS end, so I'm guessing it's breaking somewhere in the NAT?
(I would investigate further, but without DNS I can't install any net tools to explore!)
cant replicate, just deployed a fresh VPS, backend config is fine, vps config is fine, can resolve fine, can I suggest simply changing to google locally on the VPS while you troubleshoot? or if it persists please open a ticket and connect the VPS to the ticket so we can backtrace.
Thanks!
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try. FREE tokens when you sign up, try before you buy.
Questions:
1) will you add the ability to increase the number of vCPUs in the future?
2) when/where will be the future servers' locations?
3) do you have any published roadmap?
4) any plan to create some documentation (I am thinking especially for guidance about the creation of Recipes)?
5) any plan to create its own community (forum)? Or will LES become the defacto place?
6) any plan to have an API?
🤡 "We can confirm that this is not an issue with any servers, network, or power equipment on our end." 🤡 "We have temporarily paused controls for this service as we are performing maintenance on the server." 🤡 "The servers are working, they are just not connected to the internet!" 🤡
Questions:
1) will you add the ability to increase the number of vCPUs in the future?
2) when/where will be the future servers' locations?
3) do you have any published roadmap?
4) any plan to create some documentation (I am thinking especially for guidance about the creation of Recipes)?
5) any plan to create its own community (forum)? Or will LES become the defacto place?
6) any plan to have an API?
Probably when we move everything to dual EPYC we will just give 2 cores as standard and maximum, honestly if you need more, this is not the right service for you.
Every OVH + Hetzner location is the first goal, if any LE hosts offer us a deal we cant resist then there too
We ran out of road at "Make it available to the public" if this test goes well we will start adding to it (This is not the only thing we are working on) if this does not pay for itself or have enough interest, we will refund and shut it down and probably just open source it.
Yes, actually a bit of its written and there will also be a blog section showing real-world examples and use cases with step-by-step instructions.
Yeah I thought about that, it would be trivial to integrate a forum directly into the panel, actually, nothing fancy, but possible, i dont want to take away from LES though, might be a weekend project when we hit burn out with everything else.
We have one, I just made the decision not to expose it on day 1, this has actually been built with an API first mindset, because if/when it goes to beta, there will be a full command-line version that will rely on the API.
This is a very human-level project; it's not trying to be enterprise, and all our eggs are not in this basket, but it is something I VERY much hope works out, as long as it covers its own costs it will exist.
@ahnlak said:
If you create a new instance and set your DNS Resolvers to OpenDNS, it seems to break DNS - their resolvers appear to be configured on the VPS end, so I'm guessing it's breaking somewhere in the NAT?
(I would investigate further, but without DNS I can't install any net tools to explore!)
cant replicate, just deployed a fresh VPS, backend config is fine, vps config is fine, can resolve fine, can I suggest simply changing to google locally on the VPS while you troubleshoot? or if it persists please open a ticket and connect the VPS to the ticket so we can backtrace.
Thanks!
Hmm; might be Debian13 being ... debian, but I'll see if I can track it down further!
Might be location dependent - CA works fine, but London borks. I think it's OpenDNS rejecting queries, possibly rate-limiting because the NAT sends all the traffic out of the same IP?
@ahnlak said:
If you create a new instance and set your DNS Resolvers to OpenDNS, it seems to break DNS - their resolvers appear to be configured on the VPS end, so I'm guessing it's breaking somewhere in the NAT?
(I would investigate further, but without DNS I can't install any net tools to explore!)
cant replicate, just deployed a fresh VPS, backend config is fine, vps config is fine, can resolve fine, can I suggest simply changing to google locally on the VPS while you troubleshoot? or if it persists please open a ticket and connect the VPS to the ticket so we can backtrace.
Thanks!
Hmm; might be Debian13 being ... debian, but I'll see if I can track it down further!
I also used Debian 13
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try. FREE tokens when you sign up, try before you buy.
Haha well I don't know if you have signed up yet but if you think about how we do it, you get your subnet and meshed bridges between locations already before you even have a VPS, everything is network first service on top.
So you can probably imagine using some sort of BGP interface on your network page and being able to pin subnets or IPs etc which then becomes available for you to use.
Same idea for ipv6 when that's added.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try. FREE tokens when you sign up, try before you buy.
Haha well I don't know if you have signed up yet but if you think about how we do it, you get your subnet and meshed bridges between locations already before you even have a VPS, everything is network first service on top.
So you can probably imagine using some sort of BGP interface on your network page and being able to pin subnets or IPs etc which then becomes available for you to use.
Same idea for ipv6 when that's added.
No we mean announcing our own prefixes and asn externally.
We're the source, no cap. Address us: We/Our/Ours.
@backtogeek said: Probably when we move everything to dual EPYC we will just give 2 cores as standard and maximum, honestly if you need more, this is not the right service for you.
1vCPU as standard is fine, but I can see that you made it working for Web Hosting APPS (WordPress) and this can be CPU hungry.
🤡 "We can confirm that this is not an issue with any servers, network, or power equipment on our end." 🤡 "We have temporarily paused controls for this service as we are performing maintenance on the server." 🤡 "The servers are working, they are just not connected to the internet!" 🤡
Congratulations on a really nice next level NAT project, Ant. I thought you were planning on slowing the pace in your "old age". Then you come up with this ^. Some people can't sit still, I guess. Wishing you the best
@bmoto said:
Congratulations on a really nice next level NAT project, Ant. I thought you were planning on slowing the pace in your "old age". Then you come up with this ^. Some people can't sit still, I guess. Wishing you the best
Thanks, well the big difference is, if this does not work out, I wont lose any sleep, it was fun.
Registrations locked, sadly, the free token is just attracting half of China, and it's more work manually checking and closing accounts than it's worth, so we are going to have to change it up.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try. FREE tokens when you sign up, try before you buy.
We are looking at options. Sadly, people spoil things for the good guys and don't understand the true cost of abuse on small startups and businesses. We are not Amazon.
I had other things to do; I have spent 2 days in the background working on preventing abuse, not a good use of my time right now.
Right now, the tokens have been reduced to 0.25 for new sign-ups, and they will expire after 60 days.
And we will add other ways to get free tokens that require a small bit of effort or exchange, kind of like Digital Ocean did when they started, a tweet, a backlink, a referal link or something, i dont know right now, I am focusing on stripping out the 100's of China accounts.
but also, its day 5? (I think) of a public Alpha... so it's good data I guess.
OK, long day, but we have opened the registrations again, reduced to 0.25, we are not going to touch any of the current issued tokens, don't worry (Unless you registered a bunch of accounts, in which case you now have 0).
We were going to time-limit the use of free tokens, but we decided against that in the end.
Trying to strike a balance that allows good people to test it fully without making it far too tempting to the people who love free chicken!
As a reminder, we don't accept REGISTRATIONS from CN, BR, VN, RU, IR or people physically there using a proxy or VPN, or from disposable emails.
Comments
We did have a toggle switch "Easy | Standard | pro" But no one could agree what went in each, different people know different things, we did all agree that Easy should be "Vps Instances, Support, Billing, Account Setting" only and that becomes the default... butthen maybe people dont notice the toggle swicth or never click it and never see the features... so tbh, in the end we just removed it.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
cant replicate, just deployed a fresh VPS, backend config is fine, vps config is fine, can resolve fine, can I suggest simply changing to google locally on the VPS while you troubleshoot? or if it persists please open a ticket and connect the VPS to the ticket so we can backtrace.
Thanks!
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
@backtogeek
Questions:
1) will you add the ability to increase the number of vCPUs in the future?
2) when/where will be the future servers' locations?
3) do you have any published roadmap?
4) any plan to create some documentation (I am thinking especially for guidance about the creation of Recipes)?
5) any plan to create its own community (forum)? Or will LES become the defacto place?
6) any plan to have an API?
🤡 "We can confirm that this is not an issue with any servers, network, or power equipment on our end." 🤡 "We have temporarily paused controls for this service as we are performing maintenance on the server." 🤡 "The servers are working, they are just not connected to the internet!" 🤡
This is a very human-level project; it's not trying to be enterprise, and all our eggs are not in this basket, but it is something I VERY much hope works out, as long as it covers its own costs it will exist.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
Hmm; might be Debian13 being ... debian, but I'll see if I can track it down further!
Might be location dependent - CA works fine, but London borks. I think it's OpenDNS rejecting queries, possibly rate-limiting because the NAT sends all the traffic out of the same IP?
You're going to let people be your downstream?!
We are listening
We're the source, no cap. Address us: We/Our/Ours.
https://lowendspirit.com/discussion/comment/221016/#Comment_221016
I also used Debian 13
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
Haha well I don't know if you have signed up yet but if you think about how we do it, you get your subnet and meshed bridges between locations already before you even have a VPS, everything is network first service on top.
So you can probably imagine using some sort of BGP interface on your network page and being able to pin subnets or IPs etc which then becomes available for you to use.
Same idea for ipv6 when that's added.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
No we mean announcing our own prefixes and asn externally.
We're the source, no cap. Address us: We/Our/Ours.
https://lowendspirit.com/discussion/comment/221016/#Comment_221016
oh.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
1vCPU as standard is fine, but I can see that you made it working for Web Hosting APPS (WordPress) and this can be CPU hungry.
🤡 "We can confirm that this is not an issue with any servers, network, or power equipment on our end." 🤡 "We have temporarily paused controls for this service as we are performing maintenance on the server." 🤡 "The servers are working, they are just not connected to the internet!" 🤡
Congratulations on a really nice next level NAT project, Ant. I thought you were planning on slowing the pace in your "old age". Then you come up with this ^. Some people can't sit still, I guess. Wishing you the best
Thanks, well the big difference is, if this does not work out, I wont lose any sleep, it was fun.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
Registrations locked, sadly, the free token is just attracting half of China, and it's more work manually checking and closing accounts than it's worth, so we are going to have to change it up.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
Disable the free token? :-)
We are looking at options. Sadly, people spoil things for the good guys and don't understand the true cost of abuse on small startups and businesses. We are not Amazon.
I had other things to do; I have spent 2 days in the background working on preventing abuse, not a good use of my time right now.
Right now, the tokens have been reduced to 0.25 for new sign-ups, and they will expire after 60 days.
And we will add other ways to get free tokens that require a small bit of effort or exchange, kind of like Digital Ocean did when they started, a tweet, a backlink, a referal link or something, i dont know right now, I am focusing on stripping out the 100's of China accounts.
but also, its day 5? (I think) of a public Alpha... so it's good data I guess.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
OK, long day, but we have opened the registrations again, reduced to 0.25, we are not going to touch any of the current issued tokens, don't worry (Unless you registered a bunch of accounts, in which case you now have 0).
We were going to time-limit the use of free tokens, but we decided against that in the end.
Trying to strike a balance that allows good people to test it fully without making it far too tempting to the people who love free chicken!
As a reminder, we don't accept REGISTRATIONS from CN, BR, VN, RU, IR or people physically there using a proxy or VPN, or from disposable emails.
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.
Curious... how do you identify them
I can understand if you don't want to spill your secret sauce in case people get a clue... so no pressure if you don't want to do so.
We're the source, no cap. Address us: We/Our/Ours.
https://lowendspirit.com/discussion/comment/221016/#Comment_221016
haha, right now... badly, obvious human error, but we are working on some sauce
TierHive - NAT Native - /24 per customer - Lab in the cloud - Free to try.
FREE tokens when you sign up, try before you buy.