Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

microLXC Public Test

1424345474854

Comments

  • What's happening in Vilnius

  • jvnadrjvnadr Member

    7ad9-f4c0-edf9-f292

  • NeoonNeoon Community Contributor, Veteran

    @Carlin0 said:
    What's happening in Vilnius

    I forgot despite having put it into my calendar, to ticket and get the node renewed.
    Sorry for that, Ticket is open since 12 hours however no answer yet.

    Thanked by 1Carlin0
  • @Neoon said:

    @Carlin0 said:
    What's happening in Vilnius

    I forgot despite having put it into my calendar, to ticket and get the node renewed.
    Sorry for that, Ticket is open since 12 hours however no answer yet.

    So all containers will have to be destroyed ?

  • NeoonNeoon Community Contributor, Veteran

    @Carlin0 said:

    @Neoon said:

    @Carlin0 said:
    What's happening in Vilnius

    I forgot despite having put it into my calendar, to ticket and get the node renewed.
    Sorry for that, Ticket is open since 12 hours however no answer yet.

    So all containers will have to be destroyed ?

    No, the instance currently is just suspended, I don't expect the instance to be deleted.

    Thanked by 1Carlin0
  • Vilnius is back 👍

  • IPv6 connectivity dropped completely in Norway 8 hours ago. Could you look into it? @Neoon

  • @jwg29859 said:
    IPv6 connectivity dropped completely in Norway 8 hours ago. Could you look into it? @Neoon

    it works for me

    Thanked by 1jwg29859
  • NeoonNeoon Community Contributor, Veteran

    @jwg29859 said:
    IPv6 connectivity dropped completely in Norway 8 hours ago. Could you look into it? @Neoon

    I don't see anything, I would need more info.

  • @Neoon said:

    @jwg29859 said:
    IPv6 connectivity dropped completely in Norway 8 hours ago. Could you look into it? @Neoon

    I don't see anything, I would need more info.

    My bad. My monitor was named incorrectly. No issues with the Gigahost server.

  • NeoonNeoon Community Contributor, Veteran

    Maintenance announcement

    Chile is going to be offline for about 14 hours on the 19th of July.
    Starting from 08:00 AM GMT -4

    While this may be disruptive in the short term, it will bring long-term benefits including improved latency and reachability within the Latin American region. Additionally, it will allow us to offer new networking features such as downstream BGP sessions to clients.

    Thanked by 2vicaya Ouji
  • Hey @Neoon 6804-1930-873e-ebea

  • PieRPieR Member

    Hey ae67-f64e-694d-48c9

  • de6b-e2d4-9703-2c5d

  • NeoonNeoon Community Contributor, Veteran

    Maintenance announcement
    I have to reboot Tokyo tomorrow, at around 22:00 CET, should not take more than a few minutes

  • kskksk Member

    e529-7b18-07c6-8310
    It's been really interesting for me to try the Pakistan node. <3

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:
    Maintenance announcement
    I have to reboot Tokyo tomorrow, at around 22:00 CET, should not take more than a few minutes

    Done, I had to include a few more nodes, that I missed yesterday, sorry for that.

    Thanked by 1Carlin0
  • hi @Neoon i just want to thank you for all of your hard work,

    have a nice day, don't forget to take a rest <3

  • NeoonNeoon Community Contributor, Veteran

    Maintenance announcement for Singapore

    Scheduled maintenance at Equinix JH1 (Singapore region) for planned software upgrade.

    Maintenance window starts: Tuesday, 05 August 2025 - 14:00 UTC
    Maintenance window ends: Tuesday, 05 August 2025 - 22:00 UTC

    Outage duration: 60 to 120 minutes in the maintenance window

    Impact: Network fluctuation and service interruptions.

  • NeoonNeoon Community Contributor, Veteran

    Debian 13 is now available.

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:
    Debian 13 is now available.

    Additional, image housekeeping.

    • Fedora 39 (KVM) and CentOS Stream has been removed, since nobody was using it.
    • Additionally, new Alpine versions have been added.
  • NeoonNeoon Community Contributor, Veteran

    Maintenance announcement
    I have to reboot Bratislava and Meppel on Monday, at around 22:00 CET, this should not take more than a few minutes.
    The kernel on these systems is older than one year, hence the livepatch coverage will end soon, so a reboot is needed.

    Thanked by 2Xrmaddness Carlin0
  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:
    Inactivity Policy update

    As of right now, logging in every 60 days, is sufficient to keep everything active.
    However, despite that, it seems like we still have too many idle containers.

    In about a week, a different policy is gonna be in affect
    Which also is gonna require at least 1GB of traffic (inbound + outbound) per month, per container.

    For testing reasons, the limit is set as low as possible.
    If only one of the requirements in meet, the container will not be extended.

    The way the plan was to implement it has changed.
    Basically, its gonna applied over the cost factor instead.

    For example, as of right now, you can spend the 1GB allocation as you want.
    However, if you deploy more than 2 containers on a single node, the second container is costing you double.

    There is an exception if its a bigger node, that rule doesn't apply for the second container but for the third.

    The idea here is, to do it the same way.
    If your container has less than 100MB used traffic (inbound + outbound) in the last 15 days, starting when your bandwidth counter resets.

    Which is different from each container, depending on when you created your container.
    The cost of this container will simply put, double.

    To incentivise you to either put it to good use or terminate it.
    I have coded it already, its way easier to implement, including email notifications.

    The plan was to roll this out tomorrow, there will be no stop or terminate actions taken at this point.
    I am open for feedback, if you have some lemme know.

    The 100MB is subject to change, but as of right now, ,its set as low as possible.

    Thanked by 3Xrmaddness Fritz Ouji
  • Hey guys. I appeared here for the first time in a long time. 😄

    @Neoon said:
    Debian 13 is now available.

    I reinstalled my micro to Debian 13 yesterday.
    My micro is working without trouble. 👍

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:
    Maintenance announcement
    I have to reboot Bratislava and Meppel on Monday, at around 22:00 CET, this should not take more than a few minutes.
    The kernel on these systems is older than one year, hence the livepatch coverage will end soon, so a reboot is needed.

    Done, the update is also live, first emails have been send.

    Thanked by 2Ouji Carlin0
  • @Neoon Any plan to add storage packages (like the one we have for Sandefjord) on any other locations ?

  • NeoonNeoon Community Contributor, Veteran

    @Caztiel said:
    @Neoon Any plan to add storage packages (like the one we have for Sandefjord) on any other locations ?

    Duh, the only reason we got storage, is because @gigahost decided to give the dedi a 2TB SSD.
    Unless of course, a certain someone like @host_c might do the same.

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:

    @Neoon said:
    Inactivity Policy update

    As of right now, logging in every 60 days, is sufficient to keep everything active.
    However, despite that, it seems like we still have too many idle containers.

    In about a week, a different policy is gonna be in affect
    Which also is gonna require at least 1GB of traffic (inbound + outbound) per month, per container.

    For testing reasons, the limit is set as low as possible.
    If only one of the requirements in meet, the container will not be extended.

    The way the plan was to implement it has changed.
    Basically, its gonna applied over the cost factor instead.

    For example, as of right now, you can spend the 1GB allocation as you want.
    However, if you deploy more than 2 containers on a single node, the second container is costing you double.

    There is an exception if its a bigger node, that rule doesn't apply for the second container but for the third.

    The idea here is, to do it the same way.
    If your container has less than 100MB used traffic (inbound + outbound) in the last 15 days, starting when your bandwidth counter resets.

    Which is different from each container, depending on when you created your container.
    The cost of this container will simply put, double.

    To incentivise you to either put it to good use or terminate it.
    I have coded it already, its way easier to implement, including email notifications.

    The plan was to roll this out tomorrow, there will be no stop or terminate actions taken at this point.
    I am open for feedback, if you have some lemme know.

    The 100MB is subject to change, but as of right now, ,its set as low as possible.

    Any Feedback?

  • fbf4-6747-9a8f-4a97

  • @Neoon said:

    @Neoon said:

    @Neoon said:
    Inactivity Policy update

    As of right now, logging in every 60 days, is sufficient to keep everything active.
    However, despite that, it seems like we still have too many idle containers.

    In about a week, a different policy is gonna be in affect
    Which also is gonna require at least 1GB of traffic (inbound + outbound) per month, per container.

    For testing reasons, the limit is set as low as possible.
    If only one of the requirements in meet, the container will not be extended.

    The way the plan was to implement it has changed.
    Basically, its gonna applied over the cost factor instead.

    For example, as of right now, you can spend the 1GB allocation as you want.
    However, if you deploy more than 2 containers on a single node, the second container is costing you double.

    There is an exception if its a bigger node, that rule doesn't apply for the second container but for the third.

    The idea here is, to do it the same way.
    If your container has less than 100MB used traffic (inbound + outbound) in the last 15 days, starting when your bandwidth counter resets.

    Which is different from each container, depending on when you created your container.
    The cost of this container will simply put, double.

    To incentivise you to either put it to good use or terminate it.
    I have coded it already, its way easier to implement, including email notifications.

    The plan was to roll this out tomorrow, there will be no stop or terminate actions taken at this point.
    I am open for feedback, if you have some lemme know.

    The 100MB is subject to change, but as of right now, ,its set as low as possible.

    Any Feedback?

    Just curious—if someone keep exceeding the usage limit and ignore it, will there be any penalty?

Sign In or Register to comment.