Any reviews on layer7.net?

vitobotta · March 9

Does anyone have experience with them? Prices look amazing.

lukast__ · March 9

https://lowendtalk.com/discussion/202377/layer7-review-after-using-them-for-nearly-a-year

vitobotta · March 9

@lukast__ said:
https://lowendtalk.com/discussion/202377/layer7-review-after-using-them-for-nearly-a-year

Thanks, I just read that one and others. Seems like they have a good reputation. Will read a bit more before deciding. I need a VPS with some SSD/NVME storage as well as 1 TB HDD storage for a Nextcloud instance. This would be 7.99/mo which sounds awesome.

itachikonoha · March 9

It depends on case to case basis. I have used it for around 2 months (VDS).

For storage purpose, it is good.

For performance, in the same price range, netcup or prohosting or BEROHOST or Famesystem will yield much better value for money.

So it all boils down to what you'll use for.

I use prohosting sever while mounting 4TB storage from hostc.

Ofcourse it is a bit slow but serves the purpose. It is gaining computation at the expanse of sacrifice of network speed due to mounted storage from different providers.

lukast__ · March 9

@vitobotta said:

@lukast__ said:
https://lowendtalk.com/discussion/202377/layer7-review-after-using-them-for-nearly-a-year

Thanks, I just read that one and others. Seems like they have a good reputation. Will read a bit more before deciding. I need a VPS with some SSD/NVME storage as well as 1 TB HDD storage for a Nextcloud instance. This would be 7.99/mo which sounds awesome.

Oh, and in case you didn't know that, they also offer free test servers for 48 hours, so you can try out first if it's suitable for you.

vitobotta · March 9

@itachikonoha said:
It depends on case to case basis. I have used it for around 2 months (VDS).

For storage purpose, it is good.

For performance, in the same price range, netcup or prohosting or BEROHOST or Famesystem will yield much better value for money.

So it all boils down to what you'll use for.

Yeah it's mostly for storage for a small Nextcloud instance. I ordered a server now. Thanks

itachikonoha · March 9

@vitobotta said:

@itachikonoha said:
It depends on case to case basis. I have used it for around 2 months (VDS).

For storage purpose, it is good.

For performance, in the same price range, netcup or prohosting or BEROHOST or Famesystem will yield much better value for money.

So it all boils down to what you'll use for.

Yeah it's mostly for storage for a small Nextcloud instance. I ordered a server now. Thanks

For storage, they are one of the cheapest with premium quality. You won't regret that I can guarantee. I'll put only hostc above them in terms of value for money.

vitobotta · March 9

@lukast__ said:

@vitobotta said:

@lukast__ said:
https://lowendtalk.com/discussion/202377/layer7-review-after-using-them-for-nearly-a-year

Thanks, I just read that one and others. Seems like they have a good reputation. Will read a bit more before deciding. I need a VPS with some SSD/NVME storage as well as 1 TB HDD storage for a Nextcloud instance. This would be 7.99/mo which sounds awesome.

Oh, and in case you didn't know that, they also offer free test servers for 48 hours, so you can try out first if it's suitable for you.

Oh I didn't notice your second reply in time. Nevermind. I ordered the server now. It's 7.99 so not a big deal if I run into problems and don't like the service. But I read many good reviews so fingers crossed.

vitobotta · March 9

@layer7 Hey, I set up a new server this afternoon, and Nextcloud is now happily syncing data. Everything looks good so far. The server was up and running right away, and the performance is great.

However, there was one confusing bit. When I ordered the server, I had the option to set up the root password. But once the server was ready, I found out that password authentication was already disabled. I had to reset the root password and then noticed from a pop-up that I needed to use a private key I could download from the site to log in.

All is working now, but I had a few frustrating minutes and almost opened a support ticket before figuring it out. My suggestion is to let users upload their own keys or, if you let them set the root password, don't disable password authentication automatically. It can be confusing.

sillycat · March 9

@vitobotta said: All is working now, but I had a few frustrating minutes and almost opened a support ticket before figuring it out. My suggestion is to let users upload their own keys or, if you let them set the root password, don't disable password authentication automatically. It can be confusing.

Once you have to do it once, you get used to it.

I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7! I LOVE LAYER7!

hyperblast · March 9

@vitobotta said:
Does anyone have experience with them? Prices look amazing.

recommended!

vitobotta · March 9

So much love, I am surprised I didn't come across this provider before

layer7 · March 9

@vitobotta said:
@layer7 Hey, I set up a new server this afternoon, and Nextcloud is now happily syncing data. Everything looks good so far. The server was up and running right away, and the performance is great.

