I am writing to report a persistent issue I am experiencing with connection timeouts when my ComfyUI instance, hosted on your server in Tokyo, Japan, attempts to interact with the BFL API.
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
### Custom Node Testing
- [x] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)
### Expected Behavior
worked
### Actual Behavior
1. Environment:
ComfyUI Version: 0.3.50
Custom Node: comfy_api_nodes (specifically FluxKontextProImageNode)
Server Location: Tokyo, Japan
Server Public IP (if applicable): [Your Server Public IP here]
2. Problem Description:
I am consistently encountering aiohttp.client_exceptions.ConnectionTimeoutError when ComfyUI tries to communicate with the BFL API. The specific endpoint causing issues is https://api.eu4.bfl.ai/v1/get_result?id=....
The stack trace indicates that the timeout occurs during the polling phase of the API request (line 80 in comfy_api_nodes/nodes_bfl.py), where ComfyUI attempts to retrieve the status and results of a previously submitted task.
While most attempts result in a timeout, I have observed instances where the initial task submission succeeds (indicated by a "Request Moderated" error in the logs for certain prompts). This suggests that the initial connection to api.eu4.bfl.ai can sometimes be established, but the subsequent and continuous polling connections are highly unstable and frequently time out.
3. Network Diagnostics (from Tokyo Server):
I have performed network diagnostics from my Tokyo server, which strongly suggest a routing or connectivity issue between my server's location and the BFL EU data center (api.eu4.bfl.ai).
Target IP Address: api.eu4.bfl.ai resolves to 9.223.154.130.
ping results: [Attach ping results here, showing high latency and/or packet loss]
traceroute results: [Attach traceroute results here, showing where the connection drops or becomes very slow]
These diagnostics consistently show high latency, significant packet loss, and timeouts when attempting to reach 9.223.154.130.
4. Observed Contrast with BFL CDN:
It's important to note that I am able to access BFL's content delivery network (e.g., delivery-us1.bfl.ai) without any connectivity issues. This indicates that the problem is specific to the direct API endpoint (api.eu4.bfl.ai) and its routing from my region, rather than a general block or issue with BFL's service.
5. Troubleshooting Taken by User:
Confirmed network connectivity issues to 9.223.154.130 using ping and traceroute.
Attempted to modify ComfyUI's --comfy-api-base argument, but the comfy_api_nodes custom node appears to be hardcoded or inherently designed to use the api.eu4.bfl.ai endpoint for polling (as the polling URL is provided by the BFL API itself, which I cannot control).
### Steps to Reproduce
aiohttp.client_exceptions.ConnectionTimeoutError: Connection timeout to host https://api.eu4.bfl.ai/v1/get_result?id=9088916b-b4e5-4b43-a061-d3fac7a69204
### Debug Logs
```powershell
aiohttp.client_exceptions.ConnectionTimeoutError: Connection timeout to host https://api.eu4.bfl.ai/v1/get_result?id=9088916b-b4e5-4b43-a061-d3fac7a69204
```
### Other
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.