run-llama/sec-insights
1
0
Fork 0
mirror of https://github.com/run-llama/sec-insights.git synced 2026-07-01 20:24:03 -04:00
Code Issues 44 Packages Projects Releases Wiki Activity

Could not connect to the endpoint URL: "http://localhost:4566/llama-app-backend-local" #25

New Issue
Closed
opened 2026-02-15 23:16:51 -05:00 by yindo · 4 comments
yindo commented 2026-02-15 23:16:51 -05:00
Owner
Copy Link
Copy Source

Originally created by @BytesByJay on GitHub (Oct 19, 2023).

I'm encountering this error in both CodeSpace and on my local machine.

image

File "/root/.cache/pypoetry/virtualenvs/llama-app-backend-9TtSrW0h-py3.11/lib/python3.11/site-packages/aiobotocore/endpoint.py", line 285, in _send
    return await self.http_session.send(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/.cache/pypoetry/virtualenvs/llama-app-backend-9TtSrW0h-py3.11/lib/python3.11/site-packages/aiobotocore/httpsession.py", line 253, in send
    raise EndpointConnectionError(endpoint_url=request.url, error=e)
botocore.exceptions.EndpointConnectionError: Could not connect to the endpoint URL: "http://localhost:4566/llama-app-backend-local"
Originally created by @BytesByJay on GitHub (Oct 19, 2023). I'm encountering this error in both CodeSpace and on my local machine. ![image](https://github.com/run-llama/sec-insights/assets/82816086/789429e8-c96c-4b7a-a3d6-60b5cf9219e9) ```sh File "/root/.cache/pypoetry/virtualenvs/llama-app-backend-9TtSrW0h-py3.11/lib/python3.11/site-packages/aiobotocore/endpoint.py", line 285, in _send return await self.http_session.send(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/root/.cache/pypoetry/virtualenvs/llama-app-backend-9TtSrW0h-py3.11/lib/python3.11/site-packages/aiobotocore/httpsession.py", line 253, in send raise EndpointConnectionError(endpoint_url=request.url, error=e) botocore.exceptions.EndpointConnectionError: Could not connect to the endpoint URL: "http://localhost:4566/llama-app-backend-local" ```
yindo closed this issue 2026-02-15 23:16:51 -05:00
yindo commented 2026-02-15 23:16:51 -05:00
Author
Owner
Copy Link
Copy Source

@sourabhdesai commented on GitHub (Oct 20, 2023):

@DhananjayanOnline can you provide more context on when you're seeing this error? Is this when running a particular make command or when taking a certain action on the frontend?

@sourabhdesai commented on GitHub (Oct 20, 2023): @DhananjayanOnline can you provide more context on when you're seeing this error? Is this when running a particular `make` command or when taking a certain action on the frontend?
yindo commented 2026-02-15 23:16:51 -05:00
Author
Owner
Copy Link
Copy Source

@mphipps2 commented on GitHub (Oct 20, 2023):

@sourabhdesai I have the same error as @DhananjayanOnline.

I get this error when setting up my environment for the first time and while testing the backend through make chat. I added new documents in the same way as the youtube video and get this response in the chat window:

(Chat🦙) message What are the three scaling factors?
=== Message 0 ===
{'id': 'cc08e26b-b0dd-4adf-a0c7-635d84c2f443', 'created_at': '2023-10-20T20:02:14.371304', 'updated_at': '2023-10-20T20:02:14.371304', 'conversation_id': 'f32b33e5-a035-4ef3-8878-11162c9e5430', 'content': '', 'role': 'assistant', 'status': 'ERROR', 'sub_processes': []}

And in my localstack log I get the same error shown above.

Some more details:

  • I'm running this from behind a proxy but seem to have that part of it worked out. I have external connectivity and set $no_proxy for these local addresses:
    export no_proxy="localhost,127.0.0.1,llama-app-fastapi,db,localstack"
  • http://localhost:8001/api/document/ looks good:
    [
    {
    "id": "bb50458d-94e2-4cf5-a1cc-0fb438ef0da1",
    "created_at": "2023-10-20T02:14:46.346857",
    "updated_at": "2023-10-20T02:14:46.346857",
    "url": "https://arxiv.org/pdf/2310.05915.pdf",
    "metadata_map": {}
    },
    {
    "id": "34f131d5-d146-4441-bece-53b03c215b65",
    "created_at": "2023-10-20T02:26:10.007830",
    "updated_at": "2023-10-20T02:26:10.007830",
    "url": "https://arxiv.org/pdf/1706.03762.pdf",
    "metadata_map": {}
    }
    ]
  • Similarly, http://localhost:4566/health looks good with all the services available.
  • I'm able to curl from my local machine: curl http://localhost:4566/health as well with all the services showing up
  • however, if I try to curl from inside llama-app-fastapi I get an empty reply:
    $ docker-compose exec llama-app-fastapi curl http://localstack:4566/health
    curl: (52) Empty reply from server
  • ie) the issue seems to be connectivity between the containers, not between host and container
  • So finally, I tried editing the app/core/config.py S3_ENDPOINT_URL to call "http://localstack:4566" instead of localhost. This resulted in a slightly different error in the localstack log during the make chat message:

