2.7.0.beta2 upgrade mislukt

@pfaffman I did use the discourse official installation process to the letter, including the use of PuTTY referenced in that official installation document.

It is possible that you derived the opinion how I used DO 1-click install and think that I should depend on DO:

If you want help with Digital Ocean’s one-click installation and want to “rely on DO folks to ensure reasonable behavior”, then you should rely on them to support you.

My reference to 1-clock install comes from the recent email from Discourse:

Hooray, a new version of Discourse is available!

Your version: 2.7.0.beta1
New version: 2.7.0.beta2

So, the current situation is that

  • I genuinely appreciate your help, Jay :revolving_hearts: knowing that you make your living from helping people with Discourse. Despite me not looking like a potential customer, you spent time pulling me out of the weeds.
  • I managed to install the 2.7.0.2 .beta2 upgrade, easy as a breeze, once I learned that the PuTTY is misbehaving regardless of the keep-alive settings I applied. So, I switched from SSH-based authentication to userid / password pair, logged in the droplet host, and run the ./launcher rebuild app command successfully.

Many thanks to everyone who provided parts of the solution.