Users cannot log in to new site in multisite

I am working with the Drupal multisite functionality. I have been asked to implement the following architecture:

mysite is a Drupal site with several angular pages. mysite/backend is a separate site with a separate user store that mostly acts as a headless Drupal system. For political reasons, it is very important that the users in mysite/backend not be stored in the same database as the users in mysite .

Anyway, from what I have read about Drupal multi-sites, I have taken the following steps.

  1. I started with a working site and performed the following steps to add a second one
  2. Create a symlink, making the /backend a symlink to the web root:

    ln -s backend . 
  3. Add entries to my sites.php (because with our deployment workflow, the site name cannot always match with the domain name. Also allows us to test with xip.io).

    $sites['mysite.dev'] = 'mysite';  $sites['mysite.dev.backend'] = 'mysite.backend'; 
  4. I created a directory named mysite.backend .

  5. In mysite.backend, I created a directory corresponding to all directories in mysite.
  6. In mysite.backend, I created the following settings.php file:

    $databases = array (    'default' =>    array (      'default' =>      array (        'database' => 'XXXXXX',        'username' => 'XXXXXX',        'password' => 'XXXXXX',        'host' => 'localhost',        'port' => '',        'driver' => 'mysql',        'prefix' => '',      ),    ),  );   $update_free_access = FALSE;  $drupal_hash_salt = 'k_vtgGjzCyq0mp0dsxDk1gILuEs6G5ODP5aJuQsAUuc';  $base_url = 'http://mysite.dev/backend';  // NO trailing slash!  ini_set('session.gc_probability', 1);  ini_set('session.gc_divisor', 100);  ini_set('session.gc_maxlifetime', 200000);  ini_set('session.cookie_lifetime', 2000000); 
  7. I go to /backend/install.php and go through the install process. Everything goes smoothly

  8. I click the link to view the new site, and enter the admin login credentials (for the new site. I made it a point to have separate logins for each site)

My problem is that when I go to the /backend directory of my test site and log in with my credentials, I get the standard authentication error behavior if I login with an invalid username or password, but when I supply the correct credentials, I get redirected to /backend/node, but I see no indication of being logged in. If I try to go to the admin pages, I get an access denied error. I still see the login block. If I click the reset password link, I get a one-time login link in my email, but when I click it, I get a message that says that the link has expired.

Forgive me if this is too verbose or missing details. This seems to be a messy problem. Has anyone run into similar issues with Drupal?

This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

Users cannot log in to new site in multisite

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.