Client wont keep Modules up-to-date

[sdetweil]

@karsten13 said in Client wont keep Modules up-to-date:

ports:
  - "8080:8080"
  - "8036:8036"

why wouldn’t

     ports:
           "8036:8080"

be enough?

[karsten13]

@sdetweil think you are right …

[sdetweil]

@karsten13 actually I think you were closer…

I know a module that uses the port number in a url it presents…
(MMM-Config in the QR code)

8080 won’t work, but if the mapping was added

so

     ports:
           "8036:8080"
           "8080:8080"

would be needed

and if u need to do that, then 8080 on the docker host needs to be used, so then no need for 8036

     ports:
           "8080:8080"

but can’t run two container instances

[sdetweil]

@sdetweil also, my MM uses 8090 not to collide with another app.

[karsten13]

@codac

Servers IP: 192.168.0.23 (local Port 8036, container-port: 8080)

if I read this correctly your setup is

ports:
  - "8036:8080"

So mm should be reachable under 192.168.0.23:8036.

If not the client ip is may not white listed, I would try ipWhitelist: [], in the server config for testing.

Another question: Is 192.168.0.23:8036 not reachable in general (e.g. in a browser) or only not reachable running the clientonly command?

[codac]

The client is a raspberry pi.
192.168.0.23:8036 is reachable without problems.

First try seems to work
I’ve changed to:

ipWhitelist: [],

and

ports: "8036:8080"

I will check that and come back if there is still an issue.

Thank you guys!