Hi dears, unfortunately, my website http://specknz.me/ has stopped opening and I don’t really know what has caused it. Also I’ve got an error: 502 Bad Gateway nginx How could be it sort out without touching the Snapshot on the Digitalocean? Thank you.

Thanks Rafael, I’ve already rebuilded the app, but it still doesn’t work. … Removing old container + /usr/bin/docker rm app app + /usr/bin/docker run -d --restart=always -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GLOBAL_METHOD_CACHE_SIZE=131072 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e DISCOURSE_HOSTNAME=speckme.nz -e DISCOURSE_DEVELOPER_EMAILS=tamerlanium@gmail.com -e DISCOURSE_SMTP_ADDRESS=smtp.gmail.com -h discourse-app -e DOCKER_HOST_IP=172.17.0.1 --name app -t -p 25654:80 -p 443:443 -v /var/discourse/shared/standalone:/shared -v /var/discourse/shared/standalone/log/var-log:/var/log --mac-address 02:f9:8c:dd:3d:63 local_discourse/app /sbin/boot 357203ee7df50c1e85272786c05d1826f773412b6706ad3f9d6de262eb148119 root@discourse:/var/discourse# reboot Broadcast message from itamerlanium@discourse (/dev/pts/0) at 18:51 ... The system is going down for reboot NOW! root@discourse:/var/discourse# Connection to 159.203.205.195 closed by remote host. Connection to 159.203.205.195 closed.

I didn’t understood the log, why the reboot after the rebuild?

I tried to open the website before and after the reboot, anyway it doesn’t work.

Please tail the logs. My bet is a wrong permission so start by tailing nginx log.

Unfortunately the access.log is empty. I found some logs through the error files. access.log error.log.1 error.log.3.gz error.log error.log.2.gz error.log.4.gz root@discourse:/var/log/nginx# GNU nano 2.2.6 File: error.log.1 2016/07/19 00:22:26 [emerg] 1536#0: BIO_new_file("/etc/letsencrypt/live/specknz$ 2016/07/19 17:31:32 [emerg] 1525#0: BIO_new_file("/etc/letsencrypt/live/specknz$ 2016/07/19 17:39:44 [emerg] 4211#0: BIO_new_file("/etc/letsencrypt/live/specknz$ 2016/07/24 07:27:11 [emerg] 1499#0: BIO_new_file("/etc/letsencrypt/live/specknz$ 2016/07/24 18:13:19 [emerg] 1537#0: BIO_new_file("/etc/letsencrypt/live/specknz$ 2016/07/24 18:52:03 [emerg] 1542#0: BIO_new_file("/etc/letsencrypt/live/specknz$ 2016/07/24 22:57:59 [emerg] 1540#0: BIO_new_file("/etc/letsencrypt/live/specknz$ GNU nano 2.2.6 File: error.log.4.gz ^_�^H^@JsoW^@^C��Mo�@^P�{��X�^G�R^Uf? skչK��=�^XE�^C�^F^U��V��/·Y�*^PB/e�oև̇>�+f<� ��^@L �^AGmP�� n��~Ÿ^@^]�^Cd7i�̸^W�$ �}H^Rg˒�2gWɞ�9ەv�V�,�%�Օ?JM�^D�^?��U�e,.vY^Õ��zXʏ^U^R9�ҏǏ؏ȏ,ŏX�{$^_(�� {rؽ�Y^@ ӹt^B��jDɝهk&p^B�(x�^Ç^V(e^S�"^U�)�+�+D^S8�O^S�_a+�^�VrL͇^]ɇ_!�� {Rؽ�YE��ތ�Q4掣+$ ,�oWi~��ŹQ�ŹŹ^Wdֹ¹!^H^@^N �ܗ�ݰ,�q+�ǰu��9~-X��oٰa=V8��ΰưU��|�2�ٰ��-^^V�^W6� ^D�$ 1��?5HC�x� [2�`�`^@^H��^N� �!�N^]R�ӹ'^A^Q9Թr��5g^E^@J�C-�Ĺ^Ry��^RRޟ��C�CB{^N)�ɡơ!α�*�SkImȱ3��αQ�6� ]Ϲ_�^]ı�C�^RSԃڃ^Fу8��A^B�i��ʐ^Lz4H^^6d Qq�^W��A��a?�R{^[2C��ѐ Ðj^~�Ɓ^R�7�^OG�p�$

Those emerg entries on the nginx log mean he’s not gonna run. This is a problem with your ssl setup, it is missing deparams. I recommend setting up ssl again.

[תמונה] tgxworld: /shared/log/var-log/nginx Unfortunately, it gives nothing. root@discourse:~# ./launcher logs app -su: ./launcher: No such file or directory root@discourse:/# cd /shared/log/var-log/nginx -su: cd: /shared/log/var-log/nginx: No such file or directory

Yeah, this is the problem. (“Emerg” = Emergency)

I went through this tutorial https://www.digitalocean.com/community/tutorials/how-to-install-discourse-behind-nginx-on-ubuntu-14-04#prerequisites to recreate SSL Certificate on Nginx for Ubuntu 14.04 and got a message. root@discourse:/opt/letsencrypt# ./letsencrypt-auto certonly --standalone --email tamerlanium@gmail.com --agree-tos -d specknz.me The program exe (process ID 1304) is already listening on TCP port │ │ 443. This will prevent us from binding to that port. Please stop the │ │ exe program temporarily and then try again. At least one of the (possibly) required ports is already taken. root@discourse:/opt/letsencrypt# cd /etc/letsencrypt/live -su: cd: /etc/letsencrypt/live: No such file or directory root@discourse:/opt/letsencrypt# ls acme letsencrypt-nginx certbot letshelp-certbot certbot-apache letshelp-letsencrypt certbot-auto LICENSE.txt certbot-compatibility-test linter_plugin.py certbot-nginx MANIFEST.in CHANGES.rst pep8.travis.sh CONTRIBUTING.md README.rst docker-compose.yml readthedocs.org.requirements.txt Dockerfile setup.cfg Dockerfile-dev setup.py docs tests examples tools letsencrypt tox.cover.sh letsencrypt-apache tox.ini letsencrypt-auto Vagrantfile letsencrypt-auto-source And didn’t get a response similar to this: Let’s Encrypt Output IMPORTANT NOTES: If you lose your account credentials, you can recover through e-mails sent to sammy@example.com. Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/discourse.example.com/fullchain.pem. Your cert will expire on 2016-04-26. To obtain a new version of the certificate in the future, simply run Let’s Encrypt again. Your account credentials have been saved in your Let’s Encrypt configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Let’s Encrypt so making regular backups of this folder is ideal.

Discourse has stopped opening

Product Support Self-hosting

tgxworld (Alan Tan) 26 ביולי,‏ 2016,‏ 2:52am 8

What does

./launcher logs app

give you?

Our nginx logs are actually in /shared/log/var-log/nginx

נושא		תגובות	צפיות
Discourse not serving pages Self-hosting	25	3486	4 באוגוסט,‏ 2020
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	4408	20 בספטמבר,‏ 2022
Installing Discourse With Plesk Onyx (Ubuntu 14.04) Self-hosting unsupported-install	47	13288	10 באוקטובר,‏ 2019
Run other websites on the same machine as Discourse Self-Hosting how-to , advanced-setup	66	141198	30 ביוני,‏ 2026
Seeking help for discourse installation Self-hosting	20	1925	15 במרץ,‏ 2023

Discourse has stopped opening

נושאים קשורים