Trouble connecting drupal and discourse

Setup a hosted discourse instance and trying the Drupal Discourse Module:

Reading the Drupal module’s README says:

  • Log into the Discourse instance as an admin and go to the site settings screen /admin/site_settings
    Set force_hostname to be the Drupal url and path in Discourse site settings.
    Eg This will give correct links in emails sent by Discourse.
  • Your forum should now be available at /discourse

“force_hostname” doesn’t exist in my Discourse instance. Has this been deprecated?
Also noticed the Drupal Module was tested with Discourse 1.2.0.beta5 and Discourse is on ver 1.4.
Has anybody tried this module with newest Discourse? Does it work?

That’s very wrong. The referenced setting is restricted to development mode only because of people doing stupid things like that.

Sounds like it’s trying to set up subfolder. You can do that with hosted forums, but it’s a bit expensive.

Reading the page, seems like it doesn’t offer much other than SSO? In that case, might as well skip it.

If you want our official supported SSO follow this topic

The module is trying to embed Discourse into Drupal, so instead of using Drupal Forums you’re using Discourse. Doesn’t look like the module works though. It’s doing some whacky monkey patch with Ember to get Discourse to run on the Drupal page. Not looking like a robust, quick and easy solution to get Discourse in Drupal.

If you want to embed discourse, follow our official supported instructions at

After spending quite a while getting login integration, I finally have OAuth2 working between Discourse and Drupal. See here:

I hope that saves some time for others!

tarek : )

1 Like


Let me share our implementation of SSO based on Drupal 7.56 and Discourse 1.9.0.beta7 using discourse_sso plugin. I have tried the plugin on the subject, even OAuth2 integration but the most interesting were this one. Unfortunately, there is no enough information how to force SSO to run, even Readme does not contain useful information. For that reason, I decided to publish my live configuration.

SSO Drupal Discourse

The configuration is:

Ubuntu 16.04.1 x86_64
Docker 17.06.1-ce
Discourse 1.9.0.beta7
Drupal 7.56
Php v7.0.22
Discourse_sso (from github)

On test environment, both services, Discourse and Drupal are located on the same server as virtual servers managed by Nginx. Both services are managed by two separate config files (see below). The sources how to install Discourse and Drupal are here and here.

I have to mention that Discourse is the main service in our case (because Drupal is more flexible to tune), it uses port 80. But as desired by our team, the forum has moved from root (/) folder to /support folder. The guide I used for this is located here but the settings are described below as well.

Next, Drupal website operates on port 8080 on the same server.

Forum URL:
Drupal site URL:

Config for Drupal /etc/nginx/sites-enabled/drupal:

server {
        listen 8080 default_server;
        root /var/www/html/drupal;
        location / {
                # This line and below allow to use clean links
                try_files $uri /index.php?$query_string;
        location @rewrite {
                rewrite ^/(.*)$ /index.php?q=$1;
        location ~ ^/sites/.*/files/styles/ {
                try_files $uri @rewrite;
        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
                fastcgi_pass unix:/run/php/php7.0-fpm.sock;

Enable clean URLs in Drupal: Configuration - Search and metadata (block) - Clean URLs - Enable clean URLs

To disable a blank screen on root folder apply redirection definition into Nginx config for Discourse:
Config for Discourse /etc/nginx/sites-enabled/discourse:

server {
        listen 80;
        location /support {
                proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
                proxy_set_header Host $http_host;
                proxy_http_version 1.1;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
        # Forward requests from Discourse root to Drupal root 
        location / {
#               proxy_redirect off;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_read_timeout 30m;

Some additional settings to Discourse app.yml:
Add a line to templates:

   - "templates/web.socketed.template.yml"  # <-- Added

Comment a line answering for the port 80 redirection:

# - "80:80"    # http

Add to ‘env’ section:
version: 1.9.0.beta7

Modify your ‘run’ section (completely view):

    - exec:
        cd: $home
          - mkdir -p public/support
          - cd public/support && ln -s ../uploads && ln -s ../backups
    - replace:
       global: true
       filename: /etc/nginx/conf.d/discourse.conf
       from: proxy_pass http://discourse;
       to: |
          rewrite ^/(.*)$ /support/$1 break;
          proxy_pass http://discourse;
    - replace:
       filename: /etc/nginx/conf.d/discourse.conf
       from: etag off;
       to: |
          etag off;
          location /support/ {
             rewrite ^/support/?(.*)$ /$1;
    - replace:
         filename: /etc/nginx/conf.d/discourse.conf
         from: $proxy_add_x_forwarded_for
         to: $http_fastly_client_ip
         global: true
    - exec:
           - sed -i '/no-referrer-when-downgrade/a proxy_redirect http:\/\/\/ \/support\/;' /etc/nginx/conf.d/discourse.conf

Configure your discourse_sso plugin, download
discourse_sso.tar.gz (129.1 KB)


Fill Discourse site URL with your Discourse URL (our case:
Fill SSO secret with your secret token.

Go to your Discourse forum as admin and set the following options:

enable sso - enabled
sso url - <your Drupal URL + /discourse/sso> (example:, this address should not return 404!)
sso secret - fill the same secret token as used above in Drupal.

Open your forum in private browser and click ‘Login’. If above settings were configured properly, you will be redirected to Drupal site. Enter your credentials and next second you will be redirected back to the forum.

p.s. After applying settings you are not allowed to login locally using your credentials. To prevent lost connection to your forum use private browsing and do not close admin settings, use /users/admin-login to login. If something went wrong, follow the instruction how to disable SSO using rails commands:

cd /var/discourse
./launcher enter app
rails c
irb > SiteSetting.enable_sso = false
irb > SiteSetting.enable_local_logins = true
irb > exit

p.p.s. Disable option ‘email editable’ in Discourse admin settings to prevent using a single Drupal account to recreate Discourse user if the email was changed by a user.


Hi, there is another SSO solution for Drupal 7 and Discourse tested on beta13.

  1. Download discourse 7.x-1.5 module.
  2. Install module and dependency (querypath)
  3. Go to Configuration - System - Discourse:

in my case forum works from folder /forum.

  1. Set SSO endpoint (/discourse_sso) and secret in Discourse settings:


You may use both discourse sso plugins mentioned above.