I have created a new droplet “Discourse-beta-ubuntu”, then I connected to the Droplet with Putty (root - password) and Discourse’s setup is started.
But setup doesn’t work:
Ports 80 and 443 are free for use
'samples/standalone.yml' -> 'containers/app.yml'
Found 1GB of memory and 1 physical CPU cores
setting db_shared_buffers = 128MB
setting UNICORN_WORKERS = 2
containers/app.yml memory parameters updated.
Hostname for your Discourse? [discourse.example.com]: forum.mywebsite.eu
Checking your domain name . . .
WARNING:: This server does not appear to be accessible at forum.mywebsite.eu:443.
A connection to http://forum.mywebsite.eu (port 80) also fails.
This suggests that forum.mywebsite.eu resolves to the wrong IP address
or that traffic is not being routed to your server.
Google: "open ports YOUR CLOUD SERVICE" for information for resolving this problem.
If you want to proceed anyway, you will need to
edit the containers/app.yml file manually.
Discourse is now installed. Log into your admin account in a browser to continue
configuring Discourse.
I have bought the domaind from register.it and added to Cloudflare. I have changed only DNS, to redirect to Cloudflare.
Hostname for your Discourse? [discourse.example.com]: myforum.us
Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: myforum.us.
WARNING: Connection to http://myforum.us (port 80) also fails.
This suggests that myforum.us resolves to some IP address that does not reach this
machine where you are installing discourse.
The first thing to do is confirm that myforum.us resolves to the IP address of this server.
You usually do this at the same place you purchased the domain.
If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for "open ports YOUR CLOUD SERVICE" might help.
This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type
./launcher rebuild app
Also, you could have used cloudflare as your name server, but just needed to create the A record for your digital ocean server (with the orange cloud turned off), but as long as you remember that digital ocean is where to manage your DNS in the future your current solution is fine.
Did you add additional NS records for the forum.omaggieconcorsi.online subdomain, or is this a quirk of the DigitalOcean DNS interface?
To be clear, you only need NS records for your root domain (omaggieconcorsi.online) unless you plan to delegate DNS to different name servers for specific subdomains.
If you added them yourself I would remove them again, it will work without.
Also please note that while you have redirected three domains to your droplet, Discourse can only operate under a single DNS address. The others will redirect as long as the protocol isn’t specified.
I have added manually forum.omaggieconcorsi.online on DigitalOcean DNS control panel.
During setup, when it asks me “Hostname for your Discourse? [discourse.example.com]:” what should I put, only omaggieconcorsi.online?
Because if I put forum.omaggieconcorsi.online and in DNS there is not this subdomain it shouldn’t work, right? Because Discourse would not find this subdomain “forum”.
You can use any of the three domain names you have pointed at the droplet IP on the understanding that it will be your forum URL, the other two will only redirect.
EDIT: I’m going to assume you want forum.omaggieconcorsi.online.
Delete the records marked with a RED
Probably delete the record marked with a RED
Delete the records marked with a PURPLE if you want to use forum.omaggieconcorsi.online
First impressions: it’s really powerful! even notifications via browser when a user creates a post :o
Then Onebox, very useful for me because I report promotions from other sites, so I just need to put a link and automatically show a preview image of the site and the link, fabulous.
Same thing for bookmarks (keep track of expiring contests, daily, monthly) and all settings on event dates.
I also glimpsed the possibility of uploading various images to external services (I also believe imgur) so as to save a lot of space on the disk (I have users who post photos of gifts received at maximum resolution, obviously not compressed or even resized).
The only things that block me a bit from using it: importing likes from mybb will be very hard (I’m still trying to import at least users and messages from mybb, but this in another thread); if something does not work with the server or I have to reinstall everything will be a mess (with a normal forum just save the files from ftp and the database and reinstall as it was before, but here I have practically nothing, everything is installed by DigitalOcean, I used their marketplace).
I don’t know Discouse really has many useful features that on other forums there aren’t, but on the other side I think it is dedicated to those who are experts in servers, Ruby etc. and who wants to keep up with the various problems. Only PHP and Mysql is simpler.
Discourse doesn’t normally require any expertise. I’ve never had to know any of those things you mention to install and administer Discourse. So I don’t want potential users to be put off by your comment.
Editing a yaml file to add a plug-in is the highest level of technical ability that I have needed and that simple process is well-documented in this forum.
One big exception would be if I needed to migrate data from a different application. But, depending on the application, that has also been done by people who are not experts in any part of IT.
):
- that’s how you move to a new server.