User macr encountered issues typing ‘@’ (which produced ‘2’ instead) and pasting text in the DigitalOcean Recovery Console while installing Discourse on a MacBook. This blocked progress at the email/SMTP configuration step. ClawdiaWolf suggested trying SSH instead of the VNC-based console, noting past similar issues with DigitalOcean’s VNC. macr tried creating a new droplet with SSH access but still faced the same console issue. Eventually, macr resolved the problem by copying the console’s pop-up link and opening it directly in a web browser — where ‘@’ and pasting worked normally. KhoiUSA affirmed the fix and recommended using an SSH client if the issue recurs. The root cause appears tied to DigitalOcean’s browser-based Recovery Console behavior on certain devices or browsers, particularly when accessed via pop-up windows rather than direct browser tabs.
Hi! I’m following the steps to install Discourse with DigitalOcean. I managed to create a droplet and add Discourse to it, my problem is that I’m not able to type ‘@’ in the console (I only get a ‘2’), and I’m not able to paste anything into it, so basically I’m stuck at the installation step where I’m supposed to enter the email and SMTP settings in the console. I’m at a MacBook, if that makes any difference. And I wasn’t able access the Droplet Console at DigitalOcean so I’m using the Recovery Console. Am I doing anything wrong or is there something I’m missing in regards to not being able to type ‘@’ or pasting into the console? Any help would be appreciated! Thanks in advance!
Do you have the same issue if you boot normally and use ssh instead? I’ve had this issue in the past with their VNC consoles but never via SSH. For the record, my device is a late 2017 MacBook Air.
Thanks for your reply! So I deleted the droplet and created a new one choosing to create it with SSH instead of password, if that’s what you meant. But unfortunately it didn’t change anything in the console.
Problem solved, I believe. What seems to have been working for me was to copy the link in the pop up window that opened up when trying to reach the console, and pasting the link right into the web browser. Once there—in the browser and not the pop up window—I was able to type ‘@’ and paste text.
