NanoKVM | Free NAT KVM | Multiple Locations

18910111214»

Comments

  • @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.

    Will be done on Sunday instead, same time though.

    Thanked by (3)carlin0 tuc Wonder_Woman
  • havochavoc OGContent Writer
    edited July 26

    41a033760922ee59773dc33631410d4d85859cef

    Usage will be searx and a http proxy. Low usage & will be secured so that it's not open - just me

  • @havoc said:
    41a033760922ee59773dc33631410d4d85859cef

    Usage will be searx and a http proxy. Low usage & will be secured so that it's not open - just me

    Will process your request shortly, currently migrating the website over to another server.

  • havochavoc OGContent Writer

    @Neoon said:

    @havoc said:
    41a033760922ee59773dc33631410d4d85859cef

    Usage will be searx and a http proxy. Low usage & will be secured so that it's not open - just me

    Will process your request shortly, currently migrating the website over to another server.

    Thanks! No rush on mine

  • @havoc said:

    @Neoon said:

    @havoc said:
    41a033760922ee59773dc33631410d4d85859cef

    Usage will be searx and a http proxy. Low usage & will be secured so that it's not open - just me

    Will process your request shortly, currently migrating the website over to another server.

    Thanks! No rush on mine

    Deployed.

  • @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.

  • jqrjqr OG
    edited July 28

    > @Neoon said:
    > All nodes have been upgraded.
    > If you notice any issues, please lemme know.

    My Valdivia node is not accessible. The Dashboard shows it's online, but clicking on Manage gives me an error: "Failed to contact Node, please try again later."

    Just thought I'd led you know as you asked. No rush. Thank you for offering the service.

    edit: Oops, wrong service. My bad.

    It's pronounced hacker.

  • @Neoon said:
    If you notice any issues, please lemme know.

    Could you check if there's any issue with IPv6 in Fremont? Gateway is reachable but nothing beyond.

    default via fe80::4a8:e8ff:fe78:754d dev eth1 proto ra metric 1024 expires 1600sec hoplimit 64 pref medium
    [root@vps129 ~]# ping6 fe80::4a8:e8ff:fe78:754d%eth1
    PING fe80::4a8:e8ff:fe78:754d%eth1(fe80::4a8:e8ff:fe78:754d%eth1) 56 data bytes
    64 bytes from fe80::4a8:e8ff:fe78:754d%eth1: icmp_seq=1 ttl=64 time=0.166 ms
    64 bytes from fe80::4a8:e8ff:fe78:754d%eth1: icmp_seq=2 ttl=64 time=0.167 ms
    64 bytes from fe80::4a8:e8ff:fe78:754d%eth1: icmp_seq=3 ttl=64 time=0.169 ms
    64 bytes from fe80::4a8:e8ff:fe78:754d%eth1: icmp_seq=4 ttl=64 time=0.158 ms
    ^C
    --- fe80::4a8:e8ff:fe78:754d%eth1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2999ms
    rtt min/avg/max/mdev = 0.158/0.165/0.169/0.004 ms
    [root@vps129 ~]# ping6 2a09::
    PING 2a09::(2a09::) 56 data bytes
    ^C
    --- 2a09:: ping statistics ---
    9 packets transmitted, 0 received, 100% packet loss, time 8000ms
    

    dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/

  • @Brueggus said:

    @Neoon said:
    If you notice any issues, please lemme know.

    Could you check if there's any issue with IPv6 in Fremont? Gateway is reachable but nothing beyond.

    default via fe80::4a8:e8ff:fe78:754d dev eth1 proto ra metric 1024 expires 1600sec hoplimit 64 pref medium
    [root@vps129 ~]# ping6 fe80::4a8:e8ff:fe78:754d%eth1
    PING fe80::4a8:e8ff:fe78:754d%eth1(fe80::4a8:e8ff:fe78:754d%eth1) 56 data bytes
    64 bytes from fe80::4a8:e8ff:fe78:754d%eth1: icmp_seq=1 ttl=64 time=0.166 ms
    64 bytes from fe80::4a8:e8ff:fe78:754d%eth1: icmp_seq=2 ttl=64 time=0.167 ms
    64 bytes from fe80::4a8:e8ff:fe78:754d%eth1: icmp_seq=3 ttl=64 time=0.169 ms
    64 bytes from fe80::4a8:e8ff:fe78:754d%eth1: icmp_seq=4 ttl=64 time=0.158 ms
    ^C
    --- fe80::4a8:e8ff:fe78:754d%eth1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2999ms
    rtt min/avg/max/mdev = 0.158/0.165/0.169/0.004 ms
    [root@vps129 ~]# ping6 2a09::
    PING 2a09::(2a09::) 56 data bytes
    ^C
    --- 2a09:: ping statistics ---
    9 packets transmitted, 0 received, 100% packet loss, time 8000ms
    

    Fixed, sorry for that.

    Thanked by (1)Brueggus
  • 89d000a72288b04a2a5fd73522f42fff8f580fff

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

  • @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.

  • @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 :grimace:

  • @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.

  • Can I apply

  • @abyssvpn said:
    Can I apply

    Can you read?

    Thanked by (2)bliss ElonBezos

    Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
    https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png

  • 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

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

    Thanked by (1)Wonder_Woman
  • @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.

  • @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)

    dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/

  • @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.

    Thanked by (2)Brueggus tarasis
  • @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

    dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/

  • @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 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.

    Thanked by (2)Brueggus tarasis
  • 21d53a918b9006094f242d63703b4946dd4d9102

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

  • @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?

  • @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.

  • edited December 2

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

    Want to use it to run some website tools

  • @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.

Sign In or Register to comment.