Default Calendar stuck on loading

[sdetweil]

@rushmuzik ok, but because you said yes on step 2 to pm2
you don’t need step 8 as it causes a duplicate app definition, which will cause TWO to start

pm2 status 

will show you the apps defined

[rushmuzik]

@sdetweil How do I fix that? Is there a way to undo? This is what I see in pm2 status

[sdetweil]

@rushmuzik you only have 1, so no issue…

pm2 --help

has lots of options

[rushmuzik]

@sdetweil ok. Where would you suggest I go from here? COuld it be the Firefox ESR causing the issue?

[sdetweil]

@rushmuzik I don’t know yet… I posted a potential fix for you to try, based on the error shown

[rushmuzik]

@sdetweil Yes, I saw that. I tried it. It did’t work.

I wonder if something in here might help

[sdetweil]

@rushmuzik no idea…

trying to get ff installed

[sdetweil]

@rushmuzik well i can recreate it. its a bug in firefox. trying to find a workaround, 3 so far dont

[rushmuzik]

@sdetweil OK so I’m not crazy! Good to know! It amazes me how much you know!

[sdetweil]

@rushmuzik just learned about this today, and google has a lot of info. wading thru it is time consuming.

[rushmuzik]

@sdetweil Absolutely. I appreciate all the attention you’ve given to this so far. You have been a big help to the community.

[rushmuzik]

@sdetweil I’ve searched all over google but I still haven’t found a viable solution.

Do you think a previous socket.io version would fix the problem? my current version is 4.8.1

[sdetweil]

@rushmuzik no idea yet

[rushmuzik]

@sdetweil The socket.io GIT lists this as a possible solution to the bad request error however I’m not quite sure where to put it.

Installation: npm i http-proxy

const httpProxy = require(“http-proxy”);

httpProxy
.createProxyServer({
target: “http://localhost:3000”,
ws: true,
})
.listen(80);

[sdetweil]

@rushmuzik me either. socket.io is setup in server.js

[rushmuzik]

@sdetweil I’m suspecting it might be an update to the socket.io in the recent 2.29 release which I’m using. I suspect 2.28 or prior my not have this issue

[sdetweil]

@rushmuzik 2.29 uses socket.io 4.8 where 2.28 uses 4.7.5

you could install 4.7.5

cd~/MagicMirror 
npm remove  socket.io
npm install socket.io@4.7.5

i have company today so it will tomorrow really before i can test

[rushmuzik]

@sdetweil I reverted back to socket.io@4.7.2 that was used on MagicMirror@2.26.0 and that fixed the issue! I tried socket.io@4.7.5 but that didnt work. So I went back to @4.7.2 and that fixed it. It might just be a compatibility issue with Firefox ESR. Mystery Solved! Thanks for all your help!

[sdetweil]

@rushmuzik awesome!!! thanks for the feedback

[rushmuzik]

@sdetweil Thanks for all you do to help the MM community!