Wrong site served when multiple sites in one stack

soniktrooth

I have a stack that contains multiple sites each with a {sitename}.dev domain. If I start the stack and visit siteA.dev everything works as expected. When I visit siteB.dev it serves me siteA until I restart the stack and visit siteB.dev.

Am I holding it wrong?

Indigo

Weird! I haven't come across this before. Thanks for the heads up.

As a first test, can you try visiting the sites directly using their assigned ports (eg sitename.dev:50001)? This will bypass the reverse proxy, thereby ruling that out. You can find their assigned ports by checking their site config while the stack is running.

Let me know what you find.

soniktrooth

It seems to have the same result. It's always serving siteA

soniktrooth

I've done a rebuild on my stack and it seems to have resolved it for now—I will report back if I see it again.

Indigo

Thanks for the report! If anyone else experiences this please let us know.

However, I think it's possible this was just a "beta thing" — the service configs have changed occasionally throughout the beta releases so if your stack hasn't been rebuilt recently it may be using an old config. This could conceivably cause randomness (although I can't think of any actual possibilities.)

Hakuro

I recently installed the app, running version 1.25.2, and unfortunately, it is still encountering the same issue.

Indigo

Hi Hakuro, sorry to hear this strange one has resurfaced for you!

Can you clarify what you're running that is at version 1.25.2? Indigo itself is only at version 1.0.0-rc.6 (113) right now.

Is there any chance you could put together a test stack that demonstrates the issue, and send it to me at hello@indigostack.app?

Hakuro

Hi Indigo, my apologies for any confusion. The version is Indigo v1.0.0-rc.6 (113), and the stack comprises Nginx 1.25.2, PHP 8.2.9, and MySQL 8.1.0. It's getting late here. So, I'll send you an email with the detailed information tomorrow.

soniktrooth

This feels related because I'm assuming it's a reverse proxy thing but I can't seem to run a Drupal site without explicitly providing the port number—haven't been able to for a while now. I just get 502 bad gateway. It's not usually a problem just adding the port number but some times it does get in the way. @Indigo do you think this is related or should I open a new ticket?

Indigo

soniktrooth I can't seem to run a Drupal site without explicitly providing the port number

If you're experiencing this even when there are no other PHP applications in your stack, then I now believe this issue is indeed different, so yes please, do create a new issue for that one.

Regarding the main theme of this issue (problems with multiple Drupal sites), my research thus far is indicating that the cause is the shared PHP service.

A quick way to work around it for now is to NOT share a PHP service between the sites, but rather to add multiple PHP services, even if they are the same version. So for example, to run two Drupal 10 sites, add two PHP 8.2 services, and power the first Drupal site using one PHP and the other Drupal site using the other PHP.

Let me know how you get on!

Indigo

I'm starting to think Drupal may be a common element here, in which case we'll keep it all together for now. Do you recall if you were running two Drupal sites by any chance, in your opening question in this thread? And if so, which version(s)?

soniktrooth

Yeah, they were both Drupal sites. I believe initially they were both 9 but the behaviour I'm seeing now is with 10

Indigo

One more question: were you using Apache or Nginx to serve those Drupal sites?

soniktrooth

nginx

soniktrooth

Just tried with Apache and I'm getting same 502

Indigo

Cool, I'll have a go with Nginx + 2 x Drupal 10's.

Indigo

I defined a stack with nginx & PHP 8.2, with sites https://drupal-a.test and https://drupal-b.test both pointing at their own fresh d10 installs and it all worked as expected.

@Hakuro & @soniktrooth — what version of nginx is running in your system stack's Nginx Reverse Proxy? The current is 1.25.3. If yours is older it could be worth blowing away your entire system stack and having Indigo build you a fresh one (the rp nginx config may have changed since your version).

To do this:

shut down Indigo
delete ~/.indigo/stacks/system-stack
restart Indigo

(Right-clicking the System stack and choosing "Rebuild..." should do this for you but it appears there's a bug and that isn't working right now.)

Indigo

Forget all those ideas, I've replicated the problem now. I previously hadn't completed the setup of the two Drupal sites. Digging into it now...

soniktrooth

/giphy popcorn

Hakuro

@Indigo, ideally, it shouldn't be set that way, but the implemented workaround has solved the issue.

Indigo

Hakuro ideally, it shouldn't be set that way, but the implemented workaround has solved the issue

I absolutely agree. The workaround is a hack not a fix. You should absolutely be able to use a single PHP server across multiple sites. Once we have v1.0 out this is definitely an issue I want to dig deeper into.