claude-code - 💡(How to fix) Fix [Bug] Domain allowlist not propagating to cowork-egress proxy after configuration update [1 comments, 2 participants]

Persistent error: "Host '***.context-link.ai' is not on the network allowlist (cowork-egress-blocked)"

TL;DR

The cowork-egress proxy may not be properly updating its allowlist from the user configuration, causing newly added domains to be blocked.

Guidance

• Verify that the ~/.claude/settings.json file is correctly formatted and contains the newly added domain (giy.context-link.ai) under sandbox.network.allowedDomains.
• Check if there are any caching mechanisms or synchronization issues between the Claude Desktop application and the cowork-egress proxy that could be preventing the updated allowlist from being applied.
• Investigate the possibility of the Unix socket proxy maintaining its own independent list of allowed domains, which may not be updated when changes are made to the user configuration.
• Consider manually updating the cowork-egress proxy's allowlist or restarting the proxy service to see if it resolves the issue.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be related to a synchronization or caching problem between the Claude Desktop application and the cowork-egress proxy. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply workaround: Manually update the cowork-egress proxy's allowlist or restart the proxy service to see if it resolves the issue, as the root cause of the problem is not clearly identified.