However, there was one confusing bit. When I ordered the server, I had the option to set up the root password. But once the server was ready, I found out that password authentication was already disabled. I had to reset the root password and then noticed from a pop-up that I needed to use a private key I could download from the site to log in.

All is working now, but I had a few frustrating minutes and almost opened a support ticket before figuring it out. My suggestion is to let users upload their own keys or, if you let them set the root password, don't disable password authentication automatically. It can be confusing.

Hi,

thank you for the feedback.

You could have saved some frustration moments by reading the accessmail.

Please allow me to copy-paste the very first line in the accessmail:

PLEASE READ THIS EMAIL IN FULL ( yes it really has interesting informations ! ).

and some lines below that:

To protect your server we will not deliver with this message any accessdata.

=> To access your server via SSH, you will need to login the clientarea at {$whmcs_url} and click on your ordered server!

=> Here please click the "Redeem Password" button in the Quickbar navigation on the upper right hand side.

You will be able to download your private key for the ssh authentication and the rootpassword will be shown to you too.

Please be informed that our templates have password authentication deactivated by default. So you must use the ssh key that you downloaded.

After your first login you can enable password authentication if you want. But we suggest to leave it deactivated for enhanced security!

If no one reads accessmails, even they start with this kind of first line... well then.... cant help it ^^;

We do this, because we honor the customers data and privacy. SSH Passwordauth is something that belongs to the past. None of the bigger cloud provider will provide images with password auth enabled. Same with all linux vendor's will not provide password auth enabled images. Both have reasons...

So if a customer really wants to do that, he will have to do it. We will not support him driving his server security down the hill.

As to the customer public key:

Yes, would definitely make sense. But we have limited dev capacity and have to decide what is important or not. And building a function that maybe 10-20% of all customers will use ( because they belong to the customers who are already on key auth ) while 80-90% might be still used to password auth, is not too much sexy for us, as we prefer implementing functions that will be interesting for 80% of the customers.

And lets be honest... logging into the clientarea -> clicking a button -> downloading the private key takes 30 seconds. Then you are logged in and can place your own key if wanted.

100% of customers can do that. While we have here requests of customers what they have to insert into the order mask when asked for a hostname of the server.... what do you think what they will do with us if they find an ssh public key text field...

So the current solution is the lesser evil in my opinion -- for both sides.

lala_th · March 9

@layer7 Taking this opportunity, any promo for storage servers?

vitobotta · March 9

@layer7 said:

@vitobotta said:
@layer7 Hey, I set up a new server this afternoon, and Nextcloud is now happily syncing data. Everything looks good so far. The server was up and running right away, and the performance is great.

However, there was one confusing bit. When I ordered the server, I had the option to set up the root password. But once the server was ready, I found out that password authentication was already disabled. I had to reset the root password and then noticed from a pop-up that I needed to use a private key I could download from the site to log in.

All is working now, but I had a few frustrating minutes and almost opened a support ticket before figuring it out. My suggestion is to let users upload their own keys or, if you let them set the root password, don't disable password authentication automatically. It can be confusing.

Hi,

thank you for the feedback.

You could have saved some frustration moments by reading the accessmail.

Please allow me to copy-paste the very first line in the accessmail:
PLEASE READ THIS EMAIL IN FULL ( yes it really has interesting informations ! ).
and some lines below that:
To protect your server we will not deliver with this message any accessdata.

=> To access your server via SSH, you will need to login the clientarea at {$whmcs_url} and click on your ordered server!

=> Here please click the "Redeem Password" button in the Quickbar navigation on the upper right hand side.

You will be able to download your private key for the ssh authentication and the rootpassword will be shown to you too.

Please be informed that our templates have password authentication deactivated by default. So you must use the ssh key that you downloaded.

After your first login you can enable password authentication if you want. But we suggest to leave it deactivated for enhanced security!
If no one reads accessmails, even they start with this kind of first line... well then.... cant help it ^^;

We do this, because we honor the customers data and privacy. SSH Passwordauth is something that belongs to the past. None of the bigger cloud provider will provide images with password auth enabled. Same with all linux vendor's will not provide password auth enabled images. Both have reasons...

So if a customer really wants to do that, he will have to do it. We will not support him driving his server security down the hill.

As to the customer public key:

Yes, would definitely make sense. But we have limited dev capacity and have to decide what is important or not. And building a function that maybe 10-20% of all customers will use ( because they belong to the customers who are already on key auth ) while 80-90% might be still used to password auth, is not too much sexy for us, as we prefer implementing functions that will be interesting for 80% of the customers.

