Howdy, Stranger!

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

Sign In Register

Quick Links


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
25% Recurring Discount on NVMe VPS
Try EnsoVPN - Reliable VPN - 1-Day Free Trial
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
CloudLinux
Try EnsoVPN - Fast & Private VPN - 1-Day Free Trial

Categories

In this Discussion

Home › General
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

1…5051525355

Comments

  • NeoonNeoon Community Contributor, Veteran

    @fadedmaple said:
    NTP in Vilnius appears to be having problems

    NTP isn't installed by default, I installed it on request on a few nodes.
    I didn't yet install it on all nodes, I will check later though.

  • ss93ss93 Member

    3932-356f-25d0-a686

  • fadedmaplefadedmaple Member

    @Neoon said:

    @fadedmaple said:
    NTP in Vilnius appears to be having problems

    NTP isn't installed by default, I installed it on request on a few nodes.
    I didn't yet install it on all nodes, I will check later though.

    Oh no, the time on my lxc is more than a day behind, and apt update is throwing an signature error

  • NeoonNeoon Community Contributor, Veteran

    @fadedmaple said:

    @Neoon said:

    @fadedmaple said:
    NTP in Vilnius appears to be having problems

    NTP isn't installed by default, I installed it on request on a few nodes.
    I didn't yet install it on all nodes, I will check later though.

    Oh no, the time on my lxc is more than a day behind, and apt update is throwing an signature error

    Actually LT has chrony already installed, you sure its a time problem?

  • fadedmaplefadedmaple Member

    @Neoon said:

    @fadedmaple said:

    @Neoon said:

    @fadedmaple said:
    NTP in Vilnius appears to be having problems

    NTP isn't installed by default, I installed it on request on a few nodes.
    I didn't yet install it on all nodes, I will check later though.

    Oh no, the time on my lxc is more than a day behind, and apt update is throwing an signature error

    Actually LT has chrony already installed, you sure its a time problem?

    Yes
    date -u
    Fri Jul 3 02:57:46 AM UTC 2026

    Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://deb.debian.org/debian trixie-updates InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-07-04T01:45:00Z Verifying signature: Not live until 2026-07-04T01:45:12Z

  • NeoonNeoon Community Contributor, Veteran

    @fadedmaple said:

    @Neoon said:

    @fadedmaple said:

    @Neoon said:

    @fadedmaple said:
    NTP in Vilnius appears to be having problems

    NTP isn't installed by default, I installed it on request on a few nodes.
    I didn't yet install it on all nodes, I will check later though.

    Oh no, the time on my lxc is more than a day behind, and apt update is throwing an signature error

    Actually LT has chrony already installed, you sure its a time problem?

    Yes
    date -u
    Fri Jul 3 02:57:46 AM UTC 2026

    Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://deb.debian.org/debian trixie-updates InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-07-04T01:45:00Z Verifying signature: Not live until 2026-07-04T01:45:12Z

    I added local NTP servers, for some reason the default ones caused it to desync.

    Thanked by 2Carlin0 fadedmaple
  • fadedmaplefadedmaple Member

    Sad news—I forgot Netherlands doesn't offer LXC anymore. I deleted it and lost it forever

  • vuanhsonvuanhson Member

    Hello, can we have ubuntu 26.04 LXC image?

  • fadedmaplefadedmaple Member

    Can we bring back the Netherlands lxc, nothing is safe anymore, thanks to Januscape😂

  • NeoonNeoon Community Contributor, Veteran

    @vuanhson said:
    Hello, can we have ubuntu 26.04 LXC image?

    I haven't updated all nodes to 6.8 yet, we had issues with a ancient kernel before.

    @fadedmaple said:
    Can we bring back the Netherlands lxc, nothing is safe anymore, thanks to Januscape😂

    Once the node is upgraded to 6.8

    Thanked by 1vuanhson
  • TandoorTandoor Member

    206e-3861-42e1-83b7

  • fadedmaplefadedmaple Member

    @Neoon said:

    @vuanhson said:
    Hello, can we have ubuntu 26.04 LXC image?

    I haven't updated all nodes to 6.8 yet, we had issues with a ancient kernel before.

    @fadedmaple said:
    Can we bring back the Netherlands lxc, nothing is safe anymore, thanks to Januscape😂

    Once the node is upgraded to 6.8

    Let's jump to 7.1.3—the Zabbly kernel, maintained by the Incus developer Stéphane Graber.

    Also, it seems there's a problem with the nftables module in Norway. A simple redirect rule results in the following error: /etc/nftables.conf:24:62-69: Error: Could not process rule: No such file or directory

  • NeoonNeoon Community Contributor, Veteran

    @fadedmaple said:

    @Neoon said:

    @vuanhson said:
    Hello, can we have ubuntu 26.04 LXC image?

    I haven't updated all nodes to 6.8 yet, we had issues with a ancient kernel before.

    @fadedmaple said:
    Can we bring back the Netherlands lxc, nothing is safe anymore, thanks to Januscape😂

    Once the node is upgraded to 6.8

    Let's jump to 7.1.3—the Zabbly kernel, maintained by the Incus developer Stéphane Graber.

    Also, it seems there's a problem with the nftables module in Norway. A simple redirect rule results in the following error: /etc/nftables.conf:24:62-69: Error: Could not process rule: No such file or directory

    No, there is a reason why we use the Ubuntu kernel, gets livepatching.
    Best I can do right now is 6.8, maybe 26.04 with 7.0

  • NeoonNeoon Community Contributor, Veteran

    NL got rebooted and migrated to another Node.
    Live migration wasn't possible due to the cpu passthrough we got enabled.
    Hence the 30 minutes downtime.

    Enjoy the CPU upgrade.

    Thanked by 2oloke fadedmaple
  • d2411d2411 Member

    82a3-2a57-c0f3-ece4

  • daviddavid Member

    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

  • NeoonNeoon Community Contributor, Veteran

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    Thanked by 4david fadedmaple host_c Carlin0
  • daviddavid Member

    @Neoon said:

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    It's good now, thanks.

  • fadedmaplefadedmaple Member

    @Neoon said:

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    Could you take a look at the kernel module issue on the Norway one? I'm a bit OCD, thanks a lot!

        iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j REDIRECT --to-ports 8443
    Warning: Extension REDIRECT revision 0 not supported, missing kernel module?
    iptables v1.8.11 (nf_tables):  RULE_APPEND failed (No such file or directory): rule in chain PREROUTING
  • NeoonNeoon Community Contributor, Veteran

    @fadedmaple said:

    @Neoon said:

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    Could you take a look at the kernel module issue on the Norway one? I'm a bit OCD, thanks a lot!

        iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j REDIRECT --to-ports 8443
    Warning: Extension REDIRECT revision 0 not supported, missing kernel module?
    iptables v1.8.11 (nf_tables):  RULE_APPEND failed (No such file or directory): rule in chain PREROUTING

    The Kernel module wasn't loaded, now it is.

    Thanked by 1fadedmaple
  • fadedmaplefadedmaple Member
    edited July 15

    @Neoon said:

    @fadedmaple said:

    @Neoon said:

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    Could you take a look at the kernel module issue on the Norway one? I'm a bit OCD, thanks a lot!

        iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j REDIRECT --to-ports 8443
    Warning: Extension REDIRECT revision 0 not supported, missing kernel module?
    iptables v1.8.11 (nf_tables):  RULE_APPEND failed (No such file or directory): rule in chain PREROUTING

    The Kernel module wasn't loaded, now it is.

    It turns out we still need nft_redir to support redirects in nftables
    Now I understand why some folks use NixOS

  • NeoonNeoon Community Contributor, Veteran
    edited July 16

    @fadedmaple said:

    @Neoon said:

    @fadedmaple said:

    @Neoon said:

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    Could you take a look at the kernel module issue on the Norway one? I'm a bit OCD, thanks a lot!

        iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j REDIRECT --to-ports 8443
    Warning: Extension REDIRECT revision 0 not supported, missing kernel module?
    iptables v1.8.11 (nf_tables):  RULE_APPEND failed (No such file or directory): rule in chain PREROUTING

    The Kernel module wasn't loaded, now it is.

    It turns out we still need nft_redir to support redirects in nftables
    Now I understand why some folks use NixOS

    Should be loaded since yesterday, was to tired hence a reply today.
    If you need any more modules loaded, lemme know.

    Thanked by 1fadedmaple
  • NeoonNeoon Community Contributor, Veteran

    Rebooted Helsinki, since the bookworm patch just got available.

    Thanked by 4oloke david Carlin0 BasToTheMax
  • WorldWorld Veteran

    @Neoon said:

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    I'm getting "Failed to contact Node, please try again later." in Islamabad, checked microPK status is online, maybe the same problem as this one?

  • NeoonNeoon Community Contributor, Veteran

    @World said:

    @Neoon said:

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    I'm getting "Failed to contact Node, please try again later." in Islamabad, checked microPK status is online, maybe the same problem as this one?

    Should be resolved, Tokyo is still unavailable via the API though.
    I will fix it shortly.

    Thanked by 1World
  • NeoonNeoon Community Contributor, Veteran

    @Neoon said:

    @World said:

    @Neoon said:

    @david said:
    For the past few days, I've been getting:

    Failed to contact Node, please try again later.

    when I try to manage Oradea. The vps itself is ok.

    I missed to adjust the script that renews the ssl cert, fixed.
    I go through the rest of the machines later, in case I missed another one.

    I'm getting "Failed to contact Node, please try again later." in Islamabad, checked microPK status is online, maybe the same problem as this one?

    Should be resolved, Tokyo is still unavailable via the API though.
    I will fix it shortly.

    Tokyo should be back in about 1 hour, as soon as DNS updates.
    Something is causing IPv6 connectivity issues in-between the backend and the Node.

    Thanked by 3igctt World jwg29859
  • igcttigctt Member

    hello, an instance hostname: lxc8be23eca, can't ssh login after deployment, I try to reconfigure network, reinstall it, it would accessible after reinstall but after about 10 minutes, ssh can't login again. I even create a shell script to maintain sshd_config and authorized_keys each 5 mins, it all failed, whereas the other programs running normally in this instance. would you take a look when you have free time? it's not hurry, anyway all programs runs ok except it's not sshd accessible. thanks

  • NeoonNeoon Community Contributor, Veteran

    @igctt said:
    hello, an instance hostname: lxc8be23eca, can't ssh login after deployment, I try to reconfigure network, reinstall it, it would accessible after reinstall but after about 10 minutes, ssh can't login again. I even create a shell script to maintain sshd_config and authorized_keys each 5 mins, it all failed, whereas the other programs running normally in this instance. would you take a look when you have free time? it's not hurry, anyway all programs runs ok except it's not sshd accessible. thanks

    In general, please provide more information, I am also not gonna log into your container to debug something, usually just deploy a new one and try to replicate the issue.

    Did you connect over IPv6? is SSH fine via IPv4?
    Did you check if ssh is running or crashed due to OOM?

    Please check your logs.

  • igcttigctt Member
    edited July 29

    the sshd service is running because when trying to login, it said "Permission denied", while the pub key is set. ipv4 and ipv6 have the same issue. I think it's not OOM because a ltstats agent shows that mem usage is below 10%.
    in fact, try to check out what happened, I reinstall it for a couple of times, it always deny ssh login after 10 minutes.
    it's fine to login to find some issues. it's ok to me though.
    this is what I did:
    after each reinstall, in the first 10 minutes, I always put same programs in it and enable some service such as nginx, etc, and I found the ipv6 address is not assigned to eth0, then each time I edit interface file manually according the ipv6 address/gateway on the dashboard. start the services. make a sshd_config maintain shell script in the crontab. that shell script also try to maintain the authorized_keys's content correctly. it won't works. each time after about 10 minutes, the ssh session would be kicked out and can't login.
    being kicked out and then at next reinstall, I created that shell script. I don't think that shell script corrupts the authorized_keys.

    thank you.

  • NeoonNeoon Community Contributor, Veteran

    @igctt said:
    the sshd service is running because when trying to login, it said "Permission denied", while the pub key is set. ipv4 and ipv6 have the same issue. I think it's not OOM because a ltstats agent shows that mem usage is below 10%.
    in fact, try to check out what happened, I reinstall it for a couple of times, it always deny ssh login after 10 minutes.
    it's fine to login to find some issues. it's ok to me though.
    this is what I did:
    after each reinstall, in the first 10 minutes, I always put same programs in it and enable some service such as nginx, etc, and I found the ipv6 address is not assigned to eth0, then each time I edit interface file manually according the ipv6 address/gateway on the dashboard. start the services. make a sshd_config maintain shell script in the crontab. that shell script also try to maintain the authorized_keys's content correctly. it won't works. each time after about 10 minutes, the ssh session would be kicked out and can't login.
    being kicked out and then at next reinstall, I created that shell script. I don't think that shell script corrupts the authorized_keys.

    thank you.

    Okay, so its not a Network issue, plus SSH is running.
    Please go and check the logs of the SSH service.

    Have you tried using a password with SSH?
    Also does SSH login fail over IPv4 and IPv6?

Sign In or Register to comment.