[GH-ISSUE #340] Hoarder CLI failes to connect using HTTPS, but works for HTTP #222

Closed
opened 2026-03-02 11:47:45 +03:00 by kerem · 4 comments
Owner

Originally created by @Antebios on GitHub (Aug 2, 2024).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/340

I am following instructions to upload my large HTML export. When trying to use the Hoarder CLI using HTTP works, but failes when using HTTPS.

image

The web interface is working great over HTTPS.

Originally created by @Antebios on GitHub (Aug 2, 2024). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/340 I am following instructions to upload my large HTML export. When trying to use the Hoarder CLI using HTTP works, but failes when using HTTPS. ![image](https://github.com/user-attachments/assets/2aa64034-e1db-49e4-868e-28663a94643f) The web interface is working great over HTTPS.
kerem 2026-03-02 11:47:45 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@kamtschatka commented on GitHub (Aug 3, 2024):

Do you have a proper SSL certificate? Since it works via HTTP, it must have something to do with the secure connection, so maybe you have a self signed certificate?

<!-- gh-comment-id:2266738085 --> @kamtschatka commented on GitHub (Aug 3, 2024): Do you have a proper SSL certificate? Since it works via HTTP, it must have something to do with the secure connection, so maybe you have a self signed certificate?
Author
Owner

@Antebios commented on GitHub (Aug 3, 2024):

Yes. Though this is my homelab, I have DNS and home domain's certificate server working perfectly. I was running this command from the machine that is on the domain with the root certificate loaded. And the HTTPS URL works perfectly.

image

I do have a reverse proxy in my homelab, and the routing is working pefectly:
image

<!-- gh-comment-id:2266763437 --> @Antebios commented on GitHub (Aug 3, 2024): Yes. Though this is my homelab, I have DNS and home domain's certificate server working perfectly. I was running this command from the machine that is on the domain with the root certificate loaded. And the HTTPS URL works perfectly. ![image](https://github.com/user-attachments/assets/de7af3fb-56d6-4eca-ba27-51bd30188466) I do have a reverse proxy in my homelab, and the routing is working pefectly: ![image](https://github.com/user-attachments/assets/c848a1a7-3095-43cb-8609-e892f92b15f9)
Author
Owner

@kamtschatka commented on GitHub (Sep 21, 2024):

Did you get it to work?
My guess would be that the self signed certificate is simply not accepted in node. Your screenshot is showing that The browser accepts the certificate, but node.js seems to have its own certificate store, where it would need to be accepted.

Seems like if you set "NODE_TLS_REJECT_UNAUTHORIZED", you can cause node to ignore self signed certificate errors.
https://stackoverflow.com/questions/68592669/how-to-set-value-for-node-tls-reject-unauthorized-0-in-mac

<!-- gh-comment-id:2365282528 --> @kamtschatka commented on GitHub (Sep 21, 2024): Did you get it to work? My guess would be that the self signed certificate is simply not accepted in node. Your screenshot is showing that The browser accepts the certificate, but node.js seems to have its own certificate store, where it would need to be accepted. Seems like if you set "NODE_TLS_REJECT_UNAUTHORIZED", you can cause node to ignore self signed certificate errors. https://stackoverflow.com/questions/68592669/how-to-set-value-for-node-tls-reject-unauthorized-0-in-mac
Author
Owner

@kamtschatka commented on GitHub (Oct 13, 2024):

closing as there was no response. We can reopen if there is a response

<!-- gh-comment-id:2409029867 --> @kamtschatka commented on GitHub (Oct 13, 2024): closing as there was no response. We can reopen if there is a response
Sign in to join this conversation.
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#222
No description provided.