MMPM 2.01 Now Available on PyPI!

requiemmg

Thanks for your work!
Do I start the upgrade process from mmpm’s CLI if I have 1.x installed or do i need to uninstall and reinstall?

requiemmg

Uninstalled MMPM 1 and installed MMPM 2. Problem:
mmpm install --gui # to install the GUI (needs sudo permissions)

When I execute this without sudo, I get a bad Gateway error by nginx when I try to call the URI.

Wenn I do “sudo mmpm install --gui” it tells me “mmpm not found”, as well as when I try “sudo su” and then execute the command. How do I fix this?

sonicgoose

Installation fails with

sudo mmpm install --gui

with error mmpm is not installed.

swvalenti

Clear browser cache

sonicgoose

@swvalenti What browser cache? This is in Terminal.

swvalenti

@sonicgoose I was referrring to @requiemmg as I got a bad Gateway error by nginx when I called the url. I cleared the cache and it resolved. Also @requiemmg there is probably a clash with MMPM 1 so do the following then install again.

pip3 uninstall mmpm
rm ~/.local/bin/mmpm
pip3 install —reinstall —no-cache-dir —local mmpm

bee-mar

The installation process can be found here: https://github.com/Bee-Mar/mmpm/wiki/MMPM-Installation

Then, you should configure the environment variables: https://github.com/Bee-Mar/mmpm/wiki/MMPM-Environment-Variables

And for configuring the hide/show feature: https://github.com/Bee-Mar/mmpm/wiki/Status,-Hide,-Show-MagicMirror-Modules

Review other sections of the Wiki as well.

You don’t need to clone the repo at all to install MMPM 2.01. You can run the command below, and your current installation will be upgraded.

$ pip3 install --upgrade --no-cache-dir mmpm

For a full installation of MMPM 2.01:

$ pip3 install --upgrade --no-cache-dir mmpm
$ mmpm install --gui
$ mmpm install --as-module
$ mmpm install --autocomplete

Do not used sudo in front of any of the above commands. MMPM will use sudo internally when installing the GUI.

A Former User

@bee-mar

Do you plan code exception for MM modules or npm module ?

exemple in my case (and maybe for others):

I use google grpc library and with RPI lastest version don’t work with RPI (developer don’t want to fix it)
So i fix it by using only the working package and can’t be upgraded automaticaly
You can have some electron braking library (module not found) because it’s not rebuilded

That’s why option or exception will be needed

requiemmg

Now I have a strange problem:

MMPM 2.01 worked for me for a few days.
Yesterday, on one of my 2 mirrors (they are both exactly the same hardware, config and setup, in fact I have set up one and cloned its drive to the others SD card) i got a Nginx 502 Bad gateway error when I tried to open up the MMPM GUI.
I did a full uninstall of MMPM and reinstalled. Worked as intended.
This morning the error again (the Pi does a scheduled reboot in the night).
Reinstalled again.
Browser cache is cleared.

Mirror 1 - works perfectly
Mirror 2 - works after reinstallation until i make a reboot.

Installed with --force-reinstall, --no-cache-dir and --upgrade

Anyone having an idea?

requiemmg

Addition: mmpm log shows this.
No errors in pm2 log.

Excerpt from my config:

var config = {
	address: "0.0.0.0", // Address to listen on, can be:
	                      // - "localhost", "127.0.0.1", "::1" to listen on loopback interface
	                      // - another specific IPv4/6 to listen on a specific interface
	                      // - "0.0.0.0", "::" to listen on any interface
	                      // Default, when address config is left out or empty, is "localhost"
	port: 8080,
	ipWhitelist: [], // Set [] to allow all IP addresses

This is mmpm log:

2020/07/29 10:49:53 [error] 735#735: *35 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.100, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:7891/", host: "192.168.0.123:7890"
2020/07/29 10:49:53 [error] 735#735: *35 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.100, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "http://[::1]:7891/favicon.ico", host: "192.168.0.123:7890"