2.26.0 - Calendar Error. Could not fetch calendar: http://0.0.0.0:8080/modules/calendars/fussball.ics TypeError: fetch failed about magicmirror

[khassel]

looks like a duplicate of #3329 concerning the undici errors

[sdetweil]

http://0.0.0.0:8080/modules/calendars/fussball.ics

you had to create a new folder, right? cause the folders we provide are

modules/default/calendar

not

modules/calendars 

[screensaverproblem]

Thanks for the info.

I had searched for the error in the forum, but only found #3147. I was probably missing the right search term.

[sdetweil]

we don't replicate the issues to the forum in general

[screensaverproblem]

Thanks for the info.

I had searched for the error in the forum, but only found #3147. I was probably missing the right search term.

http://0.0.0.0:8080/modules/calendars/fussball.ics

you had to create a new folder, right? cause the folders we provide are

modules/default/calendar

not

modules/calendars 

Yes, I create a new folder modules/calendars. But this is not the problem. When I move all *.ics to modules/default/calendar and change the config.js, the error is still present.

[sdetweil]

@screensaverproblem it was just a housekeeping issue to make sure I understand..

I've never seen 0.0.0.0 in a URL before, as its intended for a listening value, not a connection value.

i would only use localhost (meaning this system) or the local system name or ip address of AN interface

note that 0.0.0.0 means ALL interfaces (assume wifi and ethernet both active) , but that doesn't make sense on a connection request.. outbound on both?
and also wifi for both ipv4 and ipv6.. both makes no sense.. and ONE is likely to to be rejected at the server side..
(and I would expect the libraries would clean up any ambiguity this causes by rejecting it eventually)

[screensaverproblem]

it was just a housekeeping issue to make sure I understand..

I've never seen 0.0.0.0 in a URL before, as its intended for a listening value, not a connection value.

i would only use localhost (meaning this system) or the local system name or ip address of AN interface

note that 0.0.0.0 means ALL interfaces (assume wifi and ethernet both active) , but that doesn't make sense on a connection request.. outbound on both? and also wifi for both ipv4 and ipv6.. both makes no sense.. and ONE is likely to to be rejected at the server side.. (and I would expect the libraries would clean up any ambiguity this causes by rejecting it eventually)

I have also tried the local ipv4 address 192.168.x.x instead of 0.0.0.0. The error remained identical.

[sdetweil]

odd still.. I use http://localhost:mm_port for all my temp calendars.. on all my machines with 2.26 and don't see this

[screensaverproblem]

odd still.. I use http://localhost:mm_port for all my temp calendars.. on all my machines with 2.26 and don't see this

I had also used the http://localhost:mm_port syntax before the major upgrade. Sometimes 3 entries of the first calendar were still displayed.
However, I was still in the learning phase (where do I find log files and so on ...) so I don't know whether the error code was identical.

The error is unexpected as I have been using my Magic Mirroro Proket for years without any major problems.

I searched the forum again for the UUID and found this issue:
Calendar loading randomly fails if files stored locally #3365
-> But the solution approach sounds complicated and I don't fully understand it either. I'm just not a software developer ;-)

[sdetweil]

But the solution approach sounds complicated and I don't fully understand it either

welcome to the fun.. we don't either.. lol

none of this is our locally written code.. so, we're not sure what the issues are.. lots of changed things all at once. (no choice) should have been MORE stable, but we got WAY less..

another test approach would be to start MM in server mode (not using electron)

npm run server

and then open a browser over it. http://localhost:mm_port

and see how it behaves.. node 18 and 20 have the builtin fetch like in electron, same libs..