we are at "@fortawesome/fontawesome-free": "^6.2.1"

@fozi thanks but … no

would be better to have a solution without https, may someone else gets this figured out.

As an improvement for the above solution with https:

Holding the certs in the config directory makes them accessible from outside so better move them into a new directory beside config, e.g. certs which is not exposed. Don’t forget to update config.js afterwards.

can reproduce it if I use a nonexisting mapUrl, so I think you have a typo in your mapUrl …

see https://www.bleepingcomputer.com/news/security/dev-corrupts-npm-libs-colors-and-faker-breaking-thousands-of-apps/

@sdetweil

the missing node-fetch in package.json of MMM-RemoteControl was fixed 19h before so I think you installed the fixed version and rhbauman not …

@oberfragger yes, in the mm folder

@sdetweil

well, npm install would have installed the devDependencies too…

This sentence clicked in my brain.

I have NODE_ENV=production as default in my images (expect images I use for testing) and with this

• npm install will install nothing
• npm install node-fetch@2 will install nothing

so @codac please go again in the folder of the module and run NODE_ENV=test npm install node-fetch@2

this should hopefully solve the issue

@sdetweil

The sandbox error is mentioned in this github electron issue. It’s a chromium bug and everything should still work normally.

@tippon

you can add the following in css/custom.css:

.module.newsfeed {
  height: 200px;
}

you can play with the height value.

@spitzlbergerj

you can try the ip-address of the pi in config.js as address: instead of "0.0.0.0".