Site inaccessible after upgrading from 3.4.0 to 3.4.1

Support
,
4

We are experimenting with an AI responder, it ships whispers here, in this case it did have some reasonable advice:

Hello, it looks like your issue could be resolved by investigating the server logs to diagnose what went wrong after the upgrade. Here’s how you can proceed:

  1. Check the Discourse error logs in the Admin UI:

    • If you have admin access and the site is still partially accessible, you can check logs from the admin panel. Navigate to /logs to find error messages.

  2. Inspect other server logs:

    • Run the following commands on your server:
      cd /var/discourse
./launcher enter app
cd /shared/log/rails
less production.log
      Use less or similar tools to read the logs and identify potential errors.

  3. Check NGINX Logs:

    • You can check the NGINX logs for web server errors with:
      cd /var/discourse
./launcher enter app
cd /var/log/nginx
less error.log

  4. Network & DNS Issues:

    • Run tests to ensure your domain’s DNS resolves correctly and ports like 443 and 80 are accessible.

Let us know what you find in the logs, and we can provide more specifics to help resolve the issue.

Helpful resources:

Additional context:
If the issue persists, common causes might be:

  • A plugin incompatibility after the upgrade.
  • Insufficient memory/storage during the rebuild.
  • Configuration changes in app.yml.
2 Likes