Hello together,
after change the Address from “localhost” to “0.0.0.0” and restart the MM is runing without problems.
Now I can update and upgrade the system every day and not every month. It was not funny to do the same steps after restart and running the MM again. Thank you very much.
Read the statement by Michael Teeuw here.
Best posts made by aldisachen
-
RE: After restart and updating raspberry MM will not starting
Latest posts made by aldisachen
-
RE: Add another time to display
Hello together and thanks for the code / html.
But i don´t understadn the things. I´m not a developer. This looks very hard for me.
But I will try to do this … can take lot of time for me. ;-) -
Add another time to display
Hello together,
at my config at the MM I see my local timeon the left side
It´s possible to add and display a seccond time, for example new york, singapore or other city´s ?
If yes what is nessessary to do for chnage the config and to display this ? Thanks in advance. -
RE: After restart and updating raspberry MM will not starting
Hello together,
after change the Address from “localhost” to “0.0.0.0” and restart the MM is runing without problems.
Now I can update and upgrade the system every day and not every month. It was not funny to do the same steps after restart and running the MM again. Thank you very much. -
RE: After restart and updating raspberry MM will not starting
Hello, I don´t understand what is nessssary to change in the config file. Can you please write down the right settings at the config file ?
I have no experience with that. Thanks. -
RE: After restart and updating raspberry MM will not starting
Hello all togehter, the config.js starts with:
/* Magic Mirror Config Sample
*- By Michael Teeuw http://michaelteeuw.nl
- MIT Licensed.
- For more information how you can configurate this file
- See https://github.com/MichMich/MagicMirror#configuration
*/
var config = {
address: “localhost”, // 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, is “localhost”
port: 8080,
ipWhitelist: [], // Set [] to allow all IP addresses
// or add a specific IPv4 of 192.168.1.5 :
// [“127.0.0.1”, “::ffff:127.0.0.1”, “::1”, “::ffff:192.168.1.5”],
// or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
// [“127.0.0.1”, “::ffff:127.0.0.1”, “::1”, “::ffff:192.168.3.0/28”],and it will follow with the language, time format and so on and so on witch all the settings to display for the MM. Thnaks.
-
RE: After restart and updating raspberry MM will not starting
Hello and sorry for this misstake,
Please delete the other duplicate post. Sorry again. Thanks. -
After restart and updating raspberry MM will not starting
Hello, I have a Raspi 4 with the following system:
- Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye
- Docker version 20.10.21 and Poratiner version 2.12.2 are installed on it.
- Magic_Mirror is also running as container on portainer
Now to my problem…
Every time if I restart the Raspi or install updates and restart the Raspi the MM will not longer working.
Currently solution to workng again:
- delete the container in the Portainer
- delete the volume in the container
- delete directory directly on the Raspi using rm -r “Magic_Mirror” (including the subdirectory.
After these steps I use the next spets to running MM again:
docker run -d
–publish 8181:8080
–restart always
–volume ~/magic_mirror/config:/opt/magic_mirror/config
–volume ~/magic_mirror/modules:/opt/magic_mirror/modules
–volume /etc/localtime:/etc/localtime:ro
–name Magic_Mirror
bastilimbach/docker-magicmirrorIn order for MM to run, I have to change the network connection of MM from “Bridge” to “Host” in Portainer. Then MM runs again. Why is that and where can I see why MM is causing difficulties? It’s annoying having to do the above steps every time you install updates and have to restart the device.
Other containers are running without problems after restart. It´s only the MM with the problems.
Thanks in advance.