commit 9ecb1c8aa5a8adb41262ad1c24d63430abee49c6 parent 941893a774c83802afdc4cc76e1d30c59b6c5585 Author: Alex Schroeder <alex@alexschroeder.ch> Date: Tue, 3 Jan 2023 10:13:52 +0000 [docs] Add troubleshooting section for Apache (#1291) Diffstat:
| M | docs/installation_guide/apache-httpd.md | | | 8 | ++++++++ |
1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/docs/installation_guide/apache-httpd.md b/docs/installation_guide/apache-httpd.md @@ -217,3 +217,11 @@ Everything working? Great! Then restart Apache HTTP Server to load your new conf ```bash sudo systemctl restart apache2 ``` + +## Troubleshooting + +If you cannot connect to the site in your browser, the reverse proxy setup doesn't work. Compare the Apache log file (`tail -F /var/log/apache2/access.log`) with the GoToSocial log file. Requests made must show up in both places. Double check the `ProxyPass` setting. + +If you can connect but your posts don't federate and your account cannot be found from elsewhere, check your logs. Federation is broken if you see messages attempting to read your profile (something like `level=INFO … method=GET statusCode=401 path=/users/your_username msg="Unauthorized: …"`) or post to your inbox (something like `level=INFO … method=POST statusCode=404 path=/your_username/inbox msg="Not Found: …"`). Double check the `ProxyPreserveHost` setting. + +If you can connect but you cannot authorize your account in a Mastodon client app, check your headers. Use `curl -I https://example.com` and look for the `Content-Security-Policy` header. If your webserver sets it, you might have to unset it. One way to do that is to use `Header unset Content-Security-Policy` in the Apache site config file (something like `example.com.conf`).