Client wont keep Modules up-to-date

[sdetweil]

@codac first, remove the ipWhitelist , set to []

then try
.and the IP address used is the docker host IP address, right.

never use the containers direct address for any code not running ON the docker host machine

where is client running?

if mm rejected the connection due to whitelist you should have seen it in the mm messages

i see a message like this

Access denied to IP address: 192.168.2.106

my config

	address: "192.168.2.106", 	// Address to listen on, can be:
							// - "localhost", "127.0.0.1", "::1" to listen on loopback interface
							// - another specific IPv4/6 to listen on a specific interface
							// - "0.0.0.0", "::" to listen on any interface
							// Default, when address config is left out or empty, is "localhost"
	port: 8090,
	basePath: "/", 	// The URL path where MagicMirror is hosted. If you are using a Reverse proxy
					// you must set the sub path here. basePath must end with a /
	ipWhitelist: ["127.0.0.1"], 

[karsten13]

@codac

may you must open the additional port in the docker setup and add the line with 8036 (untested) in your docker-compose.yml:

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

[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!