NanoKVM | Free NAT KVM | Multiple Locations

Neoon

@rockinmusicgv said:
89d000a72288b04a2a5fd73522f42fff8f580fff

Hoping for a basic VPS for monitoring and some small services that is a bit out of band from what I currently have...

Deployed.

Ganonk

@Neoon said:

@Neoon said:
Maintenance Announcement
Most of the Nodes are still running Proxmox 7, which is EOL end of this month.
So they need to be upgraded, you can expect up to 30 minutes of downtime per Node.

I will start upgrading the Nodes next Friday (26.07) at around 20:00 CET, one by one.
Once its done, I will post here again.

All nodes have been upgraded.
If you notice any issues, please lemme know.

oh nOo! my uptime

rockinmusicgv

@Neoon said:

@rockinmusicgv said:
89d000a72288b04a2a5fd73522f42fff8f580fff

Hoping for a basic VPS for monitoring and some small services that is a bit out of band from what I currently have...

Deployed.

Thank you so much. I feel bad, you deployed it so fast and I haven't had a chance to stop by and say thanks yet.

abyssvpn

Can I apply

Jab

@abyssvpn said:
Can I apply

Can you read?

alissonlc

Returning to work with Information Technology and networks, leaving a job as a rescuer in the public service of health, I believe that a vps like this already helps to do the tests and learning I need.

Token
325fc5088885918829ed58d5f4146368d1b53152

Neoon

Fremont had network issues about an hour ago.
IPv6 still dead, waiting for fix.

Neoon

@Neoon said:
Fremont had network issues about an hour ago.
IPv6 still dead, waiting for fix.

IPv6 is back up since roughly 1 hour.
If you still have issues, lemme know.

Brueggus

@Neoon said:

@Neoon said:
Fremont had network issues about an hour ago.
IPv6 still dead, waiting for fix.

IPv6 is back up since roughly 1 hour.
If you still have issues, lemme know.

Still not working for me. I can ping the default gateway on eth1 but nothing beyond (Google, for example)

Neoon

@Brueggus said:

@Neoon said:

@Neoon said:
Fremont had network issues about an hour ago.
IPv6 still dead, waiting for fix.

IPv6 is back up since roughly 1 hour.
If you still have issues, lemme know.

Still not working for me. I can ping the default gateway on eth1 but nothing beyond (Google, for example)

Yikes, they fixed it last time now it broke again.
Ticket is out, I suggested a permanent fix, will see, I report back.

Brueggus

@Neoon said:

@Brueggus said:

@Neoon said:

@Neoon said:
Fremont had network issues about an hour ago.
IPv6 still dead, waiting for fix.

IPv6 is back up since roughly 1 hour.
If you still have issues, lemme know.

Still not working for me. I can ping the default gateway on eth1 but nothing beyond (Google, for example)

Yikes, they fixed it last time now it broke again.
Ticket is out, I suggested a permanent fix, will see, I report back.

Thank you, it just came back online

Neoon

@Brueggus said:

@Neoon said:

@Brueggus said:

@Neoon said:

@Neoon said:
Fremont had network issues about an hour ago.
IPv6 still dead, waiting for fix.

IPv6 is back up since roughly 1 hour.
If you still have issues, lemme know.

Still not working for me. I can ping the default gateway on eth1 but nothing beyond (Google, for example)

Yikes, they fixed it last time now it broke again.
Ticket is out, I suggested a permanent fix, will see, I report back.

Thank you, it just came back online

Yes but its not a permanent fix though.

Neoon

@Neoon said:

@Brueggus said:

@Neoon said:

@Neoon said:
Fremont had network issues about an hour ago.
IPv6 still dead, waiting for fix.

IPv6 is back up since roughly 1 hour.
If you still have issues, lemme know.

Still not working for me. I can ping the default gateway on eth1 but nothing beyond (Google, for example)

Yikes, they fixed it last time now it broke again.
Ticket is out, I suggested a permanent fix, will see, I report back.

There will be another network maintenance.
Then we should have a permanent fix.

gooblermaster

