'This page is not correct' after installation
Description
First want to say, this looks like a GREAT project and I'm excited to get it going and (I hope) contribute back where I can!
But after following the release installation guide, my instance just loads a page titled "This page is not correct" with a broken image and the headline "We're sorry, but something went wrong on our end."
I'm not sure how to proceed from here. I think this is probably something peculiar to Digital Ocean, so I guess what I'm asking for is support in diagnosing what I need to fix. I did have to change one thing about the Let's Encrypt setup (#770 (closed)) so maybe that's it?
Steps to Reproduce
-
Followed the installation guide, with the exception of changing the Let's Encrypt webroot to
/var/www/html
(see #770 (closed)). -
Loaded the website.
Expected behaviour:
A home page or login page of some kind. (I'm actually not sure what one should see after installing!)
Actual behaviour:
Error page titled "This page is not correct" with a broken image and the headline "We're sorry, but something went wrong on our end."
Reproduces how often:
Every time.
Versions
Mobilizon: 1.2.3, installed on a Digital Ocean droplet with Ubuntu 20.04 (LTS) x64, 1GB RAM. Happens in Firefox and Chromium on Linux (Linux Mint 20.1).
Additional Information
Looking in the browser's inspector, I see 502 Bad Gateway
on the logo. When I look at the nginx logs, I see a lot of things like this:
2021/07/08 03:10:53 [error] 11792#11792: *90 connect() failed (111: Connection refused) while connecting to upstream, client: IPADDR, server: DOMAIN.com, request: "GET /favicon.ico HTTP/2.0", upstream: "http://127.0.0.1:4000/favicon.ico", host: "DOMAIN.com", referrer: "https://DOMAIN.com/"
(IPADDR and DOMAIN replaced)
That's why I thought it might be an issue with the nginx SSL setup, because that reminds me of mixed-content errors (https trying to load http resources). But nginx -t
says the syntax is OK and tests successful, and I don't know enough about what the mobilizon.conf
is doing to understand how to edit it. And I confirmed with sudo nc -z
on my local machine that both ports 80 and 443 are connecting.
I'm a little confused about where in /opt/mobilizon
the actual files being loaded in the website reside, but per the installation process, it's mobilizon
that has ownership of that directory, not www-data
. Does that need to be changed?
If it's not either of those things, then I'm not sure what to do next to find the source of the problem. Any help or advice would be really appreciated, thank you!