@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
Read the statement by Michael Teeuw here.
Latest posts made by rushmuzik
-
RE: Default Calendar stuck on loading
-
RE: Default Calendar stuck on loading
@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); -
RE: Default Calendar stuck on loading
@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
-
RE: Default Calendar stuck on loading
@sdetweil Absolutely. I appreciate all the attention you’ve given to this so far. You have been a big help to the community.
-
RE: Default Calendar stuck on loading
@sdetweil OK so I’m not crazy! Good to know! It amazes me how much you know!
-
RE: Default Calendar stuck on loading
@sdetweil Yes, I saw that. I tried it. It did’t work.
I wonder if something in here might help
-
RE: Default Calendar stuck on loading
@sdetweil ok. Where would you suggest I go from here? COuld it be the Firefox ESR causing the issue?
-
RE: Default Calendar stuck on loading
@sdetweil How do I fix that? Is there a way to undo? This is what I see in pm2 status
-
RE: Default Calendar stuck on loading
@sdetweil These are the steps I followed to set it up
-
RE: Default Calendar stuck on loading
@sdetweil This is what I’m using. with Firefox ESR as the browser because Chromium and regular firefox are no longer supported on a Pi zero. Also, I’m using an API to connect to my Tempest weather station and that works fine. In addition all the other default modules work as they should except for calendar.