HOST-C, Chat, Updates, Stuff

lirrr

Please bless me this christmas with super deal that I can buy and not out of stock @host_c

host_c

Fellas, we had an issue last night with a node, and as a result we migrated some services to other nodes.

Sorry for the downtime, but we will take whatever measures we can to protect your services, even if this means taking them off for migration ( if live migration is not possible )

WE did send out an e-mail regarding this, but I know that with the delivery issues we have, some of you might not received it.

ariq01

Can you check your Debian 12 template sir? @host_c
i can't login root after fresh reinstall, or change password.

tfgp99

@ariq01 said:
Can you check your Debian 12 template sir? @host_c
i can't login root after fresh reinstall, or change password.

I highly recommend to use a SSH key instead of a password!

ariq01

@tfgp99 said: I highly recommend to use a SSH key instead of a password!

Yes i know, but i need to login with password first after successfull OS reinstallation (also cannot login with vnc)

xpress7

@ariq01 said:

@tfgp99 said: I highly recommend to use a SSH key instead of a password!

Yes i know, but i need to login with password first after successfull OS reinstallation (also cannot login with vnc)

Raise a ticket. They will fix your current setup.

Seems there is some issue with their Debian 12 template. I've also raised ticket 2 days back. They said they are working on it, and fixed my installation.

tfgp99

@xpress7 said:

@ariq01 said:

@tfgp99 said: I highly recommend to use a SSH key instead of a password!

Yes i know, but i need to login with password first after successfull OS reinstallation (also cannot login with vnc)

Raise a ticket. They will fix your current setup.

Seems there is some issue with their Debian 12 template. I've also raised ticket 2 days back. They said they are working on it, and fixed my installation.

Even yesterday i've reinstalled mine with that template, password went fine. Try use only letters and numbers, should be good to go!

ariq01

@xpress7 said: Raise a ticket. They will fix your current setup.

All good, i just straight to use pbs .iso

thanks @xpress7 @tfgp99

itsTomHarper

Danke senor

xpress7

@tfgp99 said:

@xpress7 said:

@ariq01 said:

@tfgp99 said: I highly recommend to use a SSH key instead of a password!

Yes i know, but i need to login with password first after successfull OS reinstallation (also cannot login with vnc)

Raise a ticket. They will fix your current setup.

Seems there is some issue with their Debian 12 template. I've also raised ticket 2 days back. They said they are working on it, and fixed my installation.

Even yesterday i've reinstalled mine with that template, password went fine. Try use only letters and numbers, should be good to go!

It was not just about password. It had some networking config issue as well. Confirmed through tickets. May be they fixed it now. The support was good and fixed my issue quickly.

host_c

@xpress7 said: It was not just about password. It had some networking config issue as well. Confirmed through tickets. May be they fixed it now. The support was good and fixed my issue quickly.

we managed to fix the Debian templates issues as I am aware.

No other users complained on reinstall.

Problem was that the deployment from template ignored the cloud-init section of settings, hence the template boot-ed with no ip ( IPV4/IPV6), user or password.

• We also reinstalled VNC server yesterday, should be more stable.
• There were some node-sync issues the day before, fixed those also.
• We did some tests on Proxmox 8.3, apparently NVME speed has increased, we will further test this, and pick a time frame in 2025 to update all nodes.
• Also, we are working on providing LAN communication between VPS services, this is in early phase, but it will see daylight as soon as possible.

dev_vps

if I can keep only one vps, it would be ....

host_c

@dev_vps said:
if I can keep only one vps, it would be ....

PS: I have no words for the cluster-fuckup on the yesterday issue, literally it was the worst day of 2024 for us. I effectively wanted to throw out Proxmox and go back to vMware

dev_vps

@host_c said:

@dev_vps said:
if I can keep only one vps, it would be ....

well, the reason is pretty simple
doing the right thing

xpress7

@host_c said:

@xpress7 said: It was not just about password. It had some networking config issue as well. Confirmed through tickets. May be they fixed it now. The support was good and fixed my issue quickly.

we managed to fix the Debian templates issues as I am aware.

No other users complained on reinstall.

Problem was that the deployment from template ignored the cloud-init section of settings, hence the template boot-ed with no ip ( IPV4/IPV6), user or password.

• We also reinstalled VNC server yesterday, should be more stable.
• There were some node-sync issues the day before, fixed those also.
• We did some tests on Proxmox 8.3, apparently NVME speed has increased, we will further test this, and pick a time frame in 2025 to update all nodes.

• Also, we are working on providing LAN communication between VPS services, this is in early phase, but it will see daylight as soon as possible.

Thank you. But may be not fixed on all nodes? Just now reinstalled Debian 12 from templates to test. And again same issue. No connectivity through ssh. And VNC showing Copy-of-VM-Debian-12 and not accpeting credentials. Reinstalled twice. Please check.

Can you check the Ticket #NST-402212

host_c

@xpress7 said:

@host_c said:

@xpress7 said: It was not just about password. It had some networking config issue as well. Confirmed through tickets. May be they fixed it now. The support was good and fixed my issue quickly.

we managed to fix the Debian templates issues as I am aware.

No other users complained on reinstall.

Problem was that the deployment from template ignored the cloud-init section of settings, hence the template boot-ed with no ip ( IPV4/IPV6), user or password.

• We also reinstalled VNC server yesterday, should be more stable.
• There were some node-sync issues the day before, fixed those also.
• We did some tests on Proxmox 8.3, apparently NVME speed has increased, we will further test this, and pick a time frame in 2025 to update all nodes.

• Also, we are working on providing LAN communication between VPS services, this is in early phase, but it will see daylight as soon as possible.

