Problem with ip whitelist

ottobot

I picked up a new SD card today, and did a clean install from scratch on my wife’s mirror. Now all of the sudden I am having problems connecting via port 8080 from any other device. I downloaded all of the modules that were on the old SD and literally copy/pasted the config.js so I’m not sure what got broken in the transition. Here is the whitelist rule:

var config = {
	port: 8080,
	ipWhitelist: ["127.0.0.1", "::ffff:192.168.1.1/120", "::ffff:127.0.0.1", "::1"],

	language: 'en',
	timeFormat: 24,
	units: 'imperial',

Mykle1

@ottobot

Here’s mine. It works, if you care to give it a try

var config = {
	port: 8080,
	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"],

ottobot

Still no dice. It’s weird. Literally nothing changed config wise. Just the SD card. The mirror works, and I can get to it via ssh. For some reason though I can’t get to it in a browser from any other computer on my network.

A Former User

It may have been setup as a new device on your network with a different IP address due to the clean install.

For example, if you were previously previewing the mirror at 192.168.1.2:8080, it could have been reassigned to something like 192.168.1.7:8080.

Check your router LAN settings to see what IP address has been assigned to it.

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: