Read the statement by Michael Teeuw here.
MMM-CalDAV
-
@sdetweil thank you very much for the information - but now i have another problem to get it updated can you help me with this?
-
@caw what environment are you running?
-
@sdetweil im running the docker container on a Synology NAS
-
@caw what docker container?
-
@caw said in MMM-CalDAV:
https: means you have a certificate for that address and have configured MMM-Caldav to run in secure mode
is that true?
typically one uses mmm-caldav to read from the foreign calendar, and emit ics data for the local machine
and make it available thru a url request (which causes the MMM-Caldav module to provide the data live)
http://mmIP:mmPort/caldavor shorthand for this same system is (using the default mm port)
http://localhost:8080/caldavdepending on how MM is configured,
address: and ipWhitelist, by default it rejects ALL requests from OUTSIDE systems
so your loop back at - https://myownsynologyadress.de would be rejected…I use cloudflare to map outside requests to my systems thr a tunnel, so I have https (cert provided by cloudflare) and have reconfigured my MagicMirror to allow any incoming request
address: "0.0.0.0", ipWhitelist:[], -
@sdetweil im running the “container manager” on the nas and the container by bastilimbach installation guide by https://mariushosting.com/how-to-install-magicmirror-on-your-synology-nas/
-
@sdetweil i used ipv64 to receive a certificate - but for now i dont want to get any caldav from outside or do i missunderstand something?
-
@caw said in MMM-CalDAV:
bastilimbach
that image is 4 years old, so not running the latest node or MM…
the install doc https://docs.magicmirror.builders/getting-started/installation.html#alternative-installation-methods
references this docker image
https://gitlab.com/khassel/magicmirror -
@caw because the ics generated by MMM-Caldav is only needed on this same machine I would use
http://localhost:mmport/CALDAV
in the calendar module.
I am guessing your cert is connected to your internet IP address (ISP router)
which is then port forwarded to the MM machine…this is an external (from MM’s perspective) request
MM is configured (be default) to be a closed system on the wall, not allowing any external systems to request the MM page (external means outside the machine MM is running on)
-
@sdetweil i searched for a guide to get the Khassel container running on a Synology NAS but didn’t found anything about it. I tried it by my own but did not work. Do you have a clue how to get it on the Docker on a Synology NAS?
