Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading from v3.0.26 to v3.0.27, no more *.lndo.site URLs #2934

Closed
jazty opened this issue Mar 26, 2021 · 8 comments
Closed

Upgrading from v3.0.26 to v3.0.27, no more *.lndo.site URLs #2934

jazty opened this issue Mar 26, 2021 · 8 comments
Labels
bug Something aint working right!

Comments

@jazty
Copy link

jazty commented Mar 26, 2021

After updating from v3.0.26 to v3.0.27 I don't have *.lndo.site URLs for any of my projects.

Steps to reproduce:

Expected results:

Also, trying to access the project.lndo.site URLs doesn't work, so it's not like they simply aren't printing in the "Vitals" summary.

OS: Fedora 33
Docker version: 20.10.5

@jazty jazty added the bug Something aint working right! label Mar 26, 2021
@uberhacker
Copy link
Contributor

I can back up @jazty's claim.

@uberhacker
Copy link
Contributor

uberhacker commented Mar 26, 2021

I also tried rm -rf ~/.lando && lando rebuild -y but the issue remained.

System info:

$ lsb_release -a
No LSB modules are available.
Distributor ID: MX
Description:    MX 18.3 Continuum
Release:        18.3
Codename:       Continuum
$ uname -a
Linux dell-precision-m6700 4.19.0-5-amd64 #1 SMP Debian 4.19.37-2~mx17+1 (2019-05-15) x86_64 GNU/Linux
$ docker -v
Docker version 19.03.15, build 99e3ed8919
$ docker-compose -v
docker-compose version 1.25.1, build a82fef07
$ lando version
v3.0.27

Using the drupal8 recipe.

@serundeputy
Copy link
Collaborator

serundeputy commented Mar 26, 2021

so far we have confirmed the issue on drupal7, drupal8, and drupal9 recipes.

@mikemilano
Copy link
Contributor

mikemilano commented Mar 26, 2021

@serundeputy, @dustinleblanc, and I have tested various projects. It seems to be isolated to drupal6, drupal7, drupal8, and drupal9 recipes.

  • Reproducible on recipes drupal6, drupal7, drupal8, drupal9
  • Not reproducible so far on anything else, including Acquia/Pantheon/Platform recipes running Drupal apps. Integration tests have included the following:
    • Acquia d8
    • Platform d7, d8, d9
    • Pantheon d8

Note that integrations extend _drupaly just as drupal6, drupal7, drupal8, and drupal9 do. Just calling that out because I'd otherwise expect it to be at that parent level if it is in fact specific to Drupal.

via nginx vs apache does not impact the outcome.

@mikemilano
Copy link
Contributor

@jazty @uberhacker Manually declaring the proxy in your .lando.yml file seems to be a workaround while we get this sorted out.

name: mysite
recipe: drupal8
proxy:
  appserver:
    - mysite.lndo.site
    - www.mysite.lndo.site

@rubenvarela
Copy link

Okay, not crazy.

I can confirm this too on D7 and D9.

Going the proxy route. Thanks @mikemilano

@serundeputy
Copy link
Collaborator

If you are swapping in nginx for apache you will want:

proxy:
  appserver_nginx:
    - myste.lndo.site
    - www.mysite.lndo.site

@pirog
Copy link
Sponsor Member

pirog commented Mar 26, 2021

Alright, going to roll a hotfix release with this in a moment!

pirog added a commit that referenced this issue Apr 5, 2021
pirog added a commit that referenced this issue Apr 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something aint working right!
Projects
None yet
Development

No branches or pull requests

6 participants