ElasticHosts Help Centre

CentOS 6 container issue after host reboots

Updated Aug 30th, 22:47 BST

Timeline

Updateabout 25 days ago

Another way to mitigate this:

  • Login to the container as the emergency user<br>
  • type 'passwd' to reset the 'root' password<br>
  • SSH to the container as root<br>
  • Edit this file: /etc/security/limits.d/90-nproc.conf<br>
  • Change where it says 1024 to unlimited<br>
  • Save<br>
  • Log back in as the desired user
    <br><br>
    We will be rolling out this update to affected users soon.

Identifiedabout 26 days ago

Some customers have reported issues with accessing CentOS 6 containers over SSH after the maintenance. The failed SSH login attempts results with the error shell request failed on channel 0.
<br><br>
We are working on identifying the cause of this issue. SSH sessions with private-key authentication as root user are not affected, so please this authentication method for SSH connections while we resolve the problem. <br><br>You can add your SSH keys to your containers' authorised keys either by updating /root/.ssh/authorized_keys via emergency SSH connection or by adding your SSH key to your user profile on the Profile page's Authentication tab.