And lets be honest... logging into the clientarea -> clicking a button -> downloading the private key takes 30 seconds. Then you are logged in and can place your own key if wanted.

100% of customers can do that. While we have here requests of customers what they have to insert into the order mask when asked for a hostname of the server.... what do you think what they will do with us if they find an ssh public key text field...

So the current solution is the lesser evil in my opinion -- for both sides.

Ooops. You're right, I didn't pay attention to that email as I should. I thought it would be the typical email I have seen with many provider with just vps details and terms etc. But it's no excuse. Forget about what I said

First impression with the service are good.

DeusVult · March 9

It is a pretty good provider -- I recommend it

itachikonoha · March 10

@vitobotta said:
@layer7 said:

@vitobotta said:
@layer7 Hey, I set up a new server this afternoon, and Nextcloud is now happily syncing data. Everything looks good so far. The server was up and running right away, and the performance is great.

However, there was one confusing bit. When I ordered the server, I had the option to set up the root password. But once the server was ready, I found out that password authentication was already disabled. I had to reset the root password and then noticed from a pop-up that I needed to use a private key I could download from the site to log in.

All is working now, but I had a few frustrating minutes and almost opened a support ticket before figuring it out. My suggestion is to let users upload their own keys or, if you let them set the root password, don't disable password authentication automatically. It can be confusing.

Hi,

thank you for the feedback.

You could have saved some frustration moments by reading the accessmail.

Please allow me to copy-paste the very first line in the accessmail:
PLEASE READ THIS EMAIL IN FULL ( yes it really has interesting informations ! ).
and some lines below that:
To protect your server we will not deliver with this message any accessdata.

=> To access your server via SSH, you will need to login the clientarea at {$whmcs_url} and click on your ordered server!

=> Here please click the "Redeem Password" button in the Quickbar navigation on the upper right hand side.

You will be able to download your private key for the ssh authentication and the rootpassword will be shown to you too.

Please be informed that our templates have password authentication deactivated by default. So you must use the ssh key that you downloaded.

After your first login you can enable password authentication if you want. But we suggest to leave it deactivated for enhanced security!
If no one reads accessmails, even they start with this kind of first line... well then.... cant help it ^^;

We do this, because we honor the customers data and privacy. SSH Passwordauth is something that belongs to the past. None of the bigger cloud provider will provide images with password auth enabled. Same with all linux vendor's will not provide password auth enabled images. Both have reasons...

So if a customer really wants to do that, he will have to do it. We will not support him driving his server security down the hill.

As to the customer public key:

Yes, would definitely make sense. But we have limited dev capacity and have to decide what is important or not. And building a function that maybe 10-20% of all customers will use ( because they belong to the customers who are already on key auth ) while 80-90% might be still used to password auth, is not too much sexy for us, as we prefer implementing functions that will be interesting for 80% of the customers.

And lets be honest... logging into the clientarea -> clicking a button -> downloading the private key takes 30 seconds. Then you are logged in and can place your own key if wanted.

100% of customers can do that. While we have here requests of customers what they have to insert into the order mask when asked for a hostname of the server.... what do you think what they will do with us if they find an ssh public key text field...

So the current solution is the lesser evil in my opinion -- for both sides.
Ooops. You're right, I didn't pay attention to that email as I should. I thought it would be the typical email I have seen with many provider with just vps details and terms etc. But it's no excuse. Forget about what I said

First impression with the service are good.

I was guilty as well when I bought the first vps. I didn't check the mails.

Same happened with hostbrr DA storage.

There should be some notification that says, READ THAT FRICKING MAIL I JUST SENT YA! because as a client, we tend to ignore mails.

I know it's our fault but little bit of heads up will be nice.

wadhah · March 10

Any provider that disables password auth by default gains my favor a little bit.

@layer7 good decision and I hope more LET hosts follow your path.

vitobotta · March 10

@itachikonoha said:
@vitobotta said:
@layer7 said:

@vitobotta said:
@layer7 Hey, I set up a new server this afternoon, and Nextcloud is now happily syncing data. Everything looks good so far. The server was up and running right away, and the performance is great.

However, there was one confusing bit. When I ordered the server, I had the option to set up the root password. But once the server was ready, I found out that password authentication was already disabled. I had to reset the root password and then noticed from a pop-up that I needed to use a private key I could download from the site to log in.

All is working now, but I had a few frustrating minutes and almost opened a support ticket before figuring it out. My suggestion is to let users upload their own keys or, if you let them set the root password, don't disable password authentication automatically. It can be confusing.

Hi,

thank you for the feedback.

You could have saved some frustration moments by reading the accessmail.

