Blank black screen | Noob

KirAsh4

you can only run two separate instances of MM is they are on different ports, and for that to work, you will need two separate installations (in separate folders) because of the config file. They can not share it.
Check on 'pm2' documentations on how to delete any configured startup process

Arod192

Alright so I fixed the problem of the two instances opening but when I run ‘DISPLAY=:0 npm start’ It’s still blank.

Any ideas on how to fix this? Like I said before it works when I use "node serveronly’

KirAsh4

Go back to the beginning. Move your current config.js to something else, like config.js.backup. Then grab the original config.js and try running that, see if it comes up.

You only need to set the DISPLAY=:0 if you are connecting remotely.

Arod192

Did it using the sample config and renaming it to config.js. I still get a black screen, but if I do “node serveronly” with the same files it works in my browser.

I’m getting no errors besides the “No helper found for module” (all of them)

KirAsh4

With the default config.js you get a blank screen when you try to run 'npm start' ? If so, what’s the hardware? Have you updated the OS? All variables.

Arod192

I used the automatic installer located here, https://github.com/MichMich/MagicMirror, and followed every step.
I’m using a Raspberry Pi 3 Model B.
I’m running Raspian Jesse 4.4, Node v4.4.3.
The MagicMirror is up-to-date

amanzimdwini

@Arod192
THIS is the setup that worked GREAT for me:
https://forum.magicmirror.builders/topic/236/complete-setup-tutorial

(Surprised KirAsh4 did not mention it. Follow it step by step; first time around will take you 30 min, but after that you will fly through it). Work. It really does.

KirAsh4

@Arod192, that’s a rather old version of node. When you run the automatic install from MM², it installs a more recent version automatically. You shouldn’t have to do that manually.

KirAsh4

@amanzimdwini, I didn’t mention it … yet … because I like to figure out where the problem is, before I tell someone to start from scratch. :)

Arod192

@KirAsh4 Update Node.js and I’m still having the problem