21d53a918b9006094f242d63703b4946dd4d9102

i'll be using this for uptime monitoring and possibly a private proxy for anonymity

tarasis

@Neoon said:

@Neoon said:
Yikes, they fixed it last time now it broke again.
Ticket is out, I suggested a permanent fix, will see, I report back.

There will be another network maintenance.
Then we should have a permanent fix.

Haven't checked yet, did it work?

Neoon

@tarasis said:

@Neoon said:

@Neoon said:
Yikes, they fixed it last time now it broke again.
Ticket is out, I suggested a permanent fix, will see, I report back.

There will be another network maintenance.
Then we should have a permanent fix.

Haven't checked yet, did it work?

I didn't ask for a window yet, I suggested Wednesday.

alamdarzia

Token
51915f3178d2d783f890470bd431996bf46b4054
Expire
The Token will expire in 7 day(s).

Want to use it to run some website tools

adly

@alamdarzia said:
Token
51915f3178d2d783f890470bd431996bf46b4054
Expire
The Token will expire in 7 day(s).

Want to use it to run some website tools

No - read the qualification criteria.

Neoon

Fremont IPv6 connectivity will drop in about 20 minutes.
Sorry for the short notice, I didn't got a confirmation earlier.

Neoon

Fremont has its IPv6 subnet now fully routed.
If you still run into any issues though, lemme know.

adly

@Neoon out here running a service for free that would put many paid providers to shame.

chengzi

2f8bf5d32f5a1a4fb58c9e61cbcf85dd91a1b981

will be used for one of my uptime monitoring and network latency probing nodes

Neoon

IPv6 in Liberty Lake is currently still down, no ETA.

Neoon

@Neoon said:
IPv6 in Liberty Lake is currently still down, no ETA.

Fixed

Neoon

We had a drive Failure on the Node Liberty Lake from Crankbis.
The drive has been replaced and the raid is syncing now.

Expect degraded I/O performance for the next 1-2 hours.

somik

61751044905101f34980f5d27a84e2bc66cb1f1c

cause it's available (get your nano kvm fast fast while stocks last)

Ganonk

very nice

Neoon

@somik said:
61751044905101f34980f5d27a84e2bc66cb1f1c

cause it's available (get your nano kvm fast fast while stocks last)

Its not gonna be idle right?

somik

@Neoon said:

@somik said:
61751044905101f34980f5d27a84e2bc66cb1f1c

cause it's available (get your nano kvm fast fast while stocks last)

Its not gonna be idle right?

Well, I'm just gonna poke around and terminate it. I prefer using LXC since it's much lighter on resources

Neoon

@somik said:

@Neoon said:

@somik said:
61751044905101f34980f5d27a84e2bc66cb1f1c

cause it's available (get your nano kvm fast fast while stocks last)

Its not gonna be idle right?

Well, I'm just gonna poke around and terminate it. I prefer using LXC since it's much lighter on resources

The reason I ask for is that you have to provide a valid reason to get one.
Something like a blog you know.

somik

@Neoon said:

@somik said:

@Neoon said:

@somik said:
61751044905101f34980f5d27a84e2bc66cb1f1c

cause it's available (get your nano kvm fast fast while stocks last)

Its not gonna be idle right?

Well, I'm just gonna poke around and terminate it. I prefer using LXC since it's much lighter on resources

The reason I ask for is that you have to provide a valid reason to get one.
Something like a blog you know.

Well, in that case, please ignore the request.

Got no valid reason to get it. Just wanted to poke around the control panel, but I realize it's better for someone else who needs it.

Neoon

@somik said:

@Neoon said:

@somik said:

@Neoon said:

@somik said:
61751044905101f34980f5d27a84e2bc66cb1f1c

cause it's available (get your nano kvm fast fast while stocks last)

Its not gonna be idle right?

Well, I'm just gonna poke around and terminate it. I prefer using LXC since it's much lighter on resources

The reason I ask for is that you have to provide a valid reason to get one.
Something like a blog you know.

Well, in that case, please ignore the request.

