I can recomend you 3 things:

Check the next documentation

http://rogerdudler.github.io/git-guide/ (simple) https://backlogtool.com/git-guide/en/stepup/stepup1_1.html (some details about branches) http://rogerdudler.github.io/git-guide/

Second one, use this interactive tutorial
https://try.github.io

The last, you can work better using a zsh+oh-my-zsh. This enable to see where branch you are and status repository into the shell prompt.
https://github.com/robbyrussell/oh-my-zsh

@Steff the translate module which reports an issue is an angular module of pascal precht, but it works even though you didn’t specify a sanitization strategy.

Your problem are the requests which get an 403 forbidden http status

I am still trying to fix the drop outs on the radio stream. I now suspect that it has nothing to do with the wifi connection but somehow with the resources of the PI. I have Alexa & WakeWord running in the background as well as Magic Mirror and Node Red. I switch alexa and wakword off by closing the terminal screens but the server probably still runs so i cant realy rule it out. Anyway to provide radio with more resources or to finalse the cause ?
I also noticed, that after a few seconds of running radio, the VCN connection and even terminal connection disconnects.

Digging one step further:
My magicmirror has the ip address 192.168.178.164.
I am using a cable fritz box, i configured it that this ip address has the hostname “magicmirror”.
I remember that I had to a reboot of the fritzbox 2 days ago, will investigate whether I potentially lost some settings in the fritzbox.
Funny thing:
If I try to access directly http://192.168.178.64:8080/remote.html, I do not get any problem, only if I try to access it with http://magicmirror:8080/remote.html#power-menu
I do not -yet- understand why…
BTW: if i ping the magicmirror from the same pc, the address resolving is working:

PING magicmirror.fritz.box (192.168.178.64): 56 data bytes 64 bytes from 192.168.178.64: icmp_seq=0 ttl=64 time=7.766 ms 64 bytes from 192.168.178.64: icmp_seq=1 ttl=64 time=9.753 ms 64 bytes from 192.168.178.64: icmp_seq=2 ttl=64 time=12.715 ms 64 bytes from 192.168.178.64: icmp_seq=3 ttl=64 time=10.908 ms 64 bytes from 192.168.178.64: icmp_seq=4 ttl=64 time=20.834 ms

Using the full pseudo domain name `http://magicmirror.fritz.box:8080/remote.html#power-menu’ does not help…

@Steff said in Magic Mirror @ Munich:

There is one thing I am unsure about. I have noticed that the controller unit (inverter/ controller) of the monitor has slightly shifted. Maybe I “pressed” the HDMI cable too much and therefore it got dislocated. You can see this in the last picture.

Hi all,

I encountered the same thing with my Viewsonic. It appears, the Controller units arent’t riveted or bolted (or even glued) to the backpanel. They are just taped together with a silverisch tape. My Monitor has a VESA-Mount at the back, so I thought of bolting the wonitor to the wall with a slim VESA-Mount - which worked for 12hours, then the panel fell off - fortunatetly everything is still working.
So I’m thinking - either you have to tape it more thoroughly or use a two-component metal glue for a stable compound.

In my case, I’m making a provisionary case with wood also, which holds the Monitor - and I’m not using the VESA-Mount anymore.