I’m using a docker compose file, and I have everything running just fine, containers talking to each other as needed, NPM reverse proxying everything via a duckdns subdomain… everything’s cool.

Problem is, I can still go to, for example, http://192.168.1.30:8080/ and get the services without http.

I’ve tried commenting out the ports in the compose file, which should make them only available on the internal network, I thought. But when I do that, the containers can no longer connect to each other.

Any advice for me?

Edit:

Thanks for the quick & helpful suggestions!

While investigating bridge networks, I noticed a mention that containers could only find each other on the default container bridge by container name, which I did not know. I had tried 127.0.0.1, localhost, the external IP, hostnames, etc but not container names.

In the end, the solution was just to use container names when telling each container how to find the others. No need for creating bridge networks or any other shenanigans.

Thank you!

  • schizo@forum.uncomfortable.businessEnglish
    5·
    9 hours ago

    Change your port definitions so that they’re only binding to localhost, like so:

    • “127.0.0.1:8001:8001”

    That’ll stop access from anywhere but the local host. You’ll have to redo your reverse proxy configuration to use 127.0.0.1 instead of whatever you’re using now, though.

  • Scholars_Mate@lemmy.worldEnglish
    3·
    9 hours ago

    Are you using the default bridge? I have a similar setup (with Traefik instead of NPM), and for each compose file am using separate networks for the internet, proxy, and backend services.

    services:
  some_service:
    ...
    networks:
      - frontend_network
      - proxy_network
      - backend_network
  backend_service:
    ...
    networks:
      - backend_network
networks:
  frontend_network:
    driver: "bridge"
  proxy_network:
    driver: "bridge"
    internal: true
  backend_network:
    driver: "bridge"
    internal: true
  • marsara9@lemmy.worldEnglish
    2·
    9 hours ago

    I’ve tried commenting out the ports in the compose file, which should make them only available on the internal network, I thought. But when I do that, the containers can no longer connect to each other.

    Did you create an explicit network for them to talk on? Otherwise the default docker network doesn’t support internal DNS queries.

    https://docs.docker.com/engine/network/#container-networks

    Specifically you need a network using the bridge driver: https://docs.docker.com/engine/network/drivers/bridge/

  • lemonuri@lemmy.mlEnglish
    1·
    9 hours ago

    You need to change the nginx config (for the website you will be hosting your services at. /etc/nginx/sites-available/yourdomain.com

    You can reroute all http requests to https in that config.

    Watch a video on how nginx works and how to set it up, and then look for example nginx configs for your services. It’s a pretty standard setting nowadays so the syntax should be easy to find.

    I think nginx can be setup to work locally only, but do you even need it for that? It’s primary use is to proxy http requests to the different websites running on your server, enable https via letsencryt and so on, I think.

  • just_another_person@lemmy.worldEnglish
    21·
    9 hours ago

    Don’t forward them, close firewall ports, change configs to not listen on those ports, setup redirects to forward all requests on those ports to whichever you want…lots of options here

    • robolemmy@lemmy.worldOPEnglish
      2·
      9 hours ago

      My firewall is closed, nothing is forwarded. This is all on my LAN only. I just don’t want the non-https ports available at all, even on the LAN.

      • vividspecter@lemm.eeEnglish
        1·
        5 hours ago

        There’s likely a firewall on the system that hosts the docker services, and docker’s default bridge rules bypass it when publishing a port. And since the docker rules are prioritised, it can be quite difficult to override them in a reliable way. I personally wish that the default rules would just open a rule to the host, but there might be some complexity that I’m missing that makes that challenging.

        I personally use host networking to avoid the whole mess, but be aware you’ll have to change the internal ports for a bunch of services most likely, and that’s not always well-documented. And using the container name as the host name won’t work when referencing other containers, you’ll have to use e.g. localhost:<port number> even inside the network.

        You can do the bind to localhost thing that others have mentioned, as long as the reverse proxy itself is inside the docker network (likely there are workarounds if not).