microLXC Public Test

Comments

• igctt Member

  July 29

  @Neoon said:

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

  password login is also failed. I enabled password login once a time and change the password. After kicked out, Can’t access it.

  By the way, I send the ssh -vvvv instance log through dm cause there are ip and some other private message.
• Neoon Community Contributor, Veteran

  July 29

  The Node in India had an outage today due to a fiber cut, both redundant path went down due to unforeseen circumstances, this has been resolved though.
• david Member

  6:49AM

  I've noticed an ipv6 issue in Ho Chi Minh for the past 10 hours or so.

  lxc-hochiminh:~# ping -c10 ipv6.google.com
  PING ipv6.google.com (2404:6800:4003:c0f::71): 56 data bytes
  
  --- ipv6.google.com ping statistics ---
  10 packets transmitted, 0 packets received, 100% packet loss
  
  lxc-hochiminh:~# mtr -zurw ipv6.google.com
  Start: 2026-07-31T06:44:46+0000
  HOST: lxc9bdb76d2                              Loss%   Snt   Last   Avg  Best  Wrst StDev
    1. AS150818      _gateway.incus               0.0%    10    0.1   0.1   0.1   0.2   0.0
    2. AS150818      2400:d760::101               0.0%    10    0.3   0.4   0.3   0.4   0.0
    3. AS???         fd91:3591:8000:200::86       0.0%    10    1.0   0.8   0.7   1.0   0.1
    4. AS18403       2405:4800:ae00:1b00::1:172   0.0%    10    1.5   2.5   1.4  10.4   2.8
          2405:4800:ae00:1b00::1:173
       AS18403       2405:4800:ae00:1b00::1:173
    5. AS18403       2405:4800:f003::979          0.0%    10    1.6   1.8   1.5   3.0   0.4
          2405:4800:f003:8000::c66
       AS18403       2405:4800:f003:8000::c66
    6. AS18403       2405:4802:f500::ebd          0.0%    10    1.8   2.2   1.5   3.7   0.7
    7. AS???         ???                         100.0    10    0.0   0.0   0.0   0.0   0.0
  
• Neoon Community Contributor, Veteran

  8:29AM edited 8:29AM

  @david said:
  I've noticed an ipv6 issue in Ho Chi Minh for the past 10 hours or so.

  lxc-hochiminh:~# ping -c10 ipv6.google.com
  PING ipv6.google.com (2404:6800:4003:c0f::71): 56 data bytes
  
  --- ipv6.google.com ping statistics ---
  10 packets transmitted, 0 packets received, 100% packet loss
  
  lxc-hochiminh:~# mtr -zurw ipv6.google.com
  Start: 2026-07-31T06:44:46+0000
  HOST: lxc9bdb76d2                              Loss%   Snt   Last   Avg  Best  Wrst StDev
    1. AS150818      _gateway.incus               0.0%    10    0.1   0.1   0.1   0.2   0.0
    2. AS150818      2400:d760::101               0.0%    10    0.3   0.4   0.3   0.4   0.0
    3. AS???         fd91:3591:8000:200::86       0.0%    10    1.0   0.8   0.7   1.0   0.1
    4. AS18403       2405:4800:ae00:1b00::1:172   0.0%    10    1.5   2.5   1.4  10.4   2.8
          2405:4800:ae00:1b00::1:173
       AS18403       2405:4800:ae00:1b00::1:173
    5. AS18403       2405:4800:f003::979          0.0%    10    1.6   1.8   1.5   3.0   0.4
          2405:4800:f003:8000::c66
       AS18403       2405:4800:f003:8000::c66
    6. AS18403       2405:4802:f500::ebd          0.0%    10    1.8   2.2   1.5   3.7   0.7
    7. AS???         ???                         100.0    10    0.0   0.0   0.0   0.0   0.0
  

  I will check it as soon as I can, my Internet is dead since yesterday, need to sort that out first.
• Neoon Community Contributor, Veteran

  9:42AM

  @david said:
  I've noticed an ipv6 issue in Ho Chi Minh for the past 10 hours or so.

  lxc-hochiminh:~# ping -c10 ipv6.google.com
  PING ipv6.google.com (2404:6800:4003:c0f::71): 56 data bytes
  
  --- ipv6.google.com ping statistics ---
  10 packets transmitted, 0 packets received, 100% packet loss
  
  lxc-hochiminh:~# mtr -zurw ipv6.google.com
  Start: 2026-07-31T06:44:46+0000
  HOST: lxc9bdb76d2                              Loss%   Snt   Last   Avg  Best  Wrst StDev
    1. AS150818      _gateway.incus               0.0%    10    0.1   0.1   0.1   0.2   0.0
    2. AS150818      2400:d760::101               0.0%    10    0.3   0.4   0.3   0.4   0.0
    3. AS???         fd91:3591:8000:200::86       0.0%    10    1.0   0.8   0.7   1.0   0.1
    4. AS18403       2405:4800:ae00:1b00::1:172   0.0%    10    1.5   2.5   1.4  10.4   2.8
          2405:4800:ae00:1b00::1:173
       AS18403       2405:4800:ae00:1b00::1:173
    5. AS18403       2405:4800:f003::979          0.0%    10    1.6   1.8   1.5   3.0   0.4
          2405:4800:f003:8000::c66
       AS18403       2405:4800:f003:8000::c66
    6. AS18403       2405:4802:f500::ebd          0.0%    10    1.8   2.2   1.5   3.7   0.7
    7. AS???         ???                         100.0    10    0.0   0.0   0.0   0.0   0.0
  

  I don't see any issues with the Node though, IPv6 works fine.
  Please send me MTR's booth ways, so I can take a look.

  Thanked by 1david