Client wont keep Modules up-to-date

karsten13

it seems as if there is a problem using the 127.0.0.1 address and port 8080:

yes, port 8080 on your client is already in use.
You can try another port in the client config.js but I don’t know if this works.

I wonder why there is an error catching the newsfeed, as the stated feed is the one from the client, not the server:

then remove this stuff from the client config …

I’m not familiar with the clientonly setup and I think this is not used very often and therefore maybe contains some bugs.

sdetweil

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

I’m not familiar with the clientonly setup

it just launches electron pointing at the server, same as u would do with chromium.

doesn’t use the config.js

codac

I figured out that is was due to several reasons.

The reported error messages from the client side were old ones from the time when I set up the client and before I switched to clientonly mode. So they are supposed to be ignored.
The calendar module was able to receive the events from all calendars except for one calendar that runs on my NAS system where I forgot to add the port number to the calendar url.
the module MMM-Tankerkoenig is not up to date as there is an error message regarding the identifier that was not found. As far as I can see the code has an error and therefore the module wont update correctly.
the module MMM-Formula1 (wrongly called it MMM-SocerLiveScore) module has a ReloadInterval which was just wrongly set up and far to long.

@karsten13
In the Docker on the server side is there anything adequate to the command pm2 logs --lines 300 mm ?

sdetweil

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

In the Docker on the server side is there anything adequate to the command pm2 logs --lines 300 mm ?

wouldnt you just

 docker exec container_id pm2 logs.....

to execute the command inside the container?

to clear the logs

docker exec container_id pm2 flush

karsten13

@sdetweil

there is no pm2 in the container …

The command is docker logs <containername or id>, so if you use my docker-compose setup docker logs mm.

sdetweil

@karsten13 so I have to restart the container after making config changes?

codac

@sdetweil yes, you should do that.

codac

I have still not fixed this.

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

On the client I get the following error:

Unable to connect to server: (Error: Unable to read config from server (http://192.168.0.23:8036/config/ (connect ECONNREFUSED 192.168.0.23:8036)

The servers config is set to:

        address: "0.0.0.0",
	port: 8080,
	basePath: "/", 	
	ipWhitelist: ['0.0.0.0/0', '127.0.0.1', '::ffff:127.0.0.1', '::1', '192.168.0.0/24', '172.17.0.0/24'],

Any ideas why the client wont get the servers config?

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"