Client-Side exception
I searched for this issue here and didn't find anything:
I have Runtipi running on a cloud server just fine, I have it hosting some of my small bussiness apps and a few personal one. Recently I was given an oldish HP desktop and wanted to slap Runtipi on it for HA, Minecraft, and a few other local apps. This desktop only has 3GB of RAM right now but I have already ordered additional to get it to 8GB. I did install Runtip just a few minutes ago and the install went fine, but when I try to log into it the first time, I get the registration screen, then quickly goes to "a client-side exception has occurred" error. Is this due to my low memory server-side? Like I mentioned, new memory is on the way, I just had some free time to start setting it up today and wanted to get things rolling while waiting. I understand the min installments are 4GB, but thought I might limp through it until the mem arrives.
10 Replies
Hello @pappyeric
Can you please right click on the page and select inspect then click console and share the output
(make sure you don't include any sensitive info)
I was just able to register on my phone (I was being curious) but then the same error. Here is my log:
_next/static/chunks/…f5cae8cf52b6f9.js:6 Uncaught SyntaxError: Unexpected end of input
_next/static/chunks/app/(auth)/login/page-d9c94ca185a8d582.js:1
Failed to load resource: the server responded with a status of 502 (Bad Gateway) _next/static/chunks/app/layout-9089e9219442c581.js:1
Failed to load resource: the server responded with a status of 502 (Bad Gateway) _next/static/chunks/673-0f36989d4b9c328a.js:1
Failed to load resource: the server responded with a status of 502 (Bad Gateway) app-index.js:32 Error: Connection closed. at t (react-server-dom-webpack-client.browser.production.min.js:32:45) window.console.error @ app-index.js:32 Show 1 more frame Show less react-dom.production.min.js:276 Uncaught Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at iU (react-dom.production.min.js:276:1) at o2 (react-dom.production.min.js:262:315) at react-dom.production.min.js:260:29 at o1 (react-dom.production.min.js:260:29) at oV (react-dom.production.min.js:253:92) at oB (react-dom.production.min.js:251:353) at MessagePort.T (scheduler.production.min.js:14:246) _next/image?url=%2Ftipi.png&w=64&q=75:1
Failed to load resource: the server responded with a status of 502 (Bad Gateway)
Failed to load resource: the server responded with a status of 502 (Bad Gateway) _next/static/chunks/app/layout-9089e9219442c581.js:1
Failed to load resource: the server responded with a status of 502 (Bad Gateway) _next/static/chunks/673-0f36989d4b9c328a.js:1
Failed to load resource: the server responded with a status of 502 (Bad Gateway) app-index.js:32 Error: Connection closed. at t (react-server-dom-webpack-client.browser.production.min.js:32:45) window.console.error @ app-index.js:32 Show 1 more frame Show less react-dom.production.min.js:276 Uncaught Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at iU (react-dom.production.min.js:276:1) at o2 (react-dom.production.min.js:262:315) at react-dom.production.min.js:260:29 at o1 (react-dom.production.min.js:260:29) at oV (react-dom.production.min.js:253:92) at oB (react-dom.production.min.js:251:353) at MessagePort.T (scheduler.production.min.js:14:246) _next/image?url=%2Ftipi.png&w=64&q=75:1
Failed to load resource: the server responded with a status of 502 (Bad Gateway)
Minified React error #423 – React
The library for web and native user interfaces
@Nicolas what the heck
docker logs tipi-dashboard pleaseHere's an odd thing: I just restarted the computer and it's booting into regular Ubuntu instead of showing Runtipi starting up containers and the like.
Let me drop back and see if I've done something here. It is on a dual boot computer with two drives. This is probably all on me.
Didn't the most recent versions of Runtipi include an auto-start command added?
Which version are you running?
It's not a command, it's simply how docker works it will restart after a reboot
Yes, thank you. I used the install instructions from the Runtipi website. Sorry. this is my fault. Looking back I made a few poor choices in setting up my dual-boot from the BIOS.
Let me clean up my mess and I'm going to start again. I was probably premature in reaching out for help. It appears to be an issue stemming back before my Runtipi install.
No worries could also be a tipi bug
Got it: when configuring my network configs I copied/pasted my ethernet port wrong in one config file. Used the default eth0 instead of my actual port ID.
Running now. Thanks for all you guys do!