Thank you. But may be not fixed on all nodes? Just now reinstalled Debian 12 from templates to test. And again same issue. No connectivity through ssh. And VNC showing Copy-of-VM-Debian-12 and not accpeting credentials. Reinstalled twice. Please check.

Can you check the Ticket #NST-402212

I think the fix only applied to some of the nodes, NST-402212 replied.

xpress7

@host_c said:

@xpress7 said:

@host_c said:

@xpress7 said: It was not just about password. It had some networking config issue as well. Confirmed through tickets. May be they fixed it now. The support was good and fixed my issue quickly.

we managed to fix the Debian templates issues as I am aware.

No other users complained on reinstall.

Problem was that the deployment from template ignored the cloud-init section of settings, hence the template boot-ed with no ip ( IPV4/IPV6), user or password.

• We also reinstalled VNC server yesterday, should be more stable.
• There were some node-sync issues the day before, fixed those also.
• We did some tests on Proxmox 8.3, apparently NVME speed has increased, we will further test this, and pick a time frame in 2025 to update all nodes.

• Also, we are working on providing LAN communication between VPS services, this is in early phase, but it will see daylight as soon as possible.

Thank you. But may be not fixed on all nodes? Just now reinstalled Debian 12 from templates to test. And again same issue. No connectivity through ssh. And VNC showing Copy-of-VM-Debian-12 and not accpeting credentials. Reinstalled twice. Please check.

Can you check the Ticket #NST-402212

I think the fix only applied to some of the nodes, NST-402212 replied.

That means my node may not be fixed?

Sorry that ticket was updated on 11th Dec by staff. Just now updated from my side. Please check.

host_c

@xpress7 said:

@host_c said:

@xpress7 said:

@host_c said:

@xpress7 said: It was not just about password. It had some networking config issue as well. Confirmed through tickets. May be they fixed it now. The support was good and fixed my issue quickly.

we managed to fix the Debian templates issues as I am aware.

No other users complained on reinstall.

Problem was that the deployment from template ignored the cloud-init section of settings, hence the template boot-ed with no ip ( IPV4/IPV6), user or password.

• We also reinstalled VNC server yesterday, should be more stable.
• There were some node-sync issues the day before, fixed those also.
• We did some tests on Proxmox 8.3, apparently NVME speed has increased, we will further test this, and pick a time frame in 2025 to update all nodes.

• Also, we are working on providing LAN communication between VPS services, this is in early phase, but it will see daylight as soon as possible.

Thank you. But may be not fixed on all nodes? Just now reinstalled Debian 12 from templates to test. And again same issue. No connectivity through ssh. And VNC showing Copy-of-VM-Debian-12 and not accpeting credentials. Reinstalled twice. Please check.

Can you check the Ticket #NST-402212

I think the fix only applied to some of the nodes, NST-402212 replied.

That means my node may not be fixed?

Sorry that ticket was updated on 11th Dec by staff. Just now updated from my side. Please check.

Fix was a 2 step process

1 - node -this was done on all nodes yesterday
2 - product wide - it seems some were left out of the setting, this is undergoing modifications right now.

xpress7

@host_c said:

@xpress7 said:

@host_c said:

@xpress7 said:

@host_c said:

@xpress7 said: It was not just about password. It had some networking config issue as well. Confirmed through tickets. May be they fixed it now. The support was good and fixed my issue quickly.

we managed to fix the Debian templates issues as I am aware.

No other users complained on reinstall.

Problem was that the deployment from template ignored the cloud-init section of settings, hence the template boot-ed with no ip ( IPV4/IPV6), user or password.

• We also reinstalled VNC server yesterday, should be more stable.
• There were some node-sync issues the day before, fixed those also.
• We did some tests on Proxmox 8.3, apparently NVME speed has increased, we will further test this, and pick a time frame in 2025 to update all nodes.

• Also, we are working on providing LAN communication between VPS services, this is in early phase, but it will see daylight as soon as possible.

Thank you. But may be not fixed on all nodes? Just now reinstalled Debian 12 from templates to test. And again same issue. No connectivity through ssh. And VNC showing Copy-of-VM-Debian-12 and not accpeting credentials. Reinstalled twice. Please check.

Can you check the Ticket #NST-402212

I think the fix only applied to some of the nodes, NST-402212 replied.

That means my node may not be fixed?

Sorry that ticket was updated on 11th Dec by staff. Just now updated from my side. Please check.

Fix was a 2 step process

1 - node -this was done on all nodes yesterday
2 - product wide - it seems some were left out of the setting, this is undergoing modifications right now.

Thank you. I will wait then and test later then, as I don't have any urgency. Will update you if it is fixed. 👍

host_c

@xpress7 said: Thank you. I will wait then and test later then, as I don't have any urgency. Will update you if it is fixed. 👍

your service is already fixed as I recall..

xpress7

@host_c said:

@xpress7 said: Thank you. I will wait then and test later then, as I don't have any urgency. Will update you if it is fixed. 👍

your service is already fixed as I recall..

It was manually fixed by staff. But a fresh reinstallation from Debian 12 template is reproducing the issue, as I tested in last half an hour.

host_c

Give it a try within 30 minutes.
An reply back to the tiket, dum-dums are @ work for the moment, so they can fix it.

host_c

@xpress7

I think all is fine as I checked. just reply to the ticket if yes. - Thank you

samm

@host_c Megathread has been locked.

regards

samm

What did you do ?

regards

r3k

well well well

slownedstark

count from when the regards-away started!!

aviadmini

Do regards in other threads count?

samm

Brings all guys here for the sake of regards.
regards

lukast__

@aviadmini said:
Do regards in other threads count?

No.