Cannot access MM2 across the network - localhost ok

sdetweil

@dangerousden this error is reported when there are 2 commas in a row between modules

      },,
      {
          module: "foo",

the next release shows this error in detail,

 Your configuration file contains syntax errors :(
Line 1726 column 9: Unexpected comma in middle of array.

node -c doesn’t report it

dangerousden

@sdetweil Thank you for your prompt response. Apologies that mine is not so prompt. I didn’t get notifications about your reply.

Node -c config.js didn’t seem to do anything. It just returned to CLI

I’m having problems copying the config.js via Pi Connect, so I will get back to you when I return home.

TIA

dangerousden

@sdetweil

As soon as you pointed out the double comma, I spotted it. Amazing how despite 2 hours of double checking, I missed that I had left a comma before a {

thank you, that has resolved the config error, but I still don’t have access via IP, just localhost

dangerousden

Regarding my failure to access MM via IP, but only localhost, does this mean anything to anyone??
I have installed VNC, so am wondering if this is causing problems

![alt text]( Screenshot 2025-12-15 154505.png image url)

sdetweil

@dangerousden

my startup info is

####  System Information  ####
- SYSTEM:   manufacturer: System manufacturer; model: System Product Name; virtual: false; MM: 2.34.0-develop
- OS:       platform: linux; distro: Ubuntu; release: 22.04.5 LTS; arch: x64; kernel: 5.15.0-160-generic
- VERSIONS: electron: 38.1.2; used node: 22.19.0; installed node: 22.21.1; npm: 10.9.4; pm2: 6.0.13
- ENV:      XDG_SESSION_TYPE: x11; MM_CONFIG_FILE: undefined
            WAYLAND_DISPLAY:  undefined; DISPLAY: :0.0; ELECTRON_ENABLE_GPU: undefined
- RAM:      total: 48077.12 MB; free: 22026.83 MB; used: 26050.29 MB
- OTHERS:   uptime: 79391 minutes; timeZone: America/Chicago

running with built in browser (Electron)

you are using node 24, I am using node 22. but that shouldn’t matter…

you should see these messages a few lines back from the info

[2025-12-15 15:13:31.921] [LOG]   [server] Starting server on port 8090 ...  
[2025-12-15 15:13:31.922] [WARN]  [server] You're using a full whitelist configuration to allow for all IPs 
[2025-12-15 15:13:31.935] [LOG]   [app] Server started ..

this will tell you the port and if there is a whitelist

dangerousden

I have made so many changes to the config of both Pi and MM2, I decided it would be easier to start with a fresh instance. So I backed up the config.js and custom.css files and reimaged the SD Card

I used @sdetweil amazing scripts to reinstall MM2 I was back up and running just 20 mins later. I pulled over the GIT repositories that I wanted and reconfigured the config files.

I DID NOT INSTALL VNC SERVER. This is almost definitely causing the network issues. I have reverted to Pi Connect

and everything is working. I synched the wrong MS account for my OneDrive images which I use for backgrounds, but I quickly downloaded them from my server backup and uploaded to my personal MS account. Recreated the Album and am very happy to say it is all running.

I wanted to try to set up a media player to link to my DLNA server (Serviio) but I had to give up on that. I also tried to mnt a folder to the music repository, but I have so much music that I couldn’t find a music player that gives me access to albums, so that I can choose what I want to play. But that is just me trying to push too far I think.

In short, I have my Google family calendar, I have weather and forecast (I’m a Brit and we LOVE weather), I have my holiday countdown and I have my OneDrive images on rotation for a background.

Thank you so much for the assistance. It is much appreciated. Now I need to mount my touchscreen monitor and Pi on the wall in the kitchen for all to admire :)

sdetweil

@dangerousden glad you got it working again!!