Multiple instances. Visiting the second instance signs out the logged in account on the running instance

EDIT after resolved: This happened when I open the second Discourse instance, not when I start the server.

I have two Discourse directories. I followed the following guide to install it.:

So, the first one, say,

cd ~/discourse
bundle exec rails server --binding=

is running okay, I can sign in, create my topics, etc.

Then I run another Dicsourse instance after changing the config/database.yml to use different ‘database’ name and run it on different port:

cd ~/discourse2
bundle exec rails server -p <different-port> --binding=

It does create those databases additionally. And it runs, sure. But when I visit the first instance that’s been running and refresh, I’m signed out from it. I can log in into the second instance, and start my thing there. And when I log into my first instance, it signs me out from the second instance.

And now I’ve tried running Discourse on Docker, it runs, but when I visit localhost and I get the “Register page”, I’m logged out from the running Discourse.

I’m not trying to use one account for two instances.

How do I keep each account signed-in on its own Discourse instance? (Account ‘foo’ on ‘discourse’ and account ‘bar’ on ‘discourse-2’ instance)

Are these meant to be production instances, or for development purposes?

Correct me if I’m wrong, I’m thinking of Discourse running from a Docker container to be the production instances (or purpose?) and the instances that run from the discourse/discourse repo to be development instance.

I tried running two development instances first, then failed (visiting or starting one instance logs me out from currently running one, but I can log in again which would log me out from the newly started/visited instance if I’m already logged in).

Then tried with an instance running in development instance, and another from Docker, and the same thing happens.

So, I need at least one ‘development purpose’ Discourse to run. And I need one instance for my own personal use. Sure, I could host the personal one of ‘production instance’ on a cloud service, but that would cost me (little amount of) money. Even then, I’m just confused why this is the case when I’m expecting it to just work.

They need to have different host names. Otherwise they try to use the same cookies.


Oh my god. Thank you.

I was able to have each account on each instance not interfere each other’s login by using different browser, or different ‘account bounded chrome instance’ (or something).


The following seem to work

  • Using different ‘chrome’ instances (such as the guest window)
  • Using instead of localhost

What are some other ways to avoid two servers serving clients with same cookie.

Could using ‘alias’ be an example?

Just use two hostfile entries. They can share the same IP, and won’t suffer from cookie collision.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.