I think that the connection issues were cause by DNS taking a long time to propagate or something not directly related to the install. Because it’s working great now.
The standard install is the one that’s officially supported here on Meta. There are too many variations in the one-click install style ones to be able to provide consistent support for them (and most of the people here are much more familiar with the standard one, which gives a much bigger knowledge pool to drink from )
If you can, you may want to consider getting a digital ocean droplet (or similar) and following the standard install guide, instead of using the linode one.
However, you may still find useful advice and tips if you have a search.
Linode should be fine, but if you use a one-click install (including Digital Ocean’s) then you might not know how to log in to your droplet and edit your app.yml and do a rebuild. But if it’s the same as that, then you’re fine.
The errors mentioned in the first post are not ones that I’d seen before on a standard installation. Maybe you don’t have enough ram?
You could search the site settings for Google. The search on the site settings is a good place to start before searching here. It searches the name of the setting, its description and its value.
It sounds like you may have a typo in your app.yml. Are you making sure to follow the existing formatting when you add the plugin? Ymls are very sensitive to extra spaces, etc.
But would that cause ports on the server to get closed? The Linode support tech I’ve been communicating with said that ports 80 and 443 got closed (and that’s what caused the site to be inaccessible).
The following is the syntax from the plugins section of the app.yml file:
# Plugins go here
## see https://meta.discourse.org/t/19157 for details
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-follow.git
- git clone https://github.com/discourse/discourse-bcc.git