starred/karakeep

Fork 0

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

[GH-ISSUE #2285] Error: Refusing to access disallowed resolved address #1395

New issue

Closed

opened 2026-03-02 11:57:00 +03:00 by kerem · 9 comments

kerem commented

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

Owner

Originally created by @TastyChickenLegs on GitHub (Dec 21, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2285

Describe the Bug

Hello, I have been working with an error for several days and have reached a point of giving up. I am attempting to post an API call to my n8n server on the crawled event. I am familar with n8n and have tested the api call from postman and it is working. Days of debugging has brought me to the conclusion that Karakeep is not ever sending the api call to n8n. I am getting the following error. These are not production and all information will be changed.

2025-12-21T17:49:23.391Z error: [webhook][43] Webhook to https://n8n.tclmods.com/webhook-test/d737e828-aa4b-495b-b556-250f4acebc89 call failed: Error: Refusing to access disallowed resolved address 192.168.10.11 for host n8n.tclmods.com

Steps to Reproduce

Create api call in n8n and select the "listen for test event".
Move back to Karakeep and enter in the api url and authorization key.
Select a unique bookmark and enter it into the "new item" section on the main page of Karakeep
Click to add item.
Book mark appears with picture after a few seconds.
Nothing ever reaches the n8n server.

Expected Behaviour

Once the site is crawled, an even should be fired and a Post call sent to n8n. This never happens.

Screenshots or Additional Context

I appreciate any help and also wanted to thank you for an excellent product.

Device Details

Version 143.0.7499.170 (Official Build) (64-bit) Windows 11 Enterprise LTSC

Exact Karakeep Version

v0.29.3

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 @TastyChickenLegs on GitHub (Dec 21, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2285 ### Describe the Bug Hello, I have been working with an error for several days and have reached a point of giving up. I am attempting to post an API call to my n8n server on the crawled event. I am familar with n8n and have tested the api call from postman and it is working. Days of debugging has brought me to the conclusion that Karakeep is not ever sending the api call to n8n. I am getting the following error. These are not production and all information will be changed. ` 2025-12-21T17:49:23.391Z error: [webhook][43] Webhook to https://n8n.tclmods.com/webhook-test/d737e828-aa4b-495b-b556-250f4acebc89 call failed: Error: Refusing to access disallowed resolved address 192.168.10.11 for host n8n.tclmods.com` ### Steps to Reproduce Create api call in n8n and select the "listen for test event". Move back to Karakeep and enter in the api url and authorization key. Select a unique bookmark and enter it into the "new item" section on the main page of Karakeep Click to add item. Book mark appears with picture after a few seconds. Nothing ever reaches the n8n server. ### Expected Behaviour Once the site is crawled, an even should be fired and a Post call sent to n8n. This never happens. <img width="449" height="678" alt="Image" src="https://github.com/user-attachments/assets/5d819f9f-d9e9-4739-8615-ea511ffcc92f" /> <img width="1476" height="95" alt="Image" src="https://github.com/user-attachments/assets/83695660-159c-4084-88ce-f3c8f762f943" /> ### Screenshots or Additional Context I appreciate any help and also wanted to thank you for an excellent product. ### Device Details Version 143.0.7499.170 (Official Build) (64-bit) Windows 11 Enterprise LTSC ### Exact Karakeep Version v0.29.3 ### 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:57:00 +03:00

closed this issue
added the
bug

status/untriaged
labels

kerem commented

2026-03-02 11:57:01 +03:00

Author

Owner

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

sorry that you had to go through all this debugging. This is a security mechanism on karakeep that refuses sending requests to internal domains.

You can allowlist certain domains or disable this feature completely by the env variable CRAWLER_ALLOWED_INTERNAL_HOSTNAMES(check its docs here ). I'll followup with a PR to make the error message more descriptive.

@MohamedBassem commented on GitHub (Dec 21, 2025): sorry that you had to go through all this debugging. This is a security mechanism on karakeep that refuses sending requests to internal domains. You can allowlist certain domains or disable this feature completely by the env variable CRAWLER_ALLOWED_INTERNAL_HOSTNAMES(check its docs [here](https://docs.karakeep.app/configuration)[](https://docs.karakeep.app/configuration)). I'll followup with a PR to make the error message more descriptive.

kerem commented

2026-03-02 11:57:01 +03:00

Author

Owner

@TastyChickenLegs commented on GitHub (Dec 21, 2025):

I probably should have added the .env file. I have the following added in /opt/karakeep/.env

CRAWLER_ALLOWED_INTERNAL_HOSTNAMES=.com

This container was installed using the VE Helper scripts and the .env file is in the /opt/karakeep directory.

@TastyChickenLegs commented on GitHub (Dec 21, 2025): I probably should have added the .env file. I have the following added in /opt/karakeep/.env CRAWLER_ALLOWED_INTERNAL_HOSTNAMES=.com This container was installed using the VE Helper scripts and the .env file is in the /opt/karakeep directory.

kerem commented

2026-03-02 11:57:01 +03:00

Author

Owner

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

did you restart the service after updating the env file?

@MohamedBassem commented on GitHub (Dec 21, 2025): did you restart the service after updating the env file?

kerem commented

2026-03-02 11:57:01 +03:00

Author

Owner

@TastyChickenLegs commented on GitHub (Dec 21, 2025):

I did, several times. I have been working with this file and made several changes the Crawler_allowed_Internal_hostnames Your question leads me to believe that this should work and the .env file might not be loading. I will check to ensure this is the only .env file present on the system. I will report back with more information.

@TastyChickenLegs commented on GitHub (Dec 21, 2025): I did, several times. I have been working with this file and made several changes the Crawler_allowed_Internal_hostnames Your question leads me to believe that this should work and the .env file might not be loading. I will check to ensure this is the only .env file present on the system. I will report back with more information.

kerem commented

2026-03-02 11:57:01 +03:00

Author

Owner

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

Yes, this env variable should work unless this env file is not being loaded or something. Looking at the helper scripts (https://community-scripts.github.io/ProxmoxVE/scripts?id=karakeep), it says that the env file location is at /etc/karakeep/karakeep.env..

@MohamedBassem commented on GitHub (Dec 21, 2025): Yes, this env variable should work unless this env file is not being loaded or something. Looking at the helper scripts (https://community-scripts.github.io/ProxmoxVE/scripts?id=karakeep), it says that the env file location is at `/etc/karakeep/karakeep.env`..

kerem commented

2026-03-02 11:57:01 +03:00

Author

Owner

@TastyChickenLegs commented on GitHub (Dec 21, 2025):

Ok, I am going to wipe both Karakeep and N8N and start from scratch using the recommended Docker installation. I will set that up and report back if the problem persists. Thanks again for your help.

@TastyChickenLegs commented on GitHub (Dec 21, 2025): Ok, I am going to wipe both Karakeep and N8N and start from scratch using the recommended Docker installation. I will set that up and report back if the problem persists. Thanks again for your help.

kerem commented

2026-03-02 11:57:01 +03:00

Author

Owner

@TastyChickenLegs commented on GitHub (Dec 21, 2025):

This is fixed by installing the recommended Docker method. I'm sure the LXC installed version works fine, but I could not get my install to work. Keep in mind that I messed with the LXC version and cannot confidently say that it was the software at fault. More than likely it broke after the million changes I made. I am very happy this is fixed and I truly thank you for the quick response and assistance.

For reference, I did nothing special other than add CRAWLER_ALLOWED_INTERNAL_HOSTNAMES=. to the .env file. In the Docker version installed with Dockge the .env file is located in /var/opt/stacks/karakeep

Thanks again for everything and thank you for this brilliant software. If you have a "buy me a coffee" type link I will be sending a thank you. Have a great day.

@TastyChickenLegs commented on GitHub (Dec 21, 2025): This is fixed by installing the recommended Docker method. I'm sure the LXC installed version works fine, but I could not get my install to work. Keep in mind that I messed with the LXC version and cannot confidently say that it was the software at fault. More than likely it broke after the million changes I made. I am very happy this is fixed and I truly thank you for the quick response and assistance. For reference, I did nothing special other than add `CRAWLER_ALLOWED_INTERNAL_HOSTNAMES=.` to the .env file. In the Docker version installed with Dockge the .env file is located in /var/opt/stacks/karakeep Thanks again for everything and thank you for this brilliant software. If you have a "buy me a coffee" type link I will be sending a thank you. Have a great day.

kerem commented

2026-03-02 11:57:01 +03:00

Author

Owner

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

Glad that your problem is solved. Hope you enjoy using Karakeep! The donation links are in the readme of the repo :)

@MohamedBassem commented on GitHub (Dec 21, 2025): Glad that your problem is solved. Hope you enjoy using Karakeep! The donation links are in the readme of the repo :)

kerem commented

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

Author

Owner

@TastyChickenLegs commented on GitHub (Dec 21, 2025):

By the way I figured out the problem with the LXC install. I was changing the /opt/karakeep/karakeep.env file when the environment file is indeed /etc/karakeep/karakeep.env.... just like the install script says it is... I can't believe I missed that. I saw the location stated on the VE script site and never actually processed that it was /etc/ and not /opt/. All that time spent working on this problem. Well thanks again.

   mkdir -p /etc/karakeep
      mv /opt/karakeep/.env /etc/karakeep/karakeep.env

@TastyChickenLegs commented on GitHub (Dec 21, 2025): By the way I figured out the problem with the LXC install. I was changing the /opt/karakeep/karakeep.env file when the environment file is indeed /etc/karakeep/karakeep.env.... just like the install script says it is... I can't believe I missed that. I saw the location stated on the VE script site and never actually processed that it was /etc/ and not /opt/. All that time spent working on this problem. Well thanks again. ``` mkdir -p /etc/karakeep mv /opt/karakeep/.env /etc/karakeep/karakeep.env ```

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

No description provided.

Rows
Columns