Application Error after updating to latest release

[lilcheeks]

"Application error: a client-side exception has occurred while loading 192.168.1.237 (see the browser console for more information)." Is there a setting in my browser i need to change after the latest release?

here is what shows in the console of my browser.

And my log file show this

maybe something went wrong with my Auth_Secret?

Originally posted by @lilcheeks in #160 (reply in thread)

[dohsimpson]

Yeah, this sounds like auth related error. The link in the log suggests that:

Possible causes are either a misconfigured secret or a malformed JWT or encode/decode methods.

I believe you have set the AUTH_SECRET (all caps) env var from the guide, Try opening the url in an incognito window, sometimes it's because old cookie.

[lilcheeks]

Yes i did follow the exacts steps for the AUTH_SECRET, here is a screen shot. Was maybe that process not perfect? Did it look normal to you?

Opening in incognito did not help, same error.

[dohsimpson]

Don't think it's an issue with the release, as I just tried clearing everything and I was able to run it locally. Could you share your AUTH_SECRET and the HabitTrove cookies in your browser? I can try to see if I can reproduce the error

[lilcheeks]

I just wiped the build and re-built it with the same docker-compose file since i was messing around with things. Here is what my log shows now:

and here is my docker-compose file:

Here is what my cookies show in an incognito window:

[no1etal]

I second the issue

[dohsimpson]

Those cookie looks normal. I think it might be related to data/ directory permission.

Do you see any Error loading auth data: Error: EACCES: permission denied, open '/Users/.../Dev/SAAS/HabitTrove/data/auth.json' in your server log?

If so, try this:

chmod -R 777 data/ # the data/ directory should be the directory where you bind to the docker container.

[lilcheeks]

I didn't see that error in my NAS server log or in the container manager log file. I just cleared my container and built a new container with v0.2.20 and it works perfectly. So something between that version and the latest release (I never updated to V0.2.21) is what is causing the problem.

[gamer1pc]

I'm also getting error "Application error: a client-side exception has occurred while loading...." on build v0.2.22. After reverting back to build v0.2.21, everything was working fine. I even created a fresh install on v0.2.22 to verify if it had to do with my current HabitTrove/data folder, but even with the new install the error showed up on different browsers or even different devices as well.

[dohsimpson]

Thanks for reporting this, I reverted latest tag back to v0.2.21

[dohsimpson]

I am still unable to reproduce this issue, but since this only occurs in v0.2.22, and is a client-side error. I highly suspect it's when the browser calls this line to generate a secure hash that throws the exception: https://github.com/dohsimpson/HabitTrove/blob/main/lib/utils.ts#L526

I'll add a check to disable the refresh feature if it cannot get the crypto.subtle object in the next version 0.2.23 as a hotfix, but this would disable the refresh feature until this is fixed from the root cause.

Could you go to the browser dev console and run the following commands and share the output:

console.log('Browser window.crypto:', window.crypto);
console.log('Browser window.crypto.subtle:', window.crypto?.subtle);

Does those statements print undefined, or prints an object.

[gamer1pc]

Prompt "console.log('Browser window.crypto:', window.crypto);" prints "[[Prototype]]: Crypto"
while the other prints undefined. I tried this on v0.2.21, unsure if you want me to try on v0.2.22.

[lilcheeks]

I went back to v0.2.20 and here is the output on my browser tab when i have HabiTrove loaded.

[dohsimpson]

Thank you both @gamer1pc @lilcheeks !

I think I have found the root cause of this issue, in v0.2.22, I added a auto-refresh feature to sync stale data, it make uses of a new Web API, which is exposed as window.crypto.subtle object in the browser.

For example, here is the output in my chrome browser:

There are a couple of reasons for this, but the most likely reason I think might be you are serving HT in http instead of https (see https://stackoverflow.com/a/46468377). Other possibilities are using outdated browser (but unlikely unless you are using 2015 browser)

[dohsimpson]

I've published a fix for this issue in dev docker image. It will be merged in v0.2.23, note that this fix disables the stale refresh feature when window.crypto.subtle is not defined.