MMM-Caldav not listening on port 8080

MMRIZE

@peterpan894
Could you post this to issue board or discussion of GitHub repository? I should look inside with focus. And maybe needs to talk more closely.

MMRIZE

@peterpan894 said in MMM-Caldav not listening on port 8080:

The only thing which can be the cause is that i run
 npm run server
can someone check on a working system if there is a listener on port 8080? I can only excecute the server as i have a headless system

Ah, you may run the server and client on different devices.
“localhost” points a device-self, so “localhost” in client will be different from that of server.
Use IP address of server instead of “localhost”

peterpan894

I tried 127.0.0.1, 192.168.x.x, same result. The curl was excecuted on the same machine the MM server was running

sdetweil

@MMRIZE if the node_helper depends on info sent down from the modulename.js, then it will not happem as that runs in a browser…

so @peterpan894 one thing to try is to open the MM server in a browser
then see if the port is open

MMRIZE

if the node_helper depends on info sent down from the modulename.js, then it will not happem as that runs in a browser…

The part serving iCal is a pure express logic without any configuration value. It just serve URL from static files on start of node_helper. So ideally, it should be served regardless of the front client.

This image shows that I tried serveronly mode, then try to access Company.ics which is not even fetched in this execution before any client is launched. (The iCal file was fetched in the previous execution)
And showing it hit the access but failed due to no auth. (So that’s why the browser show auth dialog box)

With curl (anyway, -v option is not enough to access this served ical. You should use -u option.) It should have 401 error withou auth info.

~ % curl -v http://localhost:8080/CALDAV/Company.ics
*   Trying 127.0.0.1:8080...
* connect to 127.0.0.1 port 8080 failed: Connection refused
*   Trying [::1]:8080...
* Connected to localhost (::1) port 8080 (#0)
> GET /CALDAV/Company.ics HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/8.1.2
> Accept: */*
>
< HTTP/1.1 401 Unauthorized
< Access-Control-Allow-Origin: *
< Referrer-Policy: no-referrer
< Strict-Transport-Security: max-age=15552000; includeSubDomains
< X-Content-Type-Options: nosniff
< X-DNS-Prefetch-Control: off
< X-Download-Options: noopen
< X-Frame-Options: SAMEORIGIN
< X-Permitted-Cross-Domain-Policies: none
< X-XSS-Protection: 0
< WWW-Authenticate: Basic realm="MMM-CalDAV Service"
< Date: Mon, 13 Nov 2023 23:07:36 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
< Content-Length: 0
<
* Connection #0 to host localhost left intact

So with -u options;

 ~ % curl -u "username1:password1"  http://localhost:8080/CALDAV/Company.ics
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART;TZID=Europe/Berlin:20230919T100000
DTEND;TZID=Europe/Berlin:20230919T110000
DTSTAMP:20230830T065013Z
UID:-@google.com
CREATED:20230830T065013Z
DESCRIPTION:
LAST-MODIFIED:20230830T065013Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:-
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
...

So it works for me.

Ok. Let’s check from the beginning. Is Your MM server served on port 8080? Can you open MM frontend on browser with http://localhost:8080?
Your symptom is very weird because;
If MM is served normally, this module SHOULD work. It uses express delivered from MM itself, not individually installed. So if this module’s express has a problem, MM should have the same problem. (I found unused require in the source :D. Anyway due to that, I can confirm I’m using MM’s express not individual one.)

peterpan894

Can you check the output of ?

sudo lsof -i -P -n | grep 8080

while running npm run server

I checked with using the -u option on curl but that does not help. The “connection refused” is also a symptom if the port is closed which seems to be the case on my end.

MMRIZE

@peterpan894
Send me whole configuration. When describe me which enviroments (for server and for client) are using. (eouia0819@gmail.com)

MMRIZE

@peterpan894

~ % lsof -i -P -n | grep 8080
node       7922 eouia   22u  IPv6 0x58cc15e911673fb5      0t0  TCP [::1]:8080 (LISTEN)

MMRIZE

@peterpan894
If your 8080 port is blocked, you cannot serve MM either.
As far as I read, you run server-only mode. It means you will run MM client (browser or electron whatever) on some device. Is your MM running on the other port than 8080?

% npm run server

> magicmirror@2.25.0 server
> node ./serveronly

[14.11.2023 14:39.52.783] [LOG]   Starting MagicMirror: v2.25.0
[14.11.2023 14:39.52.784] [LOG]   Loading config ...
[14.11.2023 14:39.52.785] [DEBUG] config template file not exists, no envsubst
[14.11.2023 14:39.52.785] [LOG]   Loading module helpers ...
[14.11.2023 14:39.52.785] [LOG]   No helper found for module: clock.
[14.11.2023 14:39.52.804] [LOG]   Initializing new module helper ...
[14.11.2023 14:39.52.804] [LOG]   Module helper loaded: calendar
[14.11.2023 14:39.52.815] [LOG]   Initializing new module helper ...
[14.11.2023 14:39.52.815] [LOG]   Module helper loaded: MMM-CalDAV
[14.11.2023 14:39.52.815] [LOG]   All module helpers loaded.
[14.11.2023 14:39.52.817] [LOG]   Starting server on port 8080 ...
[14.11.2023 14:39.52.823] [LOG]   Server started ...
[14.11.2023 14:39.52.823] [LOG]   Connecting socket for: calendar
[14.11.2023 14:39.52.824] [LOG]   Starting node helper for: calendar
[14.11.2023 14:39.52.824] [LOG]   Connecting socket for: MMM-CalDAV
[14.11.2023 14:39.52.824] [LOG]   Sockets connected & modules started ...
[14.11.2023 14:39.52.824] [LOG]
Ready to go! Please point your browser to: http://localhost:8080

peterpan894

@MMRIZE , found the issue, you last sentence solved it, i was indeed running the server on port 9090 but I set the url of the calendar to 8080.

After changing the port of the calendar url to 9090, all is fine.

Thanks for your support!