[GH-ISSUE #1912] After upgrading to 0.27.0 every bookmark show "Something went wrong" when clicking on preview button

kerem commented

2026-03-02 11:55:36 +03:00

Owner

Originally created by @ballerbude on GitHub (Sep 8, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1912

Describe the Bug

After the upgrade to 0.27.0 (docker), every existing bookmark opens a big "Something went wrong" text when clicking on the preview button (two arrows on the bottom of the bookmark), in place of the actual preview.

UPDATE: I figured out, when the preview with the "Something went wrong" is open, and I press F5 to refresh the page, it acually show the preview properly. But then, the next time, it's the same game when I open the same bookmark: "Something went wrong", F5, preview shows again.

I checked the docker logs, but nothing suspicious there:

web-1 | 2025-09-08T10:27:57.908Z info: --> GET /api/assets/dc8b4e60-76e6-4e15-a50e-34333ee0f9a3 200 3ms
web-1 | 2025-09-08T10:27:57.908Z info: --> GET /api/assets/51d93e0f-98fb-4807-bb45-025494da0f07 200 1ms
web-1 | 2025-09-08T10:27:57.910Z info: --> GET /api/assets/e27a446e-b8a9-4b92-935c-46881e7b7d49 200 3ms
web-1 | 2025-09-08T10:27:57.939Z info: <-- GET /api/assets/4a6ed334-735d-4691-b47e-bac0b38993b2
web-1 | 2025-09-08T10:27:57.941Z info: --> GET /api/assets/4a6ed334-735d-4691-b47e-bac0b38993b2 200 2ms
web-1 | 2025-09-08T10:27:58.002Z info: <-- GET /api/assets/b9ed0035-4565-4e3e-b634-b2817194c778
web-1 | 2025-09-08T10:27:58.005Z info: --> GET /api/assets/b9ed0035-4565-4e3e-b634-b2817194c778 200 3ms
web-1 | 2025-09-08T10:27:58.021Z info: <-- GET /api/assets/512317cb-b4e9-4d99-81ab-26ab0eb5e014
web-1 | 2025-09-08T10:27:58.023Z info: --> GET /api/assets/512317cb-b4e9-4d99-81ab-26ab0eb5e014 200 2ms

Steps to Reproduce

Go to Karakeep
Click on preview button (two arrows)
See text "Something went wrong" instead of the actual archived preview
Press F5 to refresh, the preview shows
Close Karakeep, then go back again to Karakeep
Open the same bookmark, and "Something went wrong" shows again
Press F5 again, the preview is shown properly

Expected Behaviour

After clicking on the two arrows you see your archived bookmark directly, without having to refresh with F5 every time

Screenshots or Additional Context

Device Details

Windows, Linux, Firefox, Edge, Chromium, Brave

Exact Karakeep Version

0.27.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 @ballerbude on GitHub (Sep 8, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1912 ### Describe the Bug After the upgrade to 0.27.0 (docker), every existing bookmark opens a big "Something went wrong" text when clicking on the preview button (two arrows on the bottom of the bookmark), in place of the actual preview. **UPDATE:** I figured out, when the preview with the "Something went wrong" is open, and I press F5 to refresh the page, it acually show the preview properly. But then, the next time, it's the same game when I open the same bookmark: "Something went wrong", F5, preview shows again. I checked the docker logs, but nothing suspicious there: > web-1 | 2025-09-08T10:27:57.908Z info: --> GET /api/assets/dc8b4e60-76e6-4e15-a50e-34333ee0f9a3 200 3ms > web-1 | 2025-09-08T10:27:57.908Z info: --> GET /api/assets/51d93e0f-98fb-4807-bb45-025494da0f07 200 1ms > web-1 | 2025-09-08T10:27:57.910Z info: --> GET /api/assets/e27a446e-b8a9-4b92-935c-46881e7b7d49 200 3ms > web-1 | 2025-09-08T10:27:57.939Z info: <-- GET /api/assets/4a6ed334-735d-4691-b47e-bac0b38993b2 > web-1 | 2025-09-08T10:27:57.941Z info: --> GET /api/assets/4a6ed334-735d-4691-b47e-bac0b38993b2 200 2ms > web-1 | 2025-09-08T10:27:58.002Z info: <-- GET /api/assets/b9ed0035-4565-4e3e-b634-b2817194c778 > web-1 | 2025-09-08T10:27:58.005Z info: --> GET /api/assets/b9ed0035-4565-4e3e-b634-b2817194c778 200 3ms > web-1 | 2025-09-08T10:27:58.021Z info: <-- GET /api/assets/512317cb-b4e9-4d99-81ab-26ab0eb5e014 > web-1 | 2025-09-08T10:27:58.023Z info: --> GET /api/assets/512317cb-b4e9-4d99-81ab-26ab0eb5e014 200 2ms ### Steps to Reproduce 1. Go to Karakeep 2. Click on preview button (two arrows) 3. See text "Something went wrong" instead of the actual archived preview 4. Press F5 to refresh, the preview shows 5. Close Karakeep, then go back again to Karakeep 6. Open the same bookmark, and "Something went wrong" shows again 7. Press F5 again, the preview is shown properly ### Expected Behaviour After clicking on the two arrows you see your archived bookmark directly, without having to refresh with F5 every time ### Screenshots or Additional Context ![Image](https://github.com/user-attachments/assets/951e2340-517c-4da7-b480-3ba52f9ef8ef) ### Device Details Windows, Linux, Firefox, Edge, Chromium, Brave ### Exact Karakeep Version 0.27.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

2026-03-02 11:55:36 +03:00

closed this issue
added the
bug

status/untriaged
labels

kerem commented

2026-03-02 11:55:37 +03:00

Author

Owner

@wzzrd commented on GitHub (Sep 10, 2025):

Yeah, can confirm. App works fine in one go though (without errors), so it might be a problem in the frontend.

@wzzrd commented on GitHub (Sep 10, 2025): Yeah, can confirm. App works fine in one go though (without errors), so it might be a problem in the frontend.

kerem commented

2026-03-02 11:55:37 +03:00

Author

Owner

@jecal22 commented on GitHub (Sep 13, 2025):

Just started using karakeep last night via docker compose, version 0.27.0. It seemed to be working pretty well. Today I imported my bookmarks from HTML (about 230 bookmarks) and now anytime I click on a bookmark to load the preview I get the same "Something went wrong" message. Refreshing the page seems to make it work, but when clicking back to the preview it does the same thing.

@jecal22 commented on GitHub (Sep 13, 2025): Just started using karakeep last night via docker compose, version 0.27.0. It seemed to be working pretty well. Today I imported my bookmarks from HTML (about 230 bookmarks) and now anytime I click on a bookmark to load the preview I get the same "Something went wrong" message. Refreshing the page seems to make it work, but when clicking back to the preview it does the same thing.

kerem commented

2026-03-02 11:55:37 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

hmmm, this seems like some sort of bug but I need more details. You mentioned that there’s nothing in the logs, but is there anything in the browser console logs?

@MohamedBassem commented on GitHub (Sep 13, 2025): hmmm, this seems like some sort of bug but I need more details. You mentioned that there’s nothing in the logs, but is there anything in the browser console logs?

kerem commented

2026-03-02 11:55:37 +03:00

Author

Owner

@jecal22 commented on GitHub (Sep 13, 2025):

Looks like when the issue happens, getting a 404 on the following URL:
https://[domain]/_next/static/chunks/app/dashboard/%40modal/(.)preview/%5BbookmarkId%5D/page-b28287358547282c.js

When refreshing the page, do not see this chunks/.../page-b2828735857282c.js URL. If I access the URL direct, I also get a 404.

The console shows related output:

8315-959a832ae978fa35.js:1 ChunkLoadError: Loading chunk 9731 failed.
(error: https://[domain]/_next/static/chunks/app/dashboard/%40modal/(.)preview/%5BbookmarkId%5D/page-b28287358547282c.js)
at Object.j (webpack-d2870adef487656b.js:1:3698)
at webpack-d2870adef487656b.js:1:1253
at Array.reduce ()
at r.e (webpack-d2870adef487656b.js:1:1232)
at i (8315-959a832ae978fa35.js:1:122396)
at 8315-959a832ae978fa35.js:1:134980
at t (8315-959a832ae978fa35.js:1:136429)

@jecal22 commented on GitHub (Sep 13, 2025): Looks like when the issue happens, getting a 404 on the following URL: https://[domain]/_next/static/chunks/app/dashboard/%40modal/(.)preview/%5BbookmarkId%5D/page-b28287358547282c.js When refreshing the page, do not see this chunks/.../page-b2828735857282c.js URL. If I access the URL direct, I also get a 404. The console shows related output: 8315-959a832ae978fa35.js:1 ChunkLoadError: Loading chunk 9731 failed. (error: https://[domain]/_next/static/chunks/app/dashboard/%40modal/(.)preview/%5BbookmarkId%5D/page-b28287358547282c.js) at Object.j (webpack-d2870adef487656b.js:1:3698) at webpack-d2870adef487656b.js:1:1253 at Array.reduce (<anonymous>) at r.e (webpack-d2870adef487656b.js:1:1232) at i (8315-959a832ae978fa35.js:1:122396) at 8315-959a832ae978fa35.js:1:134980 at t (8315-959a832ae978fa35.js:1:136429)

kerem commented

2026-03-02 11:55:37 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

@jecal22 are you using brave by any chance?

@MohamedBassem commented on GitHub (Sep 13, 2025): @jecal22 are you using brave by any chance?

kerem commented

2026-03-02 11:55:38 +03:00

Author

Owner

@jecal22 commented on GitHub (Sep 13, 2025):

@MohamedBassem Nope, using Edge 140.0.3485.66.

Just tested in Firefox 142.0.1 (64-bit) and same issue.

@jecal22 commented on GitHub (Sep 13, 2025): @MohamedBassem Nope, using Edge 140.0.3485.66. Just tested in Firefox 142.0.1 (64-bit) and same issue.

kerem commented

2026-03-02 11:55:38 +03:00

Author

Owner

@jecal22 commented on GitHub (Sep 13, 2025):

The URL being requested appears strange to me. Almost like maybe a string or variable is not being replaced or parsed properly when building that URL for the front end resulting in the 404? Or maybe that's an error in the javascript. I'm not a proficient web developer so not sure where that URL request is actually coming from.

@jecal22 commented on GitHub (Sep 13, 2025): The URL being requested appears strange to me. Almost like maybe a string or variable is not being replaced or parsed properly when building that URL for the front end resulting in the 404? Or maybe that's an error in the javascript. I'm not a proficient web developer so not sure where that URL request is actually coming from.

kerem commented

2026-03-02 11:55:38 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

The URL indeed looks a bit weird, but I checked the demo website and exactly the same URL is being requested and served.

I assume the same problem doesn't happen on https://try.karakeep.app ?

Also, do you have any proxy in between you and karakeep? Cloudflare? Nginx? Caddy? If yes, can you try hitting the web container directly and see if the problem reproduces? To rule out some layer along the way causing the error.

@MohamedBassem commented on GitHub (Sep 13, 2025): The URL indeed looks a bit weird, but I checked the demo website and exactly the same URL is being requested and served. <img width="1124" height="498" alt="Image" src="https://github.com/user-attachments/assets/a4f0fa34-3aa2-40e0-b378-5831db7ac9e9" /> I assume the same problem doesn't happen on https://try.karakeep.app ? Also, do you have any proxy in between you and karakeep? Cloudflare? Nginx? Caddy? If yes, can you try hitting the web container directly and see if the problem reproduces? To rule out some layer along the way causing the error.

kerem commented

2026-03-02 11:55:38 +03:00

Author

Owner

@jecal22 commented on GitHub (Sep 13, 2025):

Indeed, the URL is the same on try.karakeep.app and I do not have the problem.

I do have apache reverse proxy in front of the karakeep server. I just bypassed the reverse proxy and connected directly to the server and it is working just fine. So appears to be the reverse proxy layer.

I did notice in the HTTP request for that URL, there was an additional "Link" response header that was not present when going direct or using the demo app with the value:

Link: </_next/static/media/e4af272ccee01ff0-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/css/de5c7bdaf9df0104.css>; rel=preload; as="style"

@jecal22 commented on GitHub (Sep 13, 2025): Indeed, the URL is the same on try.karakeep.app and I do not have the problem. I do have apache reverse proxy in front of the karakeep server. I just bypassed the reverse proxy and connected directly to the server and it is working just fine. So appears to be the reverse proxy layer. I did notice in the HTTP request for that URL, there was an additional "Link" response header that was not present when going direct or using the demo app with the value: Link: </_next/static/media/e4af272ccee01ff0-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/css/de5c7bdaf9df0104.css>; rel=preload; as="style"

kerem commented

2026-03-02 11:55:38 +03:00

Author

Owner

@jecal22 commented on GitHub (Sep 13, 2025):

I think I found the answer. I did a capture from the karakeep server when using the reverse proxy and when not. When using the reverse proxy, I saw the %40 in the URL was being decoded and sent as @modal instead of %40modal. Whereas when I went direct, the request was being sent as-is, %40modal.

After some searching, I found this posting: https://stackoverflow.com/questions/69453809/how-to-use-proxypass-to-send-a-query-parameter-without-encoding-it

All I did was add "nocanon" to the parameters of my ProxyPass configruation:

ProxyPass "/" "http://:4000/" nocanon

After this, pages are loading normally without the 404 error and needing to refresh.

Update: I just cleared my browser cache and tested again from login and it worked flawlessly the first time, so I'm sticking with this as a solution for my issue. Of course, this would only be for instances where karakeep is behind apache reverse proxy.

@jecal22 commented on GitHub (Sep 13, 2025): I think I found the answer. I did a capture from the karakeep server when using the reverse proxy and when not. When using the reverse proxy, I saw the %40 in the URL was being decoded and sent as @modal instead of %40modal. Whereas when I went direct, the request was being sent as-is, %40modal. After some searching, I found this posting: https://stackoverflow.com/questions/69453809/how-to-use-proxypass-to-send-a-query-parameter-without-encoding-it All I did was add "nocanon" to the parameters of my ProxyPass configruation: ProxyPass "/" "http://<IP>:4000/" nocanon After this, pages are loading normally without the 404 error and needing to refresh. Update: I just cleared my browser cache and tested again from login and it worked flawlessly the first time, so I'm sticking with this as a solution for my issue. Of course, this would only be for instances where karakeep is behind apache reverse proxy.

kerem commented

2026-03-02 11:55:38 +03:00

Author

Owner

@ballerbude commented on GitHub (Sep 13, 2025):

I use Apache as the reverse proxy as well, and I can confirm that nocanon solved the issue for me. Thanks @jecal22 big time! It not even solved this issue, but also another issue with another software that I was troubleshooting for weeks now.

@ballerbude commented on GitHub (Sep 13, 2025): I use Apache as the reverse proxy as well, and I can confirm that nocanon solved the issue for me. Thanks @jecal22 big time! It not even solved this issue, but also another issue with another software that I was troubleshooting for weeks now.

kerem commented

2026-03-02 11:55:38 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Sep 13, 2025):

@jecal22 glad you figured it out! Thanks for sharing the fix as well! I'll close this issue now that it worked for both of you :)

@MohamedBassem commented on GitHub (Sep 13, 2025): @jecal22 glad you figured it out! Thanks for sharing the fix as well! I'll close this issue now that it worked for both of you :)

kerem referenced this issue

2026-03-02 11:59:59 +03:00

[PR #2083] [MERGED] feat: display notes on bookmark card #1969

Rows
Columns

[GH-ISSUE #1912] After upgrading to 0.27.0 every bookmark show "Something went wrong" when clicking on preview button #1183

Describe the Bug

Steps to Reproduce

Expected Behaviour

Screenshots or Additional Context

Device Details

Exact Karakeep Version

Have you checked the troubleshooting guide?