Default calendar module with iCloud calendar fetch error

[autistiii]

Hello,
i have set up the default calendar module, including both Google and iCloud calendars. Google calendars work fine, but the iCloud calendars (synced with vdirsyncer) are not displayed and i’m getting an error message that there is a problem inside the calendar module and that i should check the logs. Here they are:

0|mm | }
0|mm | [2024-05-25 15:54:14.002] [ERROR] Calendar Error. Could not fetch calendar: http://ip-address/modules/calendars/c4684ce4-3887-496a-ae4a-23eab8dacbb2.ics TypeError: fetch failed
0|mm | at Object.fetch (node:internal/deps/undici/undici:12293:11)
0|mm | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
0|mm | cause: Error: connect ECONNREFUSED ip-address:80
0|mm | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16) {
0|mm | errno: -111,
0|mm | code: ‘ECONNREFUSED’,
0|mm | syscall: ‘connect’,
0|mm | address: ‘ip-address’,
0|mm | port: 80
0|mm | }
0|mm | }

Not sure whats wrong here.
I saw in another post (https://github.com/MagicMirrorOrg/MagicMirror/issues/3147) that I should change from “localhost” to my ip-adress or “0.0.0.0”, but that did not work for me.
It would be awesome if someone could help me out on this one :)

[sdetweil]

@autistiii yes

http://ip-address/modules/calendars/c4684ce4-3887-496a-ae4a-23eab8dacbb2.ics

MagicMirror is running on port 8080 or whatever is configured in the config.js
port property

without a port number specified, it means port 80

http://ip_address:8080/…

[autistiii]

@sdetweil
thank you for the fast response.
however, adding the port “:8080” to the ip-address in the config file doesnt solve the issue :/
the error message is still the same

[sdetweil]

@autistiii said in Default calendar module with iCloud calendar fetch error:

cause: Error: connect ECONNREFUSED ip-address:80

that error?

[autistiii]

@sdetweil
yes

cause: Error: connect ECONNREFUSED ip-adress:8080

[sdetweil]

@autistiii what is ip_address?

localhost?

if NOT then you have to open up access permissions
by changing the config.js

address and ipWhitelist properties