llama-app-fastapi_1 | File "/lib/python3.11/site-packages/aiobotocore/httpsession.py", line 240, in send
llama-app-fastapi_1 | raise ConnectionClosedError(
llama-app-fastapi_1 | botocore.exceptions.ConnectionClosedError: Connection was closed before we received a valid response from endpoint URL: "http://localstack:4566/llama-app-backend-local".

Any help here would be much appreciated.

@mphipps2 commented on GitHub (Oct 20, 2023): @sourabhdesai I have the same error as @DhananjayanOnline. I get this error when setting up my environment for the first time and while testing the backend through make chat. I added new documents in the same way as the youtube video and get this response in the chat window: (Chat🦙) message What are the three scaling factors? === Message 0 === {'id': 'cc08e26b-b0dd-4adf-a0c7-635d84c2f443', 'created_at': '2023-10-20T20:02:14.371304', 'updated_at': '2023-10-20T20:02:14.371304', 'conversation_id': 'f32b33e5-a035-4ef3-8878-11162c9e5430', 'content': '', 'role': 'assistant', 'status': 'ERROR', 'sub_processes': []} And in my localstack log I get the same error shown above. Some more details: - I'm running this from behind a proxy but seem to have that part of it worked out. I have external connectivity and set $no_proxy for these local addresses: export no_proxy="localhost,127.0.0.1,llama-app-fastapi,db,localstack" - http://localhost:8001/api/document/ looks good: [ { "id": "bb50458d-94e2-4cf5-a1cc-0fb438ef0da1", "created_at": "2023-10-20T02:14:46.346857", "updated_at": "2023-10-20T02:14:46.346857", "url": "https://arxiv.org/pdf/2310.05915.pdf", "metadata_map": {} }, { "id": "34f131d5-d146-4441-bece-53b03c215b65", "created_at": "2023-10-20T02:26:10.007830", "updated_at": "2023-10-20T02:26:10.007830", "url": "https://arxiv.org/pdf/1706.03762.pdf", "metadata_map": {} } ] - Similarly, http://localhost:4566/health looks good with all the services available. - I'm able to curl from my local machine: curl http://localhost:4566/health as well with all the services showing up - however, if I try to curl from inside llama-app-fastapi I get an empty reply: $ docker-compose exec llama-app-fastapi curl http://localstack:4566/health curl: (52) Empty reply from server - ie) the issue seems to be connectivity between the containers, not between host and container - So finally, I tried editing the app/core/config.py S3_ENDPOINT_URL to call "http://localstack:4566" instead of localhost. This resulted in a slightly different error in the localstack log during the make chat message: llama-app-fastapi_1 | File "/lib/python3.11/site-packages/aiobotocore/httpsession.py", line 240, in send llama-app-fastapi_1 | raise ConnectionClosedError( llama-app-fastapi_1 | botocore.exceptions.ConnectionClosedError: Connection was closed before we received a valid response from endpoint URL: "http://localstack:4566/llama-app-backend-local". Any help here would be much appreciated.
yindo commented 2026-02-15 23:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@BytesByJay commented on GitHub (Oct 21, 2023):

@DhananjayanOnline can you provide more context on when you're seeing this error? Is this when running a particular make command or when taking a certain action on the frontend?

@sourabhdesai I was encountering this error when sending a message in the chat section, but now it seems to be working fine. I'm not sure what happened.

Additionally, I'm curious if it's possible to use Minio instead of S3 buckets. If so, could you please advise me on what changes are required to make that switch?

@BytesByJay commented on GitHub (Oct 21, 2023): > @DhananjayanOnline can you provide more context on when you're seeing this error? Is this when running a particular `make` command or when taking a certain action on the frontend? @sourabhdesai I was encountering this error when sending a message in the chat section, but now it seems to be working fine. I'm not sure what happened. Additionally, I'm curious if it's possible to use Minio instead of S3 buckets. If so, could you please advise me on what changes are required to make that switch?
yindo commented 2026-02-15 23:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@mphipps2 commented on GitHub (Oct 21, 2023):

Edit: this problem is fixed on my end now. Starting from scratch on the backend and following the readme/youtube instructions cleared things up

@mphipps2 commented on GitHub (Oct 21, 2023): Edit: this problem is fixed on my end now. Starting from scratch on the backend and following the readme/youtube instructions cleared things up
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/sec-insights#25
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?