Got it solved, but not sure what exactly fixed it.

I changed my config lines:

    address: "0.0.0.0",
    ipWhitelist: [],

And then rebooted. Didn’t fix it.
Rebooted again later, and then it was fixed.
Very odd - but fixed is fixed!

Made that change, and still can’t view the web page remotely.
Odd, since I was able to before the MM update.

I can VNC into the mirror, so I know the IP is right, and it’s got a good network connection.

Anyone have tips on seeing logs on the mirror to start troubleshooting?

I used to be able to view my Mirror’s web page from my phone & PC (nice when in the house, but not at the mirror). Yesterday I updated the MM core to the latest, and now the page won’t show remotely. Did something change in the MM core around this?

My config.js includes:

port: 8080,
ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1", "192.168.1.14"
          , "192.168.1.199", "192.168.1.0"],

For those seeking North American globe views, I have great news - GEOS-16 (aka GEOS-East) is now publishing live color (yes, COLOR) images!

See web site here:
https://www.star.nesdis.noaa.gov/GOES/GOES16_FullDisk.php

There are a few links for the latest image, depending on the resolution you want. (Watch out -many of the web site’s URLs are date and time specific) I’m using: https://cdn.star.nesdis.noaa.gov/GOES16/ABI/FD/GEOCOLOR/678x678.jpg

Until a proper GIT update is done on this module, you can edit your setup to get this new image. In the folder:
/home/pi/MagicMirror/modules/MMM-Globe
Edit the file: MMM-Globe.js

Find the lines with ‘centralAmericaDiscNat’: , and put the new URL in there. In my case, I used:

		'centralAmericaDiscNat': 'https://cdn.star.nesdis.noaa.gov/GOES16/ABI/FD/GEOCOLOR/678x678.jpg'

Do note that the code has 2 sections for different resolutions- you may need to update both.

Enjoy!

@jinjirosan - The temperature bars auto scale based upon the width of the rest of the module. I suspect some other changes you’ve made have caused the module to get wider, so you’re looking at a side effect and not a cause.

It might also be a screen resolution – the crypto currency module underneath in your screenshot is wide as well. I’m using a crummy small monitor, and have very narrow margins.

I love that someone else is picking this up and running with this module. Looks good!

@ironman_DK Not sure what my problem was, but rebooting once or twice seem to solve it. I’m wondering if there was some installed module that didn’t get initialized or something.

When in doubt reboot.

@ironman_DK Ever find a solution? I’m doing a fresh install, and only seeing “Loading commute…”

Just updated to latest MM, and got the following error:

npm WARN grunt-yamllint@0.2.0 requires a peer of grunt@~0.4.0 but none was installed.

Related error shown earlier in the install process:

MagicMirror installation successful!
magicmirror@2.1.1 /home/pi/MagicMirror
\u251c\u2500\u252c chai@3.5.0
\u2502 \u251c\u2500\u2500 assertion-error@1.0.2
\u2502 \u251c\u2500\u252c deep-eql@0.1.3
\u2502 \u2502 \u2514\u2500\u2500 type-detect@0.1.1
\u2502 \u2514\u2500\u2500 type-detect@1.0.0
\u251c\u2500\u252c chai-as-promised@6.0.0
\u2502 \u2514\u2500\u2500 check-error@1.0.2
\u251c\u2500\u2500 UNMET PEER DEPENDENCY grunt@1.0.1
\u251c\u2500\u252c http-auth@3.1.3
\u2502 \u251c\u2500\u252c apache-crypt@1.2.1
\u2502 \u2502 \u2514\u2500\u2500 unix-crypt-td-js@1.0.0

Should I be worried?

@dbaler

Yes! Build notes would be nice- as I understand, they need a special adapter or wiring.

If you have something cool going, a video might be cool too!