Please allow me to copy-paste the very first line in the accessmail:
PLEASE READ THIS EMAIL IN FULL ( yes it really has interesting informations ! ).
and some lines below that:
To protect your server we will not deliver with this message any accessdata.

=> To access your server via SSH, you will need to login the clientarea at {$whmcs_url} and click on your ordered server!

=> Here please click the "Redeem Password" button in the Quickbar navigation on the upper right hand side.

You will be able to download your private key for the ssh authentication and the rootpassword will be shown to you too.

Please be informed that our templates have password authentication deactivated by default. So you must use the ssh key that you downloaded.

After your first login you can enable password authentication if you want. But we suggest to leave it deactivated for enhanced security!
If no one reads accessmails, even they start with this kind of first line... well then.... cant help it ^^;

We do this, because we honor the customers data and privacy. SSH Passwordauth is something that belongs to the past. None of the bigger cloud provider will provide images with password auth enabled. Same with all linux vendor's will not provide password auth enabled images. Both have reasons...

So if a customer really wants to do that, he will have to do it. We will not support him driving his server security down the hill.

As to the customer public key:

Yes, would definitely make sense. But we have limited dev capacity and have to decide what is important or not. And building a function that maybe 10-20% of all customers will use ( because they belong to the customers who are already on key auth ) while 80-90% might be still used to password auth, is not too much sexy for us, as we prefer implementing functions that will be interesting for 80% of the customers.

And lets be honest... logging into the clientarea -> clicking a button -> downloading the private key takes 30 seconds. Then you are logged in and can place your own key if wanted.

100% of customers can do that. While we have here requests of customers what they have to insert into the order mask when asked for a hostname of the server.... what do you think what they will do with us if they find an ssh public key text field...

So the current solution is the lesser evil in my opinion -- for both sides.
Ooops. You're right, I didn't pay attention to that email as I should. I thought it would be the typical email I have seen with many provider with just vps details and terms etc. But it's no excuse. Forget about what I said

First impression with the service are good.
I was guilty as well when I bought the first vps. I didn't check the mails.

Same happened with hostbrr DA storage.

There should be some notification that says, READ THAT FRICKING MAIL I JUST SENT YA! because as a client, we tend to ignore mails.

I know it's our fault but little bit of heads up will be nice.

Yeah I agree. My surprise was due to the fact that I haven't seen this practice before. Of course I always disable password auth when I set up a new server, as everyone should, but I didn't expect it to be done by default on a new server or at least I have never seen this before.

layer7 · March 10

@vitobotta said:
Ooops. You're right, I didn't pay attention to that email as I should. I thought it would be the typical email I have seen with many provider with just vps details and terms etc. But it's no excuse. Forget about what I said

Hi,

no problem. You are in good ~ 90% company :-)

And yes, i can perfectly imagine that most of the hosters will give it with password enabled. Simply for the simplicity of the customers and to reduce the tickets count.

@lala_th said:
@layer7 Taking this opportunity, any promo for storage servers?

we are actually preparing a special promo, especially for this forum, especially for the active users.

@itachikonoha said:
There should be some notification that says, READ THAT FRICKING MAIL I JUST SENT YA! because as a client, we tend to ignore mails.

Honestly i was already thinking about putting something in the subject with bad words like RTFM to be allowed to open tickets and similar.

But we actually also cater customers/companies who pay a bit more than the 7 USD/year. Aside of the fact that they will really feel insulted and not understand this as a joke, in fact this kind of customers tend to actually read what you write them...

So for now... no better idea but what we have.

ArrowBoi · March 10

@vitobotta said:
Does anyone have experience with them? Prices look amazing.

Yup, used them for 2-3 months. Performance worked good! Support on telegram was quick too.

Just295 · March 10

Afternoon,
I have been with Layer7.net for one year next week. I tested the vm with several different software setups, different OS's, some video encoding, and some more, I can say I am very happy with the network and server speeds, at the very least for my needs.

Cloud Server - Mid CPU 3Cores-16GB-120GB FRA1 is what I have.

If anyone wants to do some download/speed tests.

https://layer7-fra1.downloadspeeds.xyz/

Thanks,
Anthony

admax · March 10

I have been using the Layer7.net server for over a year now! It's been great the whole time!

vitobotta · March 10

Thanks all! Looks like this provider was a nice find! I am very happy with my server so far. Sure it's been only a couple of days but all the positive reviews I have seen so far are promising I will likely migrate other stuff from other providers.

remy · March 10

