LDAP Discourse VM
Opened this issue · 6 comments
Hi, I have a problem with install this plugin on my VM Debian with Discourse. You prefer install this in app.yml file but I haven't this file. I try via link https://docs.bitnami.com/aws/apps/discourse/configuration/install-plugins/ but I have a lot of errors. Can someone help me?
Can you post the command you used to install the plugin? Also, what errors are showing?
I used the command below. Is it right way?
cd /opt/bitnami/apps/discourse/htdocs
RAILS_ENV=production bundle exec rake plugin:install repo=https://github.com/jonmbake/discourse-ldap-auth.git
RAILS_ENV=production bundle exec rake assets:precompile
That looks correct according to the Bitnami docs. This method of plugin installation is specific to Bitnami, i.e. they provide the rake plugin:install task. Are any errors logged when you run the commands?
Also, the example repo PLUGIN_REPO_URL does not have .git, so maybe try:
cd /opt/bitnami/apps/discourse/htdocs
RAILS_ENV=production bundle exec rake plugin:install repo=https://github.com/jonmbake/discourse-ldap-auth
RAILS_ENV=production bundle exec rake assets:precompile
After this, when I tried to open admin panel (administration, settings) I have server error, error code 500 Internal Server Error
I restart apache with commant sudo /opt/bitnami/ctlscript.sh restart apache and now I can't login also
We're sorry, but something went wrong.
The issue has been logged for investigation. Please try again later.
Error ID:
c2a09044
Details:
Web application could not be started by the Phusion Passenger application server.
Please read the Passenger log file (search for the Error ID) to find the details of the error.
You can also get a detailed report to appear directly on this page, but for security reasons it is only provided if Phusion Passenger is run with environment set to development and/or with the friendly error pages option set to on.
For more information about configuring environment and friendly error pages, see:
Nginx integration mode
Apache integration mode
Standalone mode
You would have to read the log file to determine the underlying issue. Can you see what error is showing in the log file?