Got no valid reason to get it. Just wanted to poke around the control panel, but I realize it's better for someone else who needs it.

its just proxmox anyway.

Neoon

NL is still down, I will update you when I know more.

Neoon

@Neoon said:
NL is still down, I will update you when I know more.

As soon as they go to the DC and check the server, I will update once again.

Neoon

@Neoon said:

@Neoon said:
NL is still down, I will update you when I know more.

As soon as they go to the DC and check the server, I will update once again.

The PSU died, the Node is up again.
Please lemme know if you have any issues with your VM.

Neoon

Maintenance Announcement

Proxmox 8 is EOL soon, hence we need to upgrade the nodes in the following weeks.
Liberty Lake is scheduled for next week Friday roughly 20:00 CET
I will upgrade all other nodes about 1 week later, same time.

Expect about 10-20 minutes of downtime, per Node.

rpqu

@Neoon said:
Maintenance Announcement

Proxmox 8 is EOL soon, hence we need to upgrade the nodes in the following weeks.
Liberty Lake is scheduled for next week Friday roughly 20:00 CET
I will upgrade all other nodes about 1 week later, same time.

Expect about 10-20 minutes of downtime, per Node.

Is it destructive or it's just the usual data moving?

yucchun

78777cdd2cf56bc269ed2567f53df96eaac0f91e

I need a place to run some code (mostly test deploys) that is not a significantly important place // that is a somewhat disposable environment for me in case things go terribly wrong™

Neoon

@rpqu said:

@Neoon said:
Maintenance Announcement

Proxmox 8 is EOL soon, hence we need to upgrade the nodes in the following weeks.
Liberty Lake is scheduled for next week Friday roughly 20:00 CET
I will upgrade all other nodes about 1 week later, same time.

Expect about 10-20 minutes of downtime, per Node.

Is it destructive or it's just the usual data moving?

It might crash and burn, we will see.

Neoon

@Neoon said:
Maintenance Announcement

Proxmox 8 is EOL soon, hence we need to upgrade the nodes in the following weeks.
Liberty Lake is scheduled for next week Friday roughly 20:00 CET
I will upgrade all other nodes about 1 week later, same time.

Expect about 10-20 minutes of downtime, per Node.

I did sleep through it, my bad, will do it tomorraw, same time.

Neoon

@Neoon said:
Maintenance Announcement

Proxmox 8 is EOL soon, hence we need to upgrade the nodes in the following weeks.
Liberty Lake is scheduled for next week Friday roughly 20:00 CET
I will upgrade all other nodes about 1 week later, same time.

Expect about 10-20 minutes of downtime, per Node.

Liberty Lake was done yesterday, no issues so far.
Gonna reschedule the others to 14:00 CET on Friday.
I don't have a IPMI on them, just in case something goes wrong.

Neoon

@Neoon said:

@Neoon said:
Maintenance Announcement

Proxmox 8 is EOL soon, hence we need to upgrade the nodes in the following weeks.
Liberty Lake is scheduled for next week Friday roughly 20:00 CET
I will upgrade all other nodes about 1 week later, same time.

Expect about 10-20 minutes of downtime, per Node.

Liberty Lake was done yesterday, no issues so far.
Gonna reschedule the others to 14:00 CET on Friday.
I don't have a IPMI on them, just in case something goes wrong.

Eygelshoven and Fremont are upgraded.
I will do the rest next week (Sandefjord & Paris)
Same time

Fritz

@Neoon said:

@Neoon said:

@Neoon said:
Maintenance Announcement

Proxmox 8 is EOL soon, hence we need to upgrade the nodes in the following weeks.
Liberty Lake is scheduled for next week Friday roughly 20:00 CET
I will upgrade all other nodes about 1 week later, same time.

Expect about 10-20 minutes of downtime, per Node.

Liberty Lake was done yesterday, no issues so far.
Gonna reschedule the others to 14:00 CET on Friday.
I don't have a IPMI on them, just in case something goes wrong.

Eygelshoven and Fremont are upgraded.
I will do the rest next week (Sandefjord & Paris)
Same time

Yay!