Repository navigation
Tech question unrelated to OASK #1059
Closed
CheminerWill
started this conversation in
General
Replies: 1 comment
|
Update: Finally go a response from the site admin and it was NOT on the client side as the original error said. It was on the sever side and they tracked it down and fixed it. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Just thinking maybe someone here with more expertise that me can help me interpret if the below error is with Chrome on my computer, or something on the server side. I emailed the website but no reply as of yet. I am just trying to set up a 30 day trial account site for a weather station on the Pro Weather website. When I enter the name of my station on their 1st setup page here, https://pro-weather.com/dashboard/start I get the below errors. Can anyone tell from that if the issue is with my computer or theirs? First line of error seems to imply on my side. The later part mentions server? Thanks.
"Application error: a client-side exception has occurred (see the browser console for more information)."
Looking at the console there is this message:
start:1 Unchecked runtime.lastError: The message port closed before a response was received.
start:1 Unchecked runtime.lastError: The message port closed before a response was received.
content.js:1 Uncaught (in promise) Error: No Listener: tabs:outgoing.message.ready
start:1 Failed to load resource: the server responded with a status of 500 ()
5525-8e9b281b62d4734f.js:64 Error: Minified React error #441; visit https://react.dev/errors/441 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
(anonymous) @ 5525-8e9b281b62d4734f.js:64
Found the full text of the console error message:
An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.
All reactions