Undortunately I can’t get the basic discourse setup working. It always stops at the exact same point: I, [2019-03-17T15:32:36.676696 #14] INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf cp: cannot create regular file '/etc/nginx/conf.d/discourse.conf': No such file or directory I, [2019-03-17T15:32:36.704154 #14] INFO -- : I, [2019-03-17T15:32:36.705628 #14] INFO -- : Terminating async processes I, [2019-03-17T15:32:36.706182 #14] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 69 I, [2019-03-17T15:32:36.706706 #14] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 185 2019-03-17 15:32:36.707 UTC [69] LOG: received fast shutdown request 185:signal-handler (1552836756) Received SIGTERM scheduling shutdown... 185:M 17 Mar 2019 15:32:36.716 # User requested shutdown... 185:M 17 Mar 2019 15:32:36.716 * Saving the final RDB snapshot before exiting. 2019-03-17 15:32:36.751 UTC [69] LOG: aborting any active transactions 185:M 17 Mar 2019 15:32:36.764 * DB saved on disk 185:M 17 Mar 2019 15:32:36.765 # Redis is now ready to exit, bye bye... 2019-03-17 15:32:36.777 UTC [69] LOG: worker process: logical replication launcher (PID 78) exited with exit code 1 2019-03-17 15:32:36.778 UTC [73] LOG: shutting down 2019-03-17 15:32:36.808 UTC [69] LOG: database system is shut down FAILED -------------------- Pups::ExecError: cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf failed with return # Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params {"cmd"=>["cp $home/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf", "rm /etc/nginx/sites-enabled/default", "mkdir -p /var/nginx/cache"]} 196c92c63a4d6a2a50df35a987b2c8dc75a7c0cea6affc59b45dfe67b7065923 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one I have completely lost my mind trying to figure this out over the course of 5 hours but to no success. I hope somebody can help me with this!

Hey, I’m no expert here but was able to install Discourse on a Droplet at Digital Ocean successfully yesterday. Can you share some more details of your setup (new host? Do you have other software on the server already? Did you read the 30-min install guide?). I spent 2 hours installing Discourse because I failed to read the 30 min guide clearly.

Yeah of course I read the 30 minute install guide and follow everything thoroughly. Yes I have indeed some other software on the system. But you have to know that I’m no little hobbyist trying to have an exciting time trying out new software, but a software developer which has to provide his clients with a working and functioning system. I have a contract with a hosting company already, with special adapted prices, so switching companies is no option for me. I disabled every webservice, even cleared out any left over nginx configuration and finally uninstalled nginx completely, so it can’t mess with discourse. I also don’t think there is any issue with existing configuration. Even when I provided discourse with the required files (already populated with configuration) it gave me the same error. I then cleaned everything thoroughly and tried to strictly follow the install guide. Still same error! EDIT 1: My server is a debian machine with full root access btw. So there shouldn’t be an issue there

Yes I ran discourse-setup. I have well over 1gb of ram and answered all the questions. I redirect my domain through an a-record to the server. I have let’s encrypt certificates for all my domains under the default directory /etc/letsencrypt/live/domain.name.com/.... I even provided my email when prompted to input one for let’s encrypt. I also tried (before cleaning everything and trying to follow the 30-minute guide) to remove any entry from the templates, that contained a copy command as stated in the errror (cp /var/www/discourse/config/nginx.sample.conf). After I did that, it ran for approx. 3 minutes longer, but it then terminated again (I remember that there was some issue with copying some other files, but can’t remember exactly, as this was last week). EDIT 1: Up until this point I had no problem whatsoever with my server including my redirection through the a-record, as well as installing software, etc. It just behaves like a normal debian stretch, installed on my pc. Except for discourse somehow. Also I can’t imagine that a misconfiguration of some dns settings can prevent the discourse-setup to copy a simple file!

[image] DustVoice: I redirect my domain through an a-record to the server. You mean that theA record points directly to your server’s public IP? [image] DustVoice: I have let’s encrypt certificates for all my domains under the default directory /etc/letsencrypt/live/domain.name.com/... Oh. That sounds like at least a piece of the problem. If you have another web server running then you can’t follow the 30 minute install. It’s easiest if you install Discourse on its own server. If you want to install it with another web server, you’ll need to search here for instructions for setting it up with another web server. And if you have some other web server in front, then you do not want to configure let’s encrypt in Discourse, as whatever other web server you have will be responsible for https.

Yes my a record points directly to my servers public ip You have misunderstood me, or rather I didn’t make myself very clear. There is no other webserver running at the moment. I backed everything up from apache and uninstalled nginx and apache completely. There is no webservice running at the moment, except of course the sshd service, which I need to do anything on the server at all. Also I tried that. I tried adding my certificates to a nginx config I placed under sites-available, but without success. I also tried to follow the tutorial under Run other websites on the same machine as Discourse, but to no success! It always fails at the copy step. I thought it would be some issue with the docker image, or something but I cloned the latest master branch!

Sorry. I’m that case, my only guess is that there is something wrong with the docker installation. How did you install docker?

I have installed docker with apt, as I would try with nearly any package first…

The command sudo apt list --installed | grep -i docker produces the following output: docker/stable,now 1.5-1+b1 amd64 [installiert] docker-ce/stretch,now 5:18.09.3~3-0~debian-stretch amd64 [installiert] docker-ce-cli/stretch,now 5:18.09.3~3-0~debian-stretch amd64 [Installiert,automatisch] docker-compose/stable,now 1.8.0-2 all [installiert] python-docker/stable,now 1.9.0-1 all [Installiert,automatisch] python-dockerpty/stable,now 0.4.1-1 all [Installiert,automatisch]

I’d recommend using get.docker.com as I think the install doc recommends. Apparently the Debian people and the docker people don’t get along and the default version is ancient.

Installation fails on my Debian server

Product Support Self-hosting

pfaffman (Jay Pfaffman) March 17, 2019, 6:32pm 4

You ran discourse-setup? Do you have at least 1gb of ram? You answered all the questions? Do you have dns configured? (if not, you need not configure let’s encrypt).

Topic		Replies	Views
Discourse not serving pages Self-hosting	25	3470	August 4, 2020
Discourse has stopped opening Self-hosting	36	6436	August 8, 2016
Seeking help for discourse installation Self-hosting	20	1921	March 15, 2023
After Discourse installation can’t reach it in browser Self-hosting	24	4380	September 5, 2020
Discourse installation for beginners but are willing to be part of the community Self-hosting	62	5286	September 17, 2019

Installation fails on my Debian server

Related topics