@sdetweil finally loaded after an hour

@sdetweil yes top left. I did notice my Electron version said undefined in pm2 logs. Would that matter?

@sdetweil according to pm2 logs it did broadcast 12 events

@sdetweil Yes, I ran the clipping fix. I’m using the surf browser.

@sdetweil yep! that fixed it. update installed. Still have issues with the calendar though. holidays doesn’t load.

@sdetweil Here it is

Upgrade started - Fri Jan 3 20:33:33 EST 2025
system is Linux kiosk 6.1.21+ #1642 Mon Apr 3 17:19:14 BST 2023 armv6l GNU/Linux
user requested to apply changes
doing test run = false
the os is PRETTY_NAME=“Raspbian GNU/Linux 11 (bullseye)” NAME=“Raspbian GNU/Linux” VERSION_ID=“11” VERSION=“11 (bullseye)” VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL=“http://www.raspbian.org/” SUPPORT_URL=“http://www.raspbian.org/RaspbianForums” BUG_REPORT_URL=“http://www.raspbian.org/RaspbianBugs”
the latest MagicMirror version, 2.23 (April 4 2023) or above, will not run on Raspian Bullseye, due to browser limitations
Upgrade ended - Fri Jan 3 20:33:33 EST 2025

@sdetweil The interesting thing is that I was able to do a fresh install using the rasberry.sh script. I renamed my original MagicMirror folder then did a fresh install using your install script. 2.30 is running. Everything works except the calendar. lol. Where can I change the fetch timeout to 60 seconds?

@sdetweil Still the same error in update log. unfortunately

@sdetweil No worries. Thanks for all that you do.

@sdetweil Im having some issues with the Upgrade script. This is what i’m getting in the log. Does this mean I have to do a manual upgrade? I’m using surf browser. How would I manually upgrade?

@sdetweil I was able to install node 20.18.1. Just trying to figure out the code to increase the fetch timeout.

@sdetweil I have two followup questions.

1. How do I install that surf based system.
2. Do you know how I can nun Node@20.17.0 or greater on a pie zero?

@sdetweil For some mysterios reason it worked for me for 10 good minutes then crashed. I still don’t know what caused it to work that period. How is the overal experience with Surf Browser? Would you recommend I use that instead?

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

@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 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 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 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 Absolutely. I appreciate all the attention you’ve given to this so far. You have been a big help to the community.

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