I can't access host-c.com, also can't access my website (which hosted in host-c vps).
Ping RTO, connection timed out in browser. But, i can SSH to my VPS.
dns over https also didn't work since ping rto.
Traced to the box
1 1 ms 1 ms 10 ms 192.168.1.1
2 11 ms 15 ms 4 ms 10.129.0.1
3 6 ms 6 ms 5 ms 140.213.23.245
4 18 ms 19 ms 20 ms if-ge-10-3-8-0.tcore1.svq-singapore.as6453.net [180.87.96.197]
5 * * * Request timed out.
6 * 196 ms * if-bundle-53-2.qcore1.tv2-tokyo.as6453.net [209.58.61.96]
7 * * * Request timed out.
8 203 ms * * if-bundle-2-2.qcore2.kv8-chiba.as6453.net [116.0.74.23]
9 195 ms * 196 ms if-ae-53-2.tcore2.lvw-losangeles.as6453.net [64.86.252.56]
10 199 ms * 198 ms if-bundle-34-2.qcore2.lvw-losangeles.as6453.net [207.45.219.128]
11 * 201 ms 211 ms if-bundle-2-2.qcore1.lvw-losangeles.as6453.net [207.45.219.2]
12 * * 204 ms lax-b22-link.ip.twelve99.net [62.115.192.12]
13 260 ms 262 ms 275 ms rest-bb1-link.ip.twelve99.net [62.115.139.194]
14 * 292 ms 278 ms nyk-bb5-link.ip.twelve99.net [62.115.139.34]
15 261 ms 260 ms 260 ms ldn-bb1-link.ip.twelve99.net [62.115.139.245]
16 266 ms * 278 ms ldn-b2-link.ip.twelve99.net [62.115.122.189]
17 250 ms 249 ms 257 ms 62.115.38.211
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
If you send a message like this, please first make sure customers may edit all the information you require from them, including email address.
Dear Customers,
As part of our ongoing efforts to maintain a secure and trusted platform, we are implementing enhanced fraud prevention measures for all new and existing accounts starting April 1, 2025.
To ensure uninterrupted access to your account, we require you to update your account information by March 31, 2025. This process is mandatory and will help us verify and protect your account from potential fraudulent activities.
What You Need to Do:
Update your contact details and personal information in your account.
If you need assistance, please open a support ticket through your client portal.
Deadline: March 31, 2025
Failure to complete this update within the given timeframe will result in the suspension of your account until the required information is verified.
We appreciate your prompt attention to this matter. If you have any questions or need assistance, our support team is ready to help.
We appreciate your support and prompt attention to this matter.
@root said: If you send a message like this, please first make sure customers may edit all the information you require from them, including email address.
E-mail is locked so the account's don't fly like crazy ( they did in the first few moths)
If you need to change that, open a ticket and we shall go from there.
@root said: If you send a message like this, please first make sure customers may edit all the information you require from them, including email address.
E-mail is locked so the account's don't fly like crazy ( they did in the first few moths)
@root said: If you send a message like this, please first make sure customers may edit all the information you require from them, including email address.
E-mail is locked so the account's don't fly like crazy ( they did in the first few moths)
@root said: Accounts fly? Is database leaked or something?
No, it’s not related to that. If we allow the email field to be editable, there would be no control over the account security. If an account gets hijacked, the attacker could simply change the email, locking out the rightful owner. We realized this after experiencing a few account hijacks, which ultimately led us to implement 2FA for better security.
As much as we value privacy, we also need to implement certain security measures to protect all users. I’m not exactly thrilled about this, but scaling beyond 1,000+ active users isn’t something that can be managed with simple tasks.
We're heading in the right direction ( by my estimates ), it would be a shame to mess it up.
It is easier to implement these changes now rather than dealing with them later down the road.
d means someone can take it by changing email address, however I can't understand the multiple changes withing first few months.> @host_c said:
@root said: Accounts fly? Is database leaked or something?
No, it’s not related to that. If we allow the email field to be editable, there would be no control over the account security. If an account gets hijacked, the attacker could simply change the email, locking out the rightful owner. We realized this after experiencing a few account hijacks, which ultimately led us to implement 2FA for better security.
As much as we value privacy, we also need to implement certain security measures to protect all users. I’m not exactly thrilled about this, but scaling beyond 1,000+ active users isn’t something that can be managed with simple tasks.
Simpler solution: If customer has 2FA enabled, then allow email editing.
@root said: Simpler solution: If customer has 2FA enabled, then allow email editing.
That will not stop the following:
A buys a service, blatantly violates the TOS. We give the fella a friendly nudge—"Hey, cut that shit out, or the service gets suspended." Fella decides to behave… but since they can’t do the "thing" they wanted anymore, they just hand off the account to Fella B.
The above is something we played for 3 months, then we just disabled the email field to not be editable.
Some of these changes might not sit well with everyone, but as I mentioned here on LES, starting from zero and growing slowly gave us a valuable learning curve. Every measure we’ve implemented came out of necessity—to keep the 80%+ happy and running smoothly, while letting the 20% find another place to do "their thing."
@root said: Simpler solution: If customer has 2FA enabled, then allow email editing.
That will not stop the following:
A buys a service, blatantly violates the TOS. We give the fella a friendly nudge—"Hey, cut that shit out, or the service gets suspended." Fella decides to behave… but since they can’t do the "thing" they wanted anymore, they just hand off the account to Fella B.
The above is something we played for 3 months, then we just disabled the email field to not be editable.
Some of these changes might not sit well with everyone, but as I mentioned here on LES, starting from zero and growing slowly gave us a valuable learning curve. Every measure we’ve implemented came out of necessity—to keep the 80%+ happy and running smoothly, while letting the 20% find another place to do "their thing."
Thank you for the explanation. I have no idea how to solve these kind of abuses. You could be right, I don't know.
@root said: Thank you for the explanation. I have no idea how to solve these kind of abuses. You could be right, I don't know.
Neither did we at first, some providers did gave us a heads up " hey host-c, that is not a good idea ", they were right, and I thank them.
In the end, if we let abusers or other into the network, that would just mess with the nice folks who play by the rules.
This translates to being disrespectful towards them as we cannot provide a good service ( I hardly doubt that hosting anything in any way works, you have a ton of examples here and on OGF ), and if we do not respect our customers, what does that say about us?
@root said: We know. You have a datacenter there too. We all love that ecological datacenter of yours which needs no cooling and reduces costs on electricity.
@yoursunny - can we colocate??? all this only, I will underline only here, if we have ISDN
@root said: We know. You have a datacenter there too. We all love that ecological datacenter of yours which needs no cooling and reduces costs on electricity.
@yoursunny - can we colocate??? all this only, I will underline only here, if we have ISDN
@root said: We know. You have a datacenter there too. We all love that ecological datacenter of yours which needs no cooling and reduces costs on electricity.
@yoursunny - can we colocate??? all this only, I will underline only here, if we have ISDN
@host_c said: 2 - auto backup / snapshot on storage VPS - ( root, )
These are being implemented right now for backup
Eligible products that come with at least 1 backup slot have auto-backup set at provisioning..
Backups are at an off-site location and not in the Oradea Datacenter.
What would be the frequency of that task? Daily/weekly/monthly/only-at-install? I did not saw anything about that besides the "on/off" button available on the root disk in the panel. To restore, is it via ticket? The root diks restore won't "format" the storage diks, nah? Thanks!
Is the iso mount/custom install fix already done / in the roadmap?
I am not asking this to know when I can b0rk my root diks repartitioning it and asking for the restore
@host_c said:
From the to-do list we are going to cut one off ( finally )
2 - auto backup / snapshot on storage VPS - ( root, )
These are being implemented right now for backup
Eligible products that come with at least 1 backup slot have auto-backup set at provisioning..
Backups are at an off-site location and not in the Oradea Datacenter.
3 - auto allocate a /64 IPV6 at provision/reinstall not via ticket. - ( Shot² )
This was also done like a few moths ago
Was there a change made to backups for the pioneer servers? Mine used to have backups in the control panel menu for the boot drive but doesn't anymore, I think maybe you mentioned something a few months ago but can't find it
Frequencie is set to 1 / week on Saturday midnight. This can be edited by the user anytime or changed.
Restore works from user panel. uou can even access individual files from the backup.
This option as I said, it is available only on products that have Backup Available for all drives, as restoring only the Boot Drive is not possible for the moment, it is a limitation of Proxmox, as restore is basically deleting the VPS then redoing it from the backup. If you do not have backup on all drives, restore will be done without those and you will loos the data.
This is the reason we took backup out of products that had it active only on the boot drive as it was unusable in that configuration.
For products that have it on all drives, it works as expected.
@eliphas said: Is the iso mount/custom install fix already done / in the roadmap?
This should also been fixed as of today.
We did not see any issues regarding power tasks done by users.
Thanks! I've gone and mounted the ubuntu server iso and changed boot order (ouch! this REBOOTS the VM, beware!) to convert my ext4 root diks to btrfs as wanted, and it worked like a charm.
Just this move already solved my diks space needs for now, as I have gained 2GB in diks free. Sometime in the future I may try to reinstall it just because I don't have backups
Comments
These should be fixed by now, as we are done with whatever settings and upgrades we did the past 3 days.
If you still have some "weird" issues, I recommend a ticket.
Cheers!
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Fellas, you should check your e-mail or the announcement in your account.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
NO and you can't make me!!!
The Yeti has left the building.
Well, this time it is not about you or diks
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Been refreshing email box. Nothing yet
Did he deadpooled?
Happy customer at AlexHost, AxusHost, Bakker-IT, Host-C, Ionos, Veesp + NanoKVM ftw.
we have a 10 MSG / 10 SEC limit, as our IP email server is already trashed by the high volume of mail we sent
Will take some time for all to receive, you can find the same message in Network Status.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Nop, just doing some house-cleaning.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
DM me, I'll hook u uupwith my private email box
Unlimited sending 🙃
The correct way to deadpool.
Make a formal announcement
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
So how will you enforce this? Or
How do I know if my info is incorrect?
I mean there is 2 Main street in practically all major cities
Next stop
@host_c Always about my big diks!!!!
You have my info what more you want?
The Yeti has left the building.
Bananas will not cut it this time
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
All your base?
Happy customer at AlexHost, AxusHost, Bakker-IT, Host-C, Ionos, Veesp + NanoKVM ftw.
the mail is a generic one, sent to all customers, those that have correct data, have nothing to worry about.
those that have:
First Name King
Last Name England
Company Name
Email Address [email protected]
Address 1 The Moon, Crater 34
Postcode 2
Now would be the time to correct this.
all have 30 days to do it.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Damn ya got me, guess Moonbeam Stratusphere is gone ffs.
The Yeti has left the building.
HA HA HA
I thought it was common sense to announce all before we go ahead and activate the fraulein Fraud Protection.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
@host_c
If you send a message like this, please first make sure customers may edit all the information you require from them, including email address.
Cloudcone | Crunchbits | Dartnode | Dedirock | Georgedatacenter | Gigahost | Hostbilby | Host-c | Hostdzire | Hostsailor | Namecrane | Nuyek | Realtoxmedia | Servarica | Terabit | Tnahosting | Virmach
E-mail is locked so the account's don't fly like crazy ( they did in the first few moths)
If you need to change that, open a ticket and we shall go from there.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Accounts fly? Is database leaked or something?
Cloudcone | Crunchbits | Dartnode | Dedirock | Georgedatacenter | Gigahost | Hostbilby | Host-c | Hostdzire | Hostsailor | Namecrane | Nuyek | Realtoxmedia | Servarica | Terabit | Tnahosting | Virmach
Must be scalpers
oh no fruedian protection again!!!
The Yeti has left the building.
No, it’s not related to that. If we allow the email field to be editable, there would be no control over the account security. If an account gets hijacked, the attacker could simply change the email, locking out the rightful owner. We realized this after experiencing a few account hijacks, which ultimately led us to implement 2FA for better security.
As much as we value privacy, we also need to implement certain security measures to protect all users. I’m not exactly thrilled about this, but scaling beyond 1,000+ active users isn’t something that can be managed with simple tasks.
and that
We're heading in the right direction ( by my estimates
), it would be a shame to mess it up.
It is easier to implement these changes now rather than dealing with them later down the road.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
d means someone can take it by changing email address, however I can't understand the multiple changes withing first few months.> @host_c said:
Simpler solution: If customer has 2FA enabled, then allow email editing.
Cloudcone | Crunchbits | Dartnode | Dedirock | Georgedatacenter | Gigahost | Hostbilby | Host-c | Hostdzire | Hostsailor | Namecrane | Nuyek | Realtoxmedia | Servarica | Terabit | Tnahosting | Virmach
So if all of our info is good, we don't need to update anything?
That will not stop the following:
A buys a service, blatantly violates the TOS. We give the fella a friendly nudge—"Hey, cut that shit out, or the service gets suspended." Fella decides to behave… but since they can’t do the "thing" they wanted anymore, they just hand off the account to Fella B.
The above is something we played for 3 months, then we just disabled the email field to not be editable.
Some of these changes might not sit well with everyone, but as I mentioned here on LES, starting from zero and growing slowly gave us a valuable learning curve. Every measure we’ve implemented came out of necessity—to keep the 80%+ happy and running smoothly, while letting the 20% find another place to do "their thing."
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
DA aka YES!
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Thank you for the explanation. I have no idea how to solve these kind of abuses. You could be right, I don't know.
Cloudcone | Crunchbits | Dartnode | Dedirock | Georgedatacenter | Gigahost | Hostbilby | Host-c | Hostdzire | Hostsailor | Namecrane | Nuyek | Realtoxmedia | Servarica | Terabit | Tnahosting | Virmach
Neither did we at first, some providers did gave us a heads up " hey host-c, that is not a good idea ", they were right, and I thank them.
In the end, if we let abusers or other into the network, that would just mess with the nice folks who play by the rules.
This translates to being disrespectful towards them as we cannot provide a good service ( I hardly doubt that hosting anything in any way works, you have a ton of examples here and on OGF ), and if we do not respect our customers, what does that say about us?
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
I updated mine with bigger diks!!!!
The Yeti has left the building.
need help?
Stu is eager to mess something up again
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Nah just going to reinstall tell Stu he is out of luck on this one lol. Also testing out NJ for MicrNode probably end of next week will add it.
The Yeti has left the building.
There's a guy in the hot tub, I don't know who
Wait a minute, it looks like Stu 🍲
Happy customer at AlexHost, AxusHost, Bakker-IT, Host-C, Ionos, Veesp + NanoKVM ftw.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Our account is totally real:
yoursunny summer host, Inc
123 Elf Street
Amundsen-Scott South Pole Station 96598
Antarctica
We accept Karma donations for the last flan. 🍮 affbrr
We know. You have a datacenter there too. We all love that ecological datacenter of yours which needs no cooling and reduces costs on electricity.
PS: I also like the one from the dark side of the moon, away from sun's heat.
Cloudcone | Crunchbits | Dartnode | Dedirock | Georgedatacenter | Gigahost | Hostbilby | Host-c | Hostdzire | Hostsailor | Namecrane | Nuyek | Realtoxmedia | Servarica | Terabit | Tnahosting | Virmach
@yoursunny - can we colocate??? all this only, I will underline only here, if we have ISDN
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Maybe they no longer have that aluminium cabling.
Cloudcone | Crunchbits | Dartnode | Dedirock | Georgedatacenter | Gigahost | Hostbilby | Host-c | Hostdzire | Hostsailor | Namecrane | Nuyek | Realtoxmedia | Servarica | Terabit | Tnahosting | Virmach
Damn, would have been nice to have a eco-cooling-dc
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Yes, plenty of spaces at South Pole Colocation facility, but no remote hands.
https://yoursunny.com/p/summer-host/colo/
We accept Karma donations for the last flan. 🍮 affbrr
From the to-do list we are going to cut one off ( finally
)
2 - auto backup / snapshot on storage VPS - ( root, )
These are being implemented right now for backup
Eligible products that come with at least 1 backup slot have auto-backup set at provisioning..
Backups are at an off-site location and not in the Oradea Datacenter.
3 - auto allocate a /64 IPV6 at provision/reinstall not via ticket. - ( Shot² )
This was also done like a few moths ago
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Hi!
What would be the frequency of that task? Daily/weekly/monthly/only-at-install?
I did not saw anything about that besides the "on/off" button available on the root disk in the panel. To restore, is it via ticket? The root diks restore won't "format" the storage diks, nah? Thanks!
Is the iso mount/custom install fix already done / in the roadmap?
I am not asking this to know when I can b0rk my root diks repartitioning it and asking for the restore
Cheers,
Was there a change made to backups for the pioneer servers? Mine used to have backups in the control panel menu for the boot drive but doesn't anymore, I think maybe you mentioned something a few months ago but can't find it
7 doll hairs no more!!! Except diks need moar!!!! Diks
The Yeti has left the building.
Frequencie is set to 1 / week on Saturday midnight. This can be edited by the user anytime or changed.
Restore works from user panel. uou can even access individual files from the backup.
This option as I said, it is available only on products that have Backup Available for all drives, as restoring only the Boot Drive is not possible for the moment, it is a limitation of Proxmox, as restore is basically deleting the VPS then redoing it from the backup. If you do not have backup on all drives, restore will be done without those and you will loos the data.
This is the reason we took backup out of products that had it active only on the boot drive as it was unusable in that configuration.
For products that have it on all drives, it works as expected.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
This should also been fixed as of today.
We did not see any issues regarding power tasks done by users.
Host-C | Storage by Design | AS211462
“If it can’t guarantee behavior under load, it doesn’t belong in production.”
Thanks! I've gone and mounted the ubuntu server iso and changed boot order (ouch! this REBOOTS the VM, beware!) to convert my ext4 root diks to btrfs as wanted, and it worked like a charm.
Just this move already solved my diks space needs for now, as I have gained 2GB in diks free. Sometime in the future I may try to reinstall it just because I don't have backups