Problem with ip whitelist

Cato

I’ve noticed that if there is an error in the config.js, I’ll get the an access denied error.

Have you checked the logs? Try connecting using SSH and run something like pm2 restart mm | pm2 logs mm and watch the log carefully. If it really is an access error, the log will tell you.

ottobot

@leadfarmer router has the address reserved

ottobot

@Cato I’m running it on a zero, so no pm2 sadly. I’m going to try another fresh install on another SD card on another zero when I get home from work today and see if I can reproduce it or if it’s just a weird hiccup.

roramirez

If you have troubles with range, IP, etc… Can set ipWhitelist: [] to allow all IP addresses.

Warning, this enables from everywhere (on your net) have access.

Cato

@roramirez Cool, didn’t know that! :)

ottobot

@roramirez Nice! Worked perfect. Thank you.

Mykle1

@roramirez said in Problem with ip whitelist:

Can set ipWhitelist: [] to allow all IP addresses.

For a novice like myself, that’s a whole lot easier than trying to figure this out:

ipWhitelist: ["::fff:0.0.0.0/1", "::fff:128.0.0.0/2", "::fff:192.0.0.0/3", 
			"::fff:224.0.0.0/4", "127.0.0.1", "::ffff:127.0.0.1", "::1"],

:clap_tone1:

roramirez

@Mykle1 Yes, It’s a problem I can see from a time ago. It’s difficult for some users understood rules /24 /32 /etc . I’m not saying “you go to hell because you not understand it” … generally to myself is hard identified what it is one or other. Every time I see https://en.wikipedia.org/wiki/IPv4_subnetting_reference ;)

I have proposed add a note
https://github.com/MichMich/MagicMirror/pull/759

In a future it should be by default.

Mykle1

@roramirez said in Problem with ip whitelist:

In a future it should be by default.

Good idea! BTW, you all do an excellent job here and I am very grateful. Thank you. :thumbsup_tone1: