Cannot make any calls between services (and even inside service's own container)

[tpluscode]

Tell us about your setup

What is your lando version and operating system?

v3.0.11 on macOS 10.15.5

Tell us about your .lando.yml

Paste in the contents of your .lando.yml this is SUPER HELPFUL for us.

Example:

name: wikibus-apis
services:
  sources:
    type: node:custom
    command: node --inspect=0.0.0.0:34567 -r ts-node/register --inspect packages/sources/index.ts
    port: 34566
    ssl: true
    overrides:
      image: node:14
      ports:
        - '0.0.0.0:34567:34567'
    moreHttpPorts:
      - 34567
  users:
    type: node:custom
    command: node --inspect=0.0.0.0:34667 -r ts-node/register --inspect apis/users/index.ts
    port: 34666
    ssl: true
    moreHttpPorts:
      - 34667
    overrides:
      image: node:14
      ports:
        - '0.0.0.0:34667:34667'
proxy:
  store:
    - wikibus-store.lndo.site:3030
  users:
    - wikibus-users.lndo.site:34666

You can find the entire project on https://github.com/wikibus/apis

Tell us about the command you were running

lando start
docker exec -it wikibusapis_sources_1 bash

curl https://wikibus-users.lndo.site/user/foo
curl https://wikibus-sources.lndo.site/
curl http://sources.wikibusapis.internal

Tell us about the error you got

It seems impossible to reach the APIs running in the sources and users services containers. I want to call between services but even trying to reach sources from its own container is impossible, trying any of the URLs: proxied as well as *.internal

All those calls inside the container fail with Failed to connect to X port 80: Connection refused but I can definitely reach my apps over the lndo.site proxy from the host system

Tell us more

The code in the repo does not reflect that but I tried all kinds of ways to make sure that the services listen on all hosts. app.listen(port, '0.0.0.0') in express as well setting 0.0.0.0 as shown above to make sure that lando also complies.

[tpluscode]

Aha, so yes, the only way that works is to call http://users:34666 😞

[tpluscode]

Otherwise lndo.site only works when calling the service from its own container and only with the port like

lando ssh -s users -c "curl http://wikibus-users.lndo.site:34666"

[tpluscode]

Thank you @pirog for fixing this. Is there any time frame for 3.1?

[pirog]

No, but this issue should be fixed in 3.0.17.

…

On Tue, Nov 3, 2020 at 4:52 AM Tomasz Pluskiewicz ***@***.***> wrote: Thank you @pirog <https://github.com/pirog> for fixing this. Is there any time frame for 3.1? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2579 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFOFUG3USYR7QCHU4ZRUCLSN7HE3ANCNFSM4QNLLRSA> .

[tpluscode]

Oh sorry, I was confused by the GitHub messages. It says "added to 3.1" and the "removed from 4.0.0-alpha.1" but I didn't realise they are the same thing :)

[pirog]

The milestones are only accurate most of them time :)

…

On Tue, Nov 3, 2020 at 5:37 AM Tomasz Pluskiewicz ***@***.***> wrote: Oh sorry, I was confused by the GitHub messages. It says "added to 3.1" and the "removed from 4.0.0-alpha.1" but I didn't realise they are the same thing :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2579 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFOFUHNPSQ3N6BTRJO2HGTSN7MQPANCNFSM4QNLLRSA> .

[tpluscode]

Unfortunately this still does not work correctly. I can have my service run on port 443 to make it accessible over its SSL proxy but custom ports are still not mapped

[tpluscode]

Ah no, sorry, I cannot trick the proxy with 443. Then requests fail with SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

So the only way is to expose port 80 from the service and http proxy will respond

[pirog]

@tpluscode you might want to read the docs on how this is expected supposed to work
https://docs.lando.dev/config/networking.html#port-considerations

[tpluscode]

Thank you. I am not hung up on custom ports.

Would it at least be possible that HTTPS requests work internally?

So with config as below I would be able to call https://thing.my-project.lndo.site?

proxy:
  appserver:
    - thing.my-project.lndo.site

SSL termination would be totally fine, if the proxy connected to the service on HTTP with X-Forwarded-Proto 🙏

[pirog]

@tpluscode an implication in the docs i shared is that if you want https to work internally then that cannot happen through the proxy eg the service itself also needs to be listening on 443. The proxy does do ssl termination and sets the correct header already but this is besides the point because internally the proxy is not part of the equation.

[tpluscode]

For this, please refer to my comment above. I tried listening on 443 and then internal https requests would fail with

SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

[pirog]

If you are using a node service then it is going to be up to you to make sure it can listen on 443 correctly. Here is an example of doing that with express
https://github.com/lando/lando/blob/master/examples/node12/src/app-https.js