I am not sure how much information to include in this topic, so let me know if information should be added. Here is a summary:
- I am installing Discourse on a Digital Ocean droplet, using my own ssl keys.
- The initial install resulted in the IP resolving, but not the domain.
- When I added the ssl keys and then performed rebuild, neither domain nor IP resolved.
- The log file had several errors, and I resolved them one by one by looking up the causes in the Discourse forums. There are a couple remaining errors, but the forums said to disregard.
Below is the log file output:
run-parts: executing /etc/runit/1.d/00-ensure-links run-parts: executing /etc/runit/1.d/00-fix-var-logs run-parts: executing /etc/runit/1.d/anacron run-parts: executing /etc/runit/1.d/cleanup-pids Cleaning stale PID files run-parts: executing /etc/runit/1.d/copy-env run-parts: executing /etc/runit/1.d/enable-brotli Started runsvdir, PID is 41 ok: run: redis: (pid 51) 0s ok: run: postgres: (pid 55) 0s rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted. rsyslogd: activation of module imklog failed Server listening on 0.0.0.0 port 22. Server listening on :: port 22. 2019-01-14T01:05:43.285264+00:00 Discourse-sfo2-01-app rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="59" x-info=] start 2019-01-14T01:05:43.280184+00:00 Discourse-sfo2-01-app rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead ] supervisor pid: 52 unicorn pid: 80
This is the port info:
root@Discourse-sfo2-01:~# sudo netstat -plnt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1440/sshd tcp6 0 0 :::22 :::* LISTEN 1440/sshd
The domain is keepinglookout.com, and the ip is 18.104.22.168.
I look forward to any advice anyone has.