lando.yml portforward doesn't work

[spencerthayer]

This is a persistent issue already well documented in Fixing DB port with portforward is not working lando/lando#39 and Locking down ports for external database connection not working. So I don't feel I need to add additional documentation to this, but I should note that I too am experiencing this issue with the latest v3.11.0 installation but with a Pantheon configuration- not PlatformSH.

I understand this isn't critical but are there any insights as to when this might be resolved?

[amaisano]

Same issue on v3.18.0. Cannot set my database portforward to 3307. Use to work in the old days :(

Lando is just handing out random port IDs as if it wasn't set to portforward at all.

[lsmith77]

I have the same issue .. had to remove

services:
  database:
    portforward: 3307

Otherwise I got

Starting dashboard_database_1 ... error

ERROR: for dashboard_database_1  Cannot start service database: driver failed programming external connectivity on endpoint dashboard_database_1 (bc3d3ae41f8de886345ee25698849203242732add3d6a3dc8c5058f4b88e1035): Bind for 127.0.0.1:3307 failed: port is already allocated

ERROR: for database  Cannot start service database: driver failed programming external connectivity on endpoint dashboard_database_1 (bc3d3ae41f8de886345ee25698849203242732add3d6a3dc8c5058f4b88e1035): Bind for 127.0.0.1:3307 failed: port is already allocated
ERROR: Encountered errors while bringing up the project.

[lsmith77]

here is the full lando file. I am using plain lando (ie. not pantheon or platform.sh)

name: dashboard
recipe: laravel

proxy:
  appserver_nginx:
    - dashboard.lndo.site
  mailhog:
    - mail.lndo.site

services:
  database:
    portforward: 3307
  node:
    type: node:14
  mailhog:
    type: mailhog
    portforward: true
    hogfrom:
      - appserver_nginx

tooling:
  npm:
    service: node
  node:
    service: node

config:
  via: nginx
  php: '8.0'
  composer_version: 2-latest
  xdebug: false
  webroot: public
  database: mariadb:10.5

[reynoldsalec]

Using that Landofile on Lando v3.19.5 I'm not able to replicate the issue.

If you've ruled out another service occupying the port, is it possible that a security service or network-specific ruleset might be blocking access? I've seen similar-ish issues be resolved when users moved off a specific network (or tried on a computer that had a different security regime), sometimes that can help debugging.

[lsmith77]

FYI I am using v3.18.0