Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Atomic red team collector won't start, connection to api/documents/upsert refused #2639

Open
clr2of8 opened this issue Mar 9, 2025 · 1 comment
Labels
question use for asking information about a functionality or behavior

Comments

@clr2of8
Copy link

clr2of8 commented Mar 9, 2025

Description

I just upgraded from v1.12.2 to v1.13.1 and my same configs give error and can't successfully start atomic red team collector.

Environment

OS: Ubuntu 24.04.2
OpenBAS v1.13.1
OpenBAS client: frontend

Expected Output

Atomic red team container to not have errors and to be able to use them in atomic testings.

Actual Output

File "/usr/local/lib/python3.13/site-packages/requests/sessions.py", line 589, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.13/site-packages/requests/sessions.py", line 703, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.13/site-packages/requests/adapters.py", line 700, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='linux.cloudlab.lan', port=8080): Max retries exceeded with url: /api/documents/upsert (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7d04d96c5fd0>: Failed to establish a new connection: [Errno 111] Connection refused'))

Additional information

I can browse to linux.cloudlab.lan on port 8080 just fine but there is no api/documents/upsert document, causing the atomic testings to not load the atomic red team tests.

@clr2of8 clr2of8 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 9, 2025
@jborozco jborozco added question use for asking information about a functionality or behavior and removed bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 10, 2025
@jborozco
Copy link

Can't reproduce I'm adding the label question so the issue can be managed by the on call team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question use for asking information about a functionality or behavior
Projects
None yet
Development

No branches or pull requests

2 participants