Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ipwhitelist not working #1036

Closed
t4rif4ri opened this issue Sep 29, 2017 · 13 comments
Closed

ipwhitelist not working #1036

t4rif4ri opened this issue Sep 29, 2017 · 13 comments

Comments

@t4rif4ri
Copy link

Platform: RPI 3 with newest MM build, installed and updated yesterday.

Description: Until yesterday my mirror was working with an older build version. The mirror was accessable trough the internet via my configured ddns service.
After the update im getting the error, that the ip was blocked.
I tested with ipwhitelist [] but it isnt working. Additionally i entered 0.0.0.0 to adress wo get the ipwhitelist: [] working, but it didnt fix the problem.

How can i make the mirror accessable from every ip adress?

@MichMich
Copy link
Collaborator

Are you running the develop branch or the master branch?

@t4rif4ri
Copy link
Author

actual Branch is master

@MichMich
Copy link
Collaborator

Could you give the develop branch a try?

git checkout develop
git pull
npm install

@t4rif4ri
Copy link
Author

Ok, this problem is solved, no blocking anymore in shell console, but cant connect anyway. Browser output: (111) Connection refused

@MichMich
Copy link
Collaborator

So, is it solved? Or isn't it? :D If it isn't solved, what message do you see in your node output when trying to connect?

@t4rif4ri
Copy link
Author

Output is not showing any blocked ips, but the connection got refused when i open the link in the browser. Ports are open, like when it was working.

@roramirez
Copy link
Contributor

There was fix into the develop branch about this issue. Please, check it out
45d597a

So, this issue is really fixed.

As @MichMich said

cd MagicMirror
git checkout develop
git pull
rm -frv node_modules
npm install

Make sure you can access from the browser and where is running MagicMirror. Are differents IPs?, I mean MM and Browser

@t4rif4ri
Copy link
Author

mirror is accessable from intern network. Also within the mirror itself. From outside i get the connection refused error shown in my browser. Tried different port settings, but cant connect via dyndns from outside. Other ports like webserver on port 80 is still working and accessable from outside.

@roramirez
Copy link
Contributor

... I presumed this is configuration issue or other not related with MagicMirror itself. Did you set address to '0.0.0.0' in your config.js?

What show you the command netstat -putan ?

@nhubbard
Copy link
Contributor

@t4rif4ri We don't (officially) support DynDNS. I would recommend taking your case to the forums.

@MichMich close?

@t4rif4ri
Copy link
Author

t4rif4ri commented Oct 1, 2017

Thank you all for your help! After i set 0.0.0.0 to adress its working again. :))

@Wird
Copy link

Wird commented Oct 1, 2017

Same her, the site was live after adding "address": "0.0.0.0", to the config

@roramirez
Copy link
Contributor

This change was introduced before to make more secure MagicMirror
Documentation change #1042

cc @MichMich close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants