A user (infered5) is experiencing an issue with their Digital Ocean Ubuntu droplet, where it tries to reinstall Discourse every time they connect through PuTTY. The issue is caused by the Digital Ocean “one click” installer, which sets up the installation in a way that causes this prompt.
infered5 is prompted to enter email addresses, usernames, and passwords, even though Discourse is already installed. To temporarily bypass this, jomaxro suggests using Ctrl + c to exit the script.
infered5 later found that commenting out the line /var/lib/digitalocean/discourse.sh in ~/.bashrc (e.g., using nano or FTP editing) stops the script from running. It is also recommended to create a user and log in with an SSH key for added security (dbm).
Every time I try to connect through PuTTy to my DigitalOcean Ubuntu 16.04 x64 droplet to connect to the terminal, it prompts me, in a way I cannot escape, to reinstall Discourse. Since it’s all installed nothing happens and my settings and users are all there, but it’s very annoying and eating up processing power.
It’s the same prompt as the initial startup when you choose the preconfigured Discourse droplet on DigitalOcean. It prompts the email address to use, username and password, mail server API key, etc etc. How do I disable this?
This is using the DigitalOcean “one click” installer, right, not the official installation instructions? If so, there have been previous discussions about this here, but ultimately you probably want to contact DigitalOcean support, as they were the ones who setup their install in this weird way, and it’d be helpful to them if they knew how much confusion their design was creating.
Yup, this is what I see every time. Just spamming enter and letting it go through yields no data loss or hiccup in performance from the end user’s side, but takes about 30 seconds for my particular droplet speed before I can actually do anything from the terminal.
I’ll contact DigitalOcean support and see what they have to say. Thank you!
Check ~/.bashrc and comment out /var/lib/digitalocean/discourse.sh to #/var/lib/digitalocean/discourse.sh. You can probably do this with nano or FTP editing.
If not immediate, a reload should stop that line from being loaded and the script should stop.