Read the statement by Michael Teeuw here.
Solved MMM-Caldav not listening on port 8080
-
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.
-
@peterpan894
Send me whole configuration. When describe me which enviroments (for server and for client) are using. (eouia0819@gmail.com) -
~ % lsof -i -P -n | grep 8080 node 7922 eouia 22u IPv6 0x58cc15e911673fb5 0t0 TCP [::1]:8080 (LISTEN)
-
@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
-
@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!