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
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

14849505254

Comments

  • ec35-26cf-b857-5d23

  • Samoht999Samoht999 Member
    edited April 19

    edit

  • NeoonNeoon Community Contributor, Veteran

    @d2411 said:
    Johannesburg is not working. I cant deploy a container on it. According to the status page it seems to be online but everytime i am trying to deploy a container, I always get "Deployment of the container failed,
    please try again." @Neoon could you please check whats wrong ? Thanks

    I will debug it later today, I already saw the notification about the failed deployment

    Thanked by 1Carlin0
  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:

    @d2411 said:
    Johannesburg is not working. I cant deploy a container on it. According to the status page it seems to be online but everytime i am trying to deploy a container, I always get "Deployment of the container failed,
    please try again." @Neoon could you please check whats wrong ? Thanks

    I will debug it later today, I already saw the notification about the failed deployment

    desync is fixed.

    Thanked by 2Carlin0 Starnberg
  • @Neoon have you been able to look into my quota?

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:

    @Neoon said:

    @d2411 said:
    Johannesburg is not working. I cant deploy a container on it. According to the status page it seems to be online but everytime i am trying to deploy a container, I always get "Deployment of the container failed,
    please try again." @Neoon could you please check whats wrong ? Thanks

    I will debug it later today, I already saw the notification about the failed deployment

    desync is fixed.

    Nevermind, it broke again, I deployed yesterday with success though.

  • NeoonNeoon Community Contributor, Veteran

    Tokyo is getting its prefix, tomorraw.

    As stated in previously sent emails, as part of migration of Japan services to our new infrastructure at Equinix TY8 location, the following changes will be applied with regard to IPv6 addresses assigned to existing services:

    • All of the services will automatically receive one dedicated routed /48 IPv6 prefix (once the migration is completed on 22nd April 2026).

    Also

    Maintenance Window:

    Start Time: 1 AM 22nd April 2026 (Japan time)
    Completion Time: 7 AM 22nd April (Japan time)

    Impact: Service will be inaccessible during the migration phase (depending on disk size it can take 5 to 30 minutes per service)

  • NeoonNeoon Community Contributor, Veteran

    @Samoht999 said:
    @Neoon have you been able to look into my quota?

    No otherwise I would have looked into it.

    Thanked by 1Samoht999
  • NeoonNeoon Community Contributor, Veteran

    I also added PK back in stock, since it has been stable the last 3 weeks.

    Thanked by 2Starnberg jcn50
  • NeoonNeoon Community Contributor, Veteran
    edited April 21

    @Neoon said:

    @Neoon said:

    @Neoon said:

    @d2411 said:
    Johannesburg is not working. I cant deploy a container on it. According to the status page it seems to be online but everytime i am trying to deploy a container, I always get "Deployment of the container failed,
    please try again." @Neoon could you please check whats wrong ? Thanks

    I will debug it later today, I already saw the notification about the failed deployment

    desync is fixed.

    Nevermind, it broke again, I deployed yesterday with success though.

    Nevermind, it works, but if there is any network issue during the deployment, this can create desyncs.
    I keep an eye on it.

    Thanked by 1Starnberg
  • d2411d2411 Member

    Can confirm that Johannesburg is working again.
    Thanks @Neoon

  • I don't understand why I signed up and didn't receive any Vps

  • NeoonNeoon Community Contributor, Veteran

    @Samoht999 said:
    I don't understand why I signed up and didn't receive any Vps

    Well, people abused the fully automated system, since then its not longer fully automated.
    Every account has to be manually verified, this is done when I have time.

    If you are unhappy, there is a account deletion button.
    Plus their are plenty of VPS providers here that would sell you one

  • @Neoon said:

    @Samoht999 said:
    I don't understand why I signed up and didn't receive any Vps

    Well, people abused the fully automated system, since then its not longer fully automated.
    Every account has to be manually verified, this is done when I have time.

    If you are unhappy, there is a account deletion button.
    Plus their are plenty of VPS providers here that would sell you one

    No it's perfectly fine, I totally understand.
    I just didn't understand what happened with my account. Now you explained to me so it's clear.
    I have plenty of paid VPSs but I was curious to test your service.
    Thank you

  • @Neoon said:
    Tokyo is getting its prefix, tomorraw.

    As stated in previously sent emails, as part of migration of Japan services to our new infrastructure at Equinix TY8 location, the following changes will be applied with regard to IPv6 addresses assigned to existing services:

    • All of the services will automatically receive one dedicated routed /48 IPv6 prefix (once the migration is completed on 22nd April 2026).

    Also

    Maintenance Window:

    Start Time: 1 AM 22nd April 2026 (Japan time)
    Completion Time: 7 AM 22nd April (Japan time)

    Impact: Service will be inaccessible during the migration phase (depending on disk size it can take 5 to 30 minutes per service)

    Is it Starry Network or WebHorizon?

  • NeoonNeoon Community Contributor, Veteran

    @fadedmaple said:

    @Neoon said:
    Tokyo is getting its prefix, tomorraw.

    As stated in previously sent emails, as part of migration of Japan services to our new infrastructure at Equinix TY8 location, the following changes will be applied with regard to IPv6 addresses assigned to existing services:

    • All of the services will automatically receive one dedicated routed /48 IPv6 prefix (once the migration is completed on 22nd April 2026).

    Also

    Maintenance Window:

    Start Time: 1 AM 22nd April 2026 (Japan time)
    Completion Time: 7 AM 22nd April (Japan time)

    Impact: Service will be inaccessible during the migration phase (depending on disk size it can take 5 to 30 minutes per service)

    Is it Starry Network or WebHorizon?

    WebHorizon, Starry has IPv6 but not routed.

  • 14a1-a9ec-30e8-ef1e

  • NeoonNeoon Community Contributor, Veteran

    The Subnet in JP is ready and configured.
    I will do a quick reboot tomorrow and enable IPv6 afterwards.

    As soon its available, just press reconfigure in the panel.

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:
    The Subnet in JP is ready and configured.
    I will do a quick reboot tomorrow and enable IPv6 afterwards.

    As soon its available, just press reconfigure in the panel.

    Done.

    Thanked by 1Carlin0
  • NeoonNeoon Community Contributor, Veteran

    Console on JP is working again.

    Thanked by 1Xrmaddness
  • NeoonNeoon Community Contributor, Veteran

    Lads and Gents, we got a new Node in Ho Chi Minh.
    Courtesy of Onidel, thanks @oloke

    /64 routed iPv6, HAPorxy, DNS Proxy the usual.

  • daviddavid Member

    Does HAProxy pass UDP on port 443 for quic/http3?

  • NeoonNeoon Community Contributor, Veteran

    @david said:
    Does HAProxy pass UDP on port 443 for quic/http3?

    Well, the http version is determined by the webserver you run.
    HAProxy should not give a fuck, it just forwards the packages.

    The only exception is if you encrypt the SNI.
    Without the SNI, HAProxy can't rout the packages anymore.

    I didn't test it though, if QUIC works.

    Thanked by 1david
  • daviddavid Member

    @Neoon said:

    @david said:
    Does HAProxy pass UDP on port 443 for quic/http3?

    Well, the http version is determined by the webserver you run.
    HAProxy should not give a fuck, it just forwards the packages.

    The only exception is if you encrypt the SNI.
    Without the SNI, HAProxy can't rout the packages anymore.

    I didn't test it though, if QUIC works.

    SNI isn't encrypted, so that should be OK. For some reason I can't get QUIC working, though. I have a similar setup on servers without HAProxy that does work.

    Doing some searching, it seems there is some configuration to enable QUIC for HAProxy.

  • NeoonNeoon Community Contributor, Veteran
    edited April 26

    @david said:

    @Neoon said:

    @david said:
    Does HAProxy pass UDP on port 443 for quic/http3?

    Well, the http version is determined by the webserver you run.
    HAProxy should not give a fuck, it just forwards the packages.

    The only exception is if you encrypt the SNI.
    Without the SNI, HAProxy can't rout the packages anymore.

    I didn't test it though, if QUIC works.

    SNI isn't encrypted, so that should be OK. For some reason I can't get QUIC working, though. I have a similar setup on servers without HAProxy that does work.

    Doing some searching, it seems there is some configuration to enable QUIC for HAProxy.

    Its not gonna work, except HAProxy terminates the connection.
    HAProxy and certificates, yak.

    I will look into caddy, sounds to easy though.
    Just remind me in a week, If I forgot it.

    Thanked by 1david
  • daviddavid Member

    @Neoon said:

    @david said:

    @Neoon said:

    @david said:
    Does HAProxy pass UDP on port 443 for quic/http3?

    Well, the http version is determined by the webserver you run.
    HAProxy should not give a fuck, it just forwards the packages.

    The only exception is if you encrypt the SNI.
    Without the SNI, HAProxy can't rout the packages anymore.

    I didn't test it though, if QUIC works.

    SNI isn't encrypted, so that should be OK. For some reason I can't get QUIC working, though. I have a similar setup on servers without HAProxy that does work.

    Doing some searching, it seems there is some configuration to enable QUIC for HAProxy.

    Its not gonna work, except HAProxy terminates the connection.
    HAProxy and certificates, yak.

    I will look into caddy, sounds to easy though.
    Just remind me in a week, If I forgot it.

    Thanks. At least I know why it's not working now. Might be a nice feature, but you don't have to do anything special just for me, either.

  • NeoonNeoon Community Contributor, Veteran

    Maintenance Announcement
    We still got 4 nodes running LXD, that are yet not migrated.
    The plan is for the next weekend to migrate them to Incus plus a distro upgrade with a new kernel.

    This includes: Singapore, Tokyo Equinix, Oradea and Islamabad.
    Expect up to 30 minutes downtime per Node, usually less.

    I will start at about 14:00 CET next Sunday.

  • NeoonNeoon Community Contributor, Veteran

    Relocation Announcement
    Our backend currently runs in AMS with Gigahost, Gigahost is gonna discontinue AMS on Wednesday morning.
    Hence our backend gets physically moved to Norway, this should not take more than 24 hours.

    During this time, the Panel including any operations will be unavailable.
    However, containers on the nodes will be running as usual.

    Backups are done, in case something goes wrong on the side of Gigahost, we are good.
    I am gonna take the opportunity, to also containerize and compartmentalize our backend.

    Which means the Panel might be unavailable for a short time today/tomorrow, during the migration.
    Just a heads up.

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:
    Relocation Announcement
    Our backend currently runs in AMS with Gigahost, Gigahost is gonna discontinue AMS on Wednesday morning.
    Hence our backend gets physically moved to Norway, this should not take more than 24 hours.

    During this time, the Panel including any operations will be unavailable.
    However, containers on the nodes will be running as usual.

    Backups are done, in case something goes wrong on the side of Gigahost, we are good.
    I am gonna take the opportunity, to also containerize and compartmentalize our backend.

    Which means the Panel might be unavailable for a short time today/tomorrow, during the migration.
    Just a heads up.

    Done, its up again.

  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:
    Maintenance Announcement
    We still got 4 nodes running LXD, that are yet not migrated.
    The plan is for the next weekend to migrate them to Incus plus a distro upgrade with a new kernel.

    This includes: Singapore, Tokyo Equinix, Oradea and Islamabad.
    Expect up to 30 minutes downtime per Node, usually less.

    I will start at about 14:00 CET next Sunday.

    Done.

Sign In or Register to comment.