I’ve now installed Discourse on 2 different VMs. I’m using the official install instructions. One running Debian 12 in a VMWare Fusion instance on a Mac Pro, the other is Ubuntu 24 in a VM running under TrueNAS. They are both on dedicated servers running on my local network with bridged networks …

[image] tknospdr: They are both on dedicated servers running on my local network with bridged networks and have unique accessible IP addresses. If they are not on the public internet with a domain name pointing at them then you can’t do a standard install . You can look at Install Discourse o…

I have a publicly available static IP address and a domain name pointing to that address. I generally use a wildcard A record to point any host to that IP but in my troubleshooting I ran across a post saying that Discourse may not play nice with proxied addresses in Cloudflare DNS so I created a de…

[image] tknospdr: On both, the bootstrap function completes, but I don’t get a working site. Just ‘server not responding’ in a browser. Did you run discourse-setup? Did it pass the connection test?

Am I using the term ‘bootstrap function’ correctly? Just want to be sure we’re talking about the same thing. ./discourse-setup IS the bootstrap, right? So if I say it bootstraps, and the container is running, then the connection test, which happens at the very beginning of the setup has passed. D…

[image] tknospdr: ./discourse-setup IS the bootstrap, right? Well, sort of. It creates a app.yml and then runs ./launcher bootstrap app. If you’ve run it a bunch of times without DNS working right then you’ve hit rate limits with let’s encrypt. The easy solutions are to wait a week or to use…

[image] pfaffman: If you’ve run it a bunch of times without DNS working right then you’ve hit rate limits with let’s encrypt. The easy solutions are to wait a week or to use a different domain name. I’ve only run it once on each VM, and I used a different host name for each. [image] pfaff…

Here’s the errors I found in the install output, none look like show stoppers: 690:M 30 Apr 2025 22:05:22.859 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use 690:M 30 Apr 2025 22:05:22.859 # Failed listening on port 6379 (TCP), aborting. 109:M 30 Apr 20…

Does increasing it to 4 GB RAM help? I think the memory requirements may have gone up.

Cannot get past bootstrapping

Product Support Self-hosting

NateDhaliwal (Nate Dhaliwal) May 1, 2025, 3:21am 9

What are the specs of your VMs? As in, how many vCPUs/RAM is allocated to them?

Topic		Replies	Views
DiscourseID installation issues Self-hosting hosting	4	184	February 13, 2026
After Discourse installation can’t reach it in browser Self-hosting	24	4332	September 5, 2020
Cannot access Discourse installation Self-hosting	25	2294	December 29, 2019
Start failed, address already in use Self-hosting	5	1311	March 8, 2016
Can't access site after installation Self-hosting	10	4264	April 14, 2016

Cannot get past bootstrapping

Related topics