starred/karakeep

Fork 0

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

[GH-ISSUE #25] Error: Something went wrong #22

New issue

Closed

opened 2026-03-02 11:45:48 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 11:45:48 +03:00

Owner

Originally created by @dyslexicjedi on GitHub (Mar 27, 2024).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/25

I'm attempting to add a text bookmark (markdown specifically) and I keep getting a red warning at the bottom of the screen saying "something went wrong". Which docker log should I look in for additional logging messages?

My text if it helps, just my own notes from doing cloudflare dns.

Cloudflared DNS

https://docs.pi-hole.net/guides/dns/cloudflared/

https://serverfault.com/questions/956447/bind-set-port-for-forwarders

AMD64 architecture (most devices)¶
Download the installer package, then use apt-get to install the package along with any dependencies. Proceed to run the binary with the -v flag to check it is all working:

For Debian/Ubuntu

wget https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb
sudo apt-get install ./cloudflared-linux-amd64.deb
cloudflared -v

Configuring cloudflared to run on startup¶
Create a cloudflared user to run the daemon:

sudo useradd -s /usr/sbin/nologin -r -M cloudflared
Proceed to create a configuration file for cloudflared:

sudo nano /etc/default/cloudflared
Edit configuration file by copying the following in to /etc/default/cloudflared. This file contains the command-line options that get passed to cloudflared on startup:

# Commandline args for cloudflared, using Cloudflare DNS
CLOUDFLARED_OPTS=--port 5053 --upstream https://1.1.1.1/dns-query --upstream https://1.0.0.1/dns-query

Update the permissions for the configuration file and cloudflared binary to allow access for the cloudflared user:

sudo chown cloudflared:cloudflared /etc/default/cloudflared
sudo chown cloudflared:cloudflared /usr/local/bin/cloudflared

Then create the systemd script by copying the following into /etc/systemd/system/cloudflared.service. This will control the running of the service and allow it to run on startup:

sudo nano /etc/systemd/system/cloudflared.service

[Unit]
Description=cloudflared DNS over HTTPS proxy
After=syslog.target network-online.target

[Service]
Type=simple
User=cloudflared
EnvironmentFile=/etc/default/cloudflared
ExecStart=/usr/local/bin/cloudflared proxy-dns $CLOUDFLARED_OPTS
Restart=on-failure
RestartSec=10
KillMode=process

[Install]
WantedBy=multi-user.target

Enable the systemd service to run on startup, then start the service and check its status:

sudo systemctl enable cloudflared
sudo systemctl start cloudflared
sudo systemctl status cloudflared

Now test that it is working! Run the following dig command, a response should be returned similar to the one below:

pi@raspberrypi:~ $ dig @127.0.0.1 -p 5053 google.com

; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> @127.0.0.1 -p 5053 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12157
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 22179adb227cd67b (echoed)
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             191     IN      A       172.217.22.14

;; Query time: 0 msec
;; SERVER: 127.0.0.1#5053(127.0.0.1)
;; WHEN: Wed Dec 04 09:29:50 EET 2019
;; MSG SIZE  rcvd: 77

Originally created by @dyslexicjedi on GitHub (Mar 27, 2024). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/25 I'm attempting to add a text bookmark (markdown specifically) and I keep getting a red warning at the bottom of the screen saying "something went wrong". Which docker log should I look in for additional logging messages? My text if it helps, just my own notes from doing cloudflare dns. ----- Cloudflared DNS https://docs.pi-hole.net/guides/dns/cloudflared/ https://serverfault.com/questions/956447/bind-set-port-for-forwarders AMD64 architecture (most devices)¶ Download the installer package, then use apt-get to install the package along with any dependencies. Proceed to run the binary with the -v flag to check it is all working: # For Debian/Ubuntu ``` wget https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb sudo apt-get install ./cloudflared-linux-amd64.deb cloudflared -v ``` Configuring cloudflared to run on startup¶ Create a cloudflared user to run the daemon: `sudo useradd -s /usr/sbin/nologin -r -M cloudflared` Proceed to create a configuration file for cloudflared: sudo nano /etc/default/cloudflared Edit configuration file by copying the following in to /etc/default/cloudflared. This file contains the command-line options that get passed to cloudflared on startup: ``` # Commandline args for cloudflared, using Cloudflare DNS CLOUDFLARED_OPTS=--port 5053 --upstream https://1.1.1.1/dns-query --upstream https://1.0.0.1/dns-query ``` Update the permissions for the configuration file and cloudflared binary to allow access for the cloudflared user: ``` sudo chown cloudflared:cloudflared /etc/default/cloudflared sudo chown cloudflared:cloudflared /usr/local/bin/cloudflared ``` Then create the systemd script by copying the following into /etc/systemd/system/cloudflared.service. This will control the running of the service and allow it to run on startup: sudo nano /etc/systemd/system/cloudflared.service ``` [Unit] Description=cloudflared DNS over HTTPS proxy After=syslog.target network-online.target [Service] Type=simple User=cloudflared EnvironmentFile=/etc/default/cloudflared ExecStart=/usr/local/bin/cloudflared proxy-dns $CLOUDFLARED_OPTS Restart=on-failure RestartSec=10 KillMode=process [Install] WantedBy=multi-user.target ``` Enable the systemd service to run on startup, then start the service and check its status: ``` sudo systemctl enable cloudflared sudo systemctl start cloudflared sudo systemctl status cloudflared ``` Now test that it is working! Run the following dig command, a response should be returned similar to the one below: ``` pi@raspberrypi:~ $ dig @127.0.0.1 -p 5053 google.com ; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> @127.0.0.1 -p 5053 google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12157 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 22179adb227cd67b (echoed) ;; QUESTION SECTION: ;google.com. IN A ;; ANSWER SECTION: google.com. 191 IN A 172.217.22.14 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#5053(127.0.0.1) ;; WHEN: Wed Dec 04 09:29:50 EET 2019 ;; MSG SIZE rcvd: 77 ```

kerem

2026-03-02 11:45:48 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-02 11:45:49 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Mar 27, 2024):

Thanks for sharing your note. I can indeed reproduce the issue. The container logs that show the issue is in hoarder-web-1.
The error you're getting is because there's a 2000 char limit on the size of the note. In a hindsight, 2k is quite small. I'll drop the limit completely or increase it to something much larger.

I should probably also show you a proper error message instead of the generic Something went wrong.

Thanks for reporting the issue, I'll send the fix soon! :)

@MohamedBassem commented on GitHub (Mar 27, 2024): Thanks for sharing your note. I can indeed reproduce the issue. The container logs that show the issue is in `hoarder-web-1`. The error you're getting is because there's a 2000 char limit on the size of the note. In a hindsight, 2k is quite small. I'll drop the limit completely or increase it to something much larger. I should probably also show you a proper error message instead of the generic `Something went wrong`. Thanks for reporting the issue, I'll send the fix soon! :)

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#22

No description provided.

Rows
Columns