While troubleshooting an issue with an independent RCE node, a configuration change caused NX sessions to be interrupted. If you are reconnecting to your lost NX session, you should now be able to resume the previous session. Please contact email@example.com if you had cluster jobs running and are unable to resume your NX session. SSH logins should not have been affected.
There was an unplanned outage today (Wed May 21) at 5pm lasting approximately until 5:15pm. This was caused by a misconfiguration of DNS. This issue has now been resolved. We apologize for any confusion or inconvenience this caused. If you have any questions or concerns, please contact us at firstname.lastname@example.org. Thank you.
Things to check if you are unable to connect to the RCE:
Is there an active outage? We post any outages to the RCE itself, our RCE calendar, and to our outages mailing list in advance of planned maintenance windows. You can also check the HMDC status page. For more information, please see our page on RCE outages.
Are you over quota? If your home directory goes over 500MB, you won't be able to log in to a RCE desktop. Log in via SSH to clean up your home directory. See, How Do I Check My Quota? for more information.
Are you using the right RCE host? You may have been assigned a host other than rce.hmdc.harvard.edu when you applied for your account. It was included in your new account verification email.