Hi all! I have tried a couple of times now to get Discourse up and running on Google Cloud. Currently on my third attempt with creating a VM instance (Ubuntu 18.04 minimal), and manually installing Discourse through terminal. Following the guide , everything seems fine - but having finished ./discour…

I don’t know why I can’t edit my previous post, but moderator may merge them. I just wanted to add that I think my problem and solution MIGHT have been that I was too eager. Because of having installed a faulty plugin, I recently had to scratch and reinstall my discourse instance. When I started …

Hey Bhanu, and thanks for suggesting! Those boxes are already checked! [allowed] Still not working. Trying to ping the site, all seems good: [ping] SSH:ing in to the site, and running netstat to check ports gives this: [ports] But I’m not that familiar with netstat.

I am now thinking that perhaps I am not running a web server? Do I need to install Nginx before/after I install Discourse or something? Following a train of thought from this thread , identical to my issue. Okay, I am beginning to think that this is the issue. It seemed like Nginx was installed, but…

You don’t have to run a dedicated web server unless you plan to use server for more than hosting discourse since discourse comes with nginx server already built in. Could you confirm your server is assigned with a public IP address and the same is configured to allow external connections to ports 22…

Yes. My VM instance on Google has a public IP and is allowing traffic on 22, 80, 443. I reckon this was also demonstrated when I killed the docker-proxy process PIDs (on ports 80 and 443) started Nginx (on port 80) and was able to access the Nginx landing page on my site.

So it indicates something wrong with the installation itself. If it’s a fresh install, its probably easier to just nuke the VM and set up again.

I’ve actually installed it 3 times already, and the ports turn out unbound everytime. Have done three successful installs, but never been able to access the forum. So I’m looking into just using the Google version, (which works but doesn’t let me set SMTP), and then find a way to set SMTP from the G…

Can I somehow set up SMTP after the installation is complete? Following “Step 11” on this link I could [create, because it doesn’t exist, and] edit the discourse.conf file. After doing so, I apparently could restart the “discourse service”, and test my email settings? So that means that I don’t ha…

I’m sorry, I have no clue as to how the Google cloud image is set up. I have done more than a dozen installs (including one in last week) and I’m pretty confident it is probably something to do with the way your VM is configured. This is my prep steps before following the official install Guide: S…

Hm. So weird. But thanks for confirming that it is indeed possible on Google Cloud. I also think Discourse installs well, and that the VM/ports are the issue. Will give it a fourth try tomorrow then. Eventhough I’ve done those prep steps each time. Thanks Bhanu. @pfaffman I have.

Discussie over Google Cloud poortprobleem?

Ondersteuning Installatie

pfaffman (Jay Pfaffman) 27 december 2020 om 03:40 12

Have you not been doing Discourse official Standard Installation?

Topic		Antwoorden	Weergaven
Discourse new install not working on Google Cloud VM Support	4	598	30 april 2019
Need help over installing Discourse using Github Documentation help? Self-hosting	21	1040	23 september 2020
Cannot access Discourse installation Self-hosting	25	2016	29 december 2019
Google Cloud One-Click install issue Self-hosting	4	1828	7 juni 2016
Install fails with port 80,443 on GCP Self-hosting	14	1463	19 juni 2020

Discussie over Google Cloud poortprobleem?

Gerelateerde topics