Multi-subdomain Sessions in Laravel

Pangratios Cosma
3 min readJan 25, 2019


I use Mac OS and Laravel Valet to develop my Laravel applications.

Part 1 is prerequisite configuration needed to make this work on your local environment.
Part 2 is framework configuration to enable session sharing across subdomains.

Let’s assume two projects, blog1 and blog2.

Assuming that Valet is already setup, navigating to blog1.test and blog2.test shows the respective app home pages.

Laravel allows to share session between subdomains, so if we could get blog1.test and blog2.test under one domain, the framework, under the right configuration, would do its magic and enable us to share same session across both apps.

I will not go into detail how to get your applications under same domain on production servers, since I feel there are many places you can find that information and relies on your cloud/hosting provider.

Part 1:

The first part of this tutorial is to get multiple projects under one domain, for example .blog.test.

At the end of this part, Valet should be able to serve our apps on and

Essentially, we create symbolic links to our project folders and call valet link inside them.

The two projects:



  1. Make sure you go to each folder and do valet link
  2. valet links should show these two folders (and maybe more)
  3. cd /Users/xyz
  4. mkdir
  5. mkdir
  6. cd /Users/xyz/
  7. valet link
  8. cd /Users/xyz/
  9. valet link
  10. cd /Users/xyz/
  11. rm -rf
  12. rm -rf
  13. ln -s blog1
  14. ln -s blog2
  15. Navigate to and confirm you can load your app
  16. Navigate to and confirm you can load your app

Part 2:

Now we are ready to configure Laravel.

It’s important to note that the session data needs to be somewhere both applications can connect to even if they are on different servers. Therefore, the best solution would be to use redis or database.

The following configuration must be applied on both projects:

Both apps must use same APP_KEY:
Copy APP_KEY from blog1 to blog2

SESSION_DRIVER = database or redis

SESSION_COOKIE = blog_session

SESSION_DOMAIN = .blog.test

If you choose SESSION_DRIVER to be database, you will have to make sure you have a sessions table. You can do that by calling the following commands. Since the projects share the same database, you only have to run these in one project:

php artisan session:table

php artisan migrate

If you choose SESSION_DRIVER to be redis, you will have to make sure the name of the collection holding the sessions is the same. You will find this in cache.php:

CACHE_PREFIX = blog_cache

It didn’t make sense when I first saw this, but its the only way I could get it work.

You can now navigate to, login and then open You are already logged in!


  • With Laravel 6 and onwards, there is another setting that needs to be shared between the projects. Look for redis.options.prefix in database.php.


  • Make sure you clear you cookies if you have had any unsuccessful attempts in your setup or configuration. It might also be a good idea to clear your sessions table if using database as SESSION_DRIVER. If using redis, you can flushall.
  • Make sure that encrypt property, found in session.php, has same value in all the projects involved.