starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-25 16:06:04 +03:00

[GH-ISSUE #921] Chrome Pluggin "Fail to Fetch" when attempting login, 0.21.0 #607

New issue

Closed

opened 2026-03-02 11:51:17 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 11:51:17 +03:00

Owner

Originally created by @brainsoft1 on GitHub (Jan 21, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/921

Describe the Bug

Attempt to sign-in to the Chrome pluggin but get a "Failed to Fetch" error after entering email and password.

Steps to Reproduce

Click Chrome Extension
Enter server IP:Port (also attempted with only IP, no port specified)
either way the extension progresses to next screen. I can only assume the server was reached, but the behaviour is the same even if I put a bad IP in.
enter email and password > Failed To Fetch

Expected Behaviour

-Visual feedback to user that you have reached the server. Bad server address should be identified before login attempt.
-Indicate wether or not entering the port is required
-Provide meaningful error message to indicate the problem (server connection vs auth)

Screenshots or Additional Context

Keep up the good work, this is interesting, lots of potential! Interested to see if I can make it useful once the browser pluggin works.

Device Details

CHrome Version 132.0.6834.84, Pluggin v1.2.3

Exact Hoarder Version

0.21.0

Have you checked the troubleshooting guide?

I have checked the troubleshooting guide and I haven't found a solution to my problem

Originally created by @brainsoft1 on GitHub (Jan 21, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/921 ### Describe the Bug Attempt to sign-in to the Chrome pluggin but get a "Failed to Fetch" error after entering email and password. ### Steps to Reproduce Click Chrome Extension Enter server IP:Port (also attempted with only IP, no port specified) either way the extension progresses to next screen. I can only assume the server was reached, but the behaviour is the same even if I put a bad IP in. enter email and password > Failed To Fetch ### Expected Behaviour -Visual feedback to user that you have reached the server. Bad server address should be identified before login attempt. -Indicate wether or not entering the port is required -Provide meaningful error message to indicate the problem (server connection vs auth) ### Screenshots or Additional Context Keep up the good work, this is interesting, lots of potential! Interested to see if I can make it useful once the browser pluggin works. ### Device Details CHrome Version 132.0.6834.84, Pluggin v1.2.3 ### Exact Hoarder Version 0.21.0 ### Have you checked the troubleshooting guide? - [x] I have checked the troubleshooting guide and I haven't found a solution to my problem

kerem closed this issue

2026-03-02 11:51:17 +03:00

kerem commented

2026-03-02 11:51:18 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Jan 21, 2025):

can you try adding "http://" before the address? This is a common problem that we're planning to add validation for.

@MohamedBassem commented on GitHub (Jan 21, 2025): can you try adding "http://" before the address? This is a common problem that we're planning to add validation for.

kerem commented

2026-03-02 11:51:18 +03:00

Author

Owner

@brainsoft1 commented on GitHub (Jan 21, 2025):

Yes, this did the trick. Indicating protocol and port requirement would be a good idea, even if it is just to pre-populate the default values

Keep in mind the other user feedback above, You should never even get to a login screen until a basic server handshake has been completed to confirm (to the user) that something is listening.

I'll keep playing around, I think this project does a lot more than I currently appreciate, keep up the good work :)

@brainsoft1 commented on GitHub (Jan 21, 2025): Yes, this did the trick. Indicating protocol and port requirement would be a good idea, even if it is just to pre-populate the default values Keep in mind the other user feedback above, You should never even get to a login screen until a basic server handshake has been completed to confirm (to the user) that something is listening. I'll keep playing around, I think this project does a lot more than I currently appreciate, keep up the good work :)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#607

No description provided.

Rows
Columns