Andre_de_Nardi_Senna_Moraes reports that their Discourse community is unable to receive emails, likely due to an outdated service. Attempts to manually update via SSH caused instability, and with no email access, they cannot transfer site ownership. The original developers are no longer with the company, complicating recovery. pfaffman confirms SSH access means they retain control and suggests restoring stability, then migrating the site to a new VM using rsync if DNS is可控 (as shown in this guide). If DNS isn’t accessible, moving to a new domain is the fallback. Andre_de_Nardi_Senna_Moraes acknowledges the advice and plans to investigate.
The platform tells us to update the service manually. We did try to send the inputs on our SSH, but this has brought instability to the pages.
Also, all of the developers who made this application are no longer employees of the company. To make things worse, as we have not access to e-mail, we can’t transfer ownership of the site. Can anybody share some light on this?
Ah. So you can ssh to the server, so you still have control. That’s good.
You’ll probably need to find a way to fix that.
Do you have control of DNS to the server? If so, you can make a new VM, backup the existing site, and transfer the data to the new server. See, for example Move a Discourse site to another VPS with rsync.
If you do not have control of the DNS then the best you can do would be to move the site to a new domain name.
