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!

[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]

ok I’ll try. Does this script also install docker-compose? Or better, what versions should I uninstall? Also I figure you just have to do curl get.docker.com | sh right?

I don’t think it includes docker compose. Strangely, the docker people think that they should include docker compose for windows (and maybe Mac? I haven’t paid attention or ever used docker compose partly because there isn’t any obvious way to get a current version). Remove everything to do with docker and then run the curl pipe you included.

I installed the new docker version successfully (version 18.09.3) and cleaned everything from my previous attempts again and tried to follow the tutorial very thoroughly. Still getting the same error. Paste.ee A free, easy to use Pastebin. This is my console output. The error is at the very bottom (I removed personal information like for example the password) EDIT 1: (didn’t post the link)

Looks like the app.yml is broken. Can you share it here? (remove personal information)

Installation fails on my Debian server

Product Support Self-hosting

pfaffman (Jay Pfaffman) March 17, 2019, 7:51pm 11

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.

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