After update to Mirror to 2.1.3 - no working Whitlist

Nick

Same here, tried addres 0.0.0.0 and various things in the Whitelist.
A ping gives “destination unreachable”… SSH also doesn’t work.
Can someone please suggest ways to troubleshoot?

Mykle1

@Nick said in After update to Mirror to 2.1.3 - no working Whitlist:

tried addres 0.0.0.0 and various things in the Whitelist.

Have you tried OUTSIDE your Whitelist, as such:

var config = {
	port: 8080,
        address: "0.0.0.0",
	ipWhitelist: [], // Set [] to allow all IP addresses.

Nick

Thx @Mykle1, indeed I have. See the beginning of my (working) config file below.
What is suspicious to me is that not even a Ping works to that IP, even though I’ve checked it by printing it on the screen of the MM and in the router.
Also, before my Whitelist was a long list of IPs, now I’ve tried the [] option but to no avail…

/*************** AUTO GENERATED BY REMOTE CONTROL MODULE ***************/

var config =
{
        address: "0.0.0.0",
        electronOptions: {

        },
        ipWhitelist: [

        ],
        modules: [
                {
                        module: "alert",
                        config: {

                        }
                },
                {
                        module: "updatenotification",
                        position: "top_bar",
                        config: {

                        }
                },
                {
                        module: "MMM-Remote-Control",
                        position: "middle_center",
                        config: {

                        }
                },

Mykle1

@Nick said in After update to Mirror to 2.1.3 - no working Whitlist:

not even a Ping works to that IP

Pinging the mirror’s IP fails? Pinging other devices on your network is successful?

Nick

Yes, including my personal wiki on another Raspberry Pi, all with 2-5ms

Mykle1

@Nick said in After update to Mirror to 2.1.3 - no working Whitlist:

Yes, including my personal wiki on another Raspberry Pi, all with 2-5ms

None of this may help, but you can use it as a checklist.

ifconfig on Pi reports the IP address you are trying to ping (wlan0) assuming wifi
Connecting Pi via ethernet, ifconfig and trying to ping then
Pinging another device from the Pi itself
The MM software updates. Clock, calendar, weather, etc?

Logically, if the only thing you can’t do is ping or connect to the Pi, then something is wrong on the software side, whether a corruption, an edit or a failed installation of the software or dependencies during the upgrade process. The answer in that case, with the most success, is a manual installation, IMHO. You can continue to troubleshoot, which could take a long time, or you can know in less than an hour. You will not lose anything in doing this.

https://forum.magicmirror.builders/topic/5274/how-to-manually-install-mm-on-your-pi-for-absolute-beginners

Jopyth

@Nick As @Mykle1 said: something is wrong if you can neither ping nor ssh. You definitely need to check your general wifi/ethernet setup. This is not something that can be solved through the config file.

FlatPepsi

This post is deleted!

ronanversendaal

Just came across this post while troubleshooting this issue.

I got it working by converting the ip range to CIDR format by using this page as mentioned in older posts. I added these ip’s to the whitelist (without the ::ffff: !) and it worked.
It’s also important to set the address value to “0.0.0.0”