Thanks for the quick reply!
I tried what you suggested. This time:
dpkg: error: dpkg frontend is locked by another process
Instead of using the same folder, I create a “var/discourse” and install discourse. It ran into the same error but “dpkg --configure -a” works this time and discourse is successfully installed.
It connects fine using the IP address, but not with the domain. Below is the message when trying to connect with my domain. Is it the problem from the server side?
# Your connection is not private
Attackers might be trying to steal your information from **testing.iapct.org** (for example, passwords, messages or credit cards). [Learn more](chrome-error://chromewebdata/#)
testing.iapct.org normally uses encryption to protect your information. When Google Chrome tried to connect to testing.iapct.org this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be testing.iapct.org, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.
You cannot visit testing.iapct.org right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.
I ran ./discourse-doctor. This is the error I got at the end.
cp: cannot create regular file 'shared/standalone/log/var-log/NzM2OWE5M2Q2ZWY3MjJm.txt': No such file or directory
cp: cannot stat '/var/log/NzM2OWE5M2Q2ZWY3MjJm.txt': No such file or directory
The output of this program may be available at http://testing.iapct.org/NzM2OWE5M2Q2ZWY3MjJm.txt
You should inspect that file carefully before sharing the URL.
You can examine the output of this script with
LESS=-Ri less /tmp/discourse-debug.txt