@vitobotta said:
Thanks all! Looks like this provider was a nice find! I am very happy with my server so far. Sure it's been only a couple of days but all the positive reviews I have seen so far are promising I will likely migrate other stuff from other providers.

Didn't manage to keep a single vps?
I can understand you!

vitobotta · March 10

Guys what is your upstream speed like? Uploading from my Mac to the VPS via Nextcloud almost maxed out my Gigabit connection (I have a 1000/1000 connection), but when that finished and I started downloading all the data from the server to another machine, also with Gigabit connection, it's downloading at less than 10MB/sec, usually around 4MB/sec. I checked with iperf and transferring from the server confirms max 97 Mbps, which is surprising because the connection with the server I bought is supposed to be up to 1000. I know what "up to means", but I wasn't expecting less than 100 either. Should I open a ticket?

lukast__ · March 10

@vitobotta said:
Guys what is your upstream speed like? Uploading from my Mac to the VPS via Nextcloud almost maxed out my Gigabit connection (I have a 1000/1000 connection), but when that finished and I started downloading all the data from the server to another machine, also with Gigabit connection, it's downloading at less than 10MB/sec, usually around 4MB/sec. I checked with iperf and transferring from the server confirms max 97 Mbps, which is surprising because the connection with the server I bought is supposed to be up to 1000. I know what "up to means", but I wasn't expecting less than 100 either. Should I open a ticket?

My guess would be that it's some peering issue. I'd recommend that you check with YABS/nws.sh/something else if you get the speeds you should get to other servers, if not, it would seem like it's limited and you should open a ticket, but if you reach gigabit speeds to other servers, you could open a ticket with MTRs/traceroutes, but sometimes the provider also can't change anything.
I'm always reaching the advertised speeds on my Layer7 VPSes in benchmarks.
Edit: and you could also try TCP BBR.

vitobotta · March 10

Uhm could it be a problem with the routing between Germany and Finland, where I live? I tried iperf with another server in Germany (GreenCloud) and the transfer speed is actually around 100 MB/sec which is what I'd expect with a Gigabit connection. But when transferring data to my home I only get a few MB/sec. What can I do?

vitobotta · March 10

@lukast__ said:

@vitobotta said:
Guys what is your upstream speed like? Uploading from my Mac to the VPS via Nextcloud almost maxed out my Gigabit connection (I have a 1000/1000 connection), but when that finished and I started downloading all the data from the server to another machine, also with Gigabit connection, it's downloading at less than 10MB/sec, usually around 4MB/sec. I checked with iperf and transferring from the server confirms max 97 Mbps, which is surprising because the connection with the server I bought is supposed to be up to 1000. I know what "up to means", but I wasn't expecting less than 100 either. Should I open a ticket?

My guess would be that it's some peering issue. I'd recommend that you check with YABS/nws.sh/something else if you get the speeds you should get to other servers, if not, it would seem like it's limited and you should open a ticket, but if you reach gigabit speeds to other servers, you could open a ticket with MTRs/traceroutes, but sometimes the provider also can't change anything.
I'm always reaching the advertised speeds on my Layer7 VPSes in benchmarks.
Edit: and you could also try TCP BBR.

yeah like I mentioned in my previous post it seems a problem with the connection to my home in Finland, because with another server I do get Gigabit speed. I am not familiar with TCP BBR, can you clarify a bit? Thanks

lukast__ · March 10

@vitobotta said: I am not familiar with TCP BBR, can you clarify a bit? Thanks

The easiest would be (needs to be run on every boot) (one can tune way more network related things, but this is usually enough):

echo fq > /proc/sys/net/core/default_qdisc
echo bbr > /proc/sys/net/ipv4/tcp_congestion_control

If that doesn't change anything, you could try to do both way MTRs/traceroutes, and open a ticket, but sometimes the provider also can't change anything.

vitobotta · March 10

@lukast__ said:

@vitobotta said: I am not familiar with TCP BBR, can you clarify a bit? Thanks

The easiest would be (needs to be run on every boot) (one can tune way more network related things, but this is usually enough):
echo fq > /proc/sys/net/core/default_qdisc
echo bbr > /proc/sys/net/ipv4/tcp_congestion_control
If that doesn't change anything, you could try to do both way MTRs/traceroutes, and open a ticket, but sometimes the provider also can't change anything.

Interesting! With this change upload speed went from 4-5 MB/sec to 15-16 MB/sec so it's a nice improvement. Still far from Gigabit speed though. I'll test a bit more and perhaps open a ticket. Thanks for the awesome suggestion!

Howdy, Stranger!

Categories

In this Discussion

Any reviews on layer7.net?

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

Any reviews on layer7.net?

Comments