can't access property "status", e.response is undefined

[greenship24]

Problem

• can't access property "status", e.response is undefined when trying to mark a book as read, update reading progress, etc.

Sequence

• Register user with email and longish password (30 char)
• login
• search a book and click onto it
• Try to toggle the dropdown for "Currently Reading" and then mark progress (either pages or percentage, same issue)

Details

• Firefox or Vivaldi (vivaldi error as toast popup is "Cannot read properties of undefined (reading 'status')
• Does the same thing on multiple books ("Emma" by Jane Austen, "The Battle for Spain", etc.)
• No relevant logs on either web or API containers (web just says normal 200 and 304 statuses
• Being served via simple ingress-nginx proxy on k8s and BL_API_ENDPOINT appropriately set
• sqlite DB per normal docker-compose (small, no need for postgres)
• noticed I got "NaN" error for the current progress when trying this sometimes too (ie. the current page read number before I've even added my updated value)
• No issue on DB migrations, etc.

I've wiped the DB once or twice (this is a testing instance) and same issue. Nothing that I can see on my end (disabled adblocker, any JS addons, etc.)

More than willing to test and wipe the DB again, etc. If you have a flag I can set for debug logs on whichever container you suspect I can add that as well. It seems like an issue with the python side and maybe a route/model isn't properly set but that's a hunch.

[Mozzo1000]

Hi @greenship24
Thank you for opening up this issue.
Sadly there aren't any debug flag to set or any good way to debug these errors. It is on my to-do list to implement both better errors on the frontend and also some way to debug / provide logs in cases like this.

After the error occurs, are you able to open the database and see if you have a row inside the profiles table corresponding to your user account?

[greenship24]

I opened the DB and can see my user in the users table but the profiles table is completely empty. As a test I made another user account and still no corresponding entry in the profiles tab for that user either.

[Mozzo1000]

Alright, that is great! If you login and go to the profiles page (its the icon of a person in the navigation menu) you should be promoted to create a profile. Does that happen?

If not, there is an item in the local storage that needs to be cleared in your browser.

[greenship24]

Nope- same error. I have tried clearing cache and using a private browser window (in Vivaldi, not normal firefox) and same issue.

Edit- can also not set a picture for my user either. Unsure if that helps but seems like it's all related. Is there a reason to have separate user/profile tables in the DB? I will take a gander at the code at some point (I dabble in python) but maybe it just needs some link.

[coilkid]

I receive the same error message can't access property "status", e.response is undefined upon trying to register a user or login.

I'm using a fresh pull from docker. Instead of https://localhost:5000, I'm using booklogr-api:5000. I thought that might be the issue, but I can ping booklogr-api:5000 from inside the booklogr-web container and it correctly resolves to the api container's docker IP address and returns a response immediately.

[Mozzo1000]

I am very sorry for the issues. I will hopefully get them all resolved or at least able to debug better them further in the future.

The profiles and user tables are separated because the auth logic was a separate container before. Now that auth has been merged into the API container the profile and user table can be in one table instead of two.

[greenship24]

No worries @Mozzo1000 ! We are all busy with life so don't stress over it.

Again, if I can find time I'd like to take a peek and see if I can help in any way. If I do find that time then I'll let you know on this ticket or with a PR, etc.

Thanks again for putting it together in the first place.

[marcothms]

@coilkid As #23 (comment) highlights, that there is no inter-container communication. The user itself must have access to both containers. (I definitely made the same mistake!)
After setting a DNS record and requesting a certificate for both services, it worked for me
Nevermind, there are still some CORS errors, like OP describes :/

[lolsuffocate]

I was able to work around the CORS issue by using the same URL for the api and web interface but proxying / to port 5150 and /v1 to port 5000 in nginx. This fixed profile not loading, not being able to add books to lists, etc.

E.g.

compose.yaml

environment:
    - BL_API_ENDPOINT=http://books.pi.lan/

booklogr.conf

server {
    listen 80;
    listen [::]:80;
    server_name books.pi.lan;
    
    location / {
        proxy_pass http://localhost:5150;
    }
    location /v1 {
        proxy_pass http://localhost:5000;
    }
}

[romanzipp]

I've also experienced this error messages from original issue post. Turned out it had to do with the AUTH_REQUIRE_VERIFICATION env var. I registered a user (without SMTP config present) with AUTH_REQUIRE_VERIFICATION=true, tried logging in and got the error as response.

Deleting the sqlite database, setting AUTH_REQUIRE_VERIFICATION=false and re-registering solved the issue. I don't need mail verification for my instance.

[Mozzo1000]

Hi @romanzipp
Thank you for commenting on this issue and including how you fixed the issue for you. I believe I have corrected the error with commit 50fbdaa.
Now if AUTH_REQUIRE_VERIFICATION is set to true it will also check if the smtp settings are properly configued as described in Configure email verification. If smtp settings are not configured properly it will set AUTH_REQUIRE_VERIFICATION to false and ignore verification altogether without raising an error on the frontend.

Before this change the code was trying to send an email but without smtp settings, thereby failing.