StrangeBeeCorp / TheHive-feedback

TheHive 5 feedback repository
https://www.strangebee.com/thehive
5 stars 0 forks source link

Bug uploading picture into alert #5

Closed priamai closed 2 years ago

priamai commented 2 years ago

Request Type

Bug

Work Environment

Question Answer
OS version (server) Ubuntu
OS version (client) Windows
Virtualized Env. False
Dedicated RAM 32 GB
vCPU 8
TheHive version 5.x.x
Package Type Docker
Database Builtin
Index type Builtin
Attachments storage Local
Browser type & version Chrome

Problem Description

In an incident I try to upload an image. Nothing happens and lot of red errors in the browser console.

Steps to Reproduce

  1. Create a case from an alert
  2. Go to Pages
  3. Create a Page
  4. Add an image

Complementary information

image

My docker setup:

version: "3"
services:
  thehive:
    image: strangebee/thehive:latest
    mem_limit: 1500m
    user: root
    ports:
      - "9000:9000"
    environment:
      - JVM_OPTS="-Xms1024M -Xmx1024M"
    command:
      - --secret
      - "victoriasecret2022!"
      - "--no-config-cortex"
    volumes:
      - thehive_db:/data/db
      - thehive_files:/data/files
      - thehive_index:/data/index
volumes:
  thehive_db:
  thehive_files:
  thehive_index:
vdebergue commented 2 years ago

It seems like there is an issue with the docker entrypoint where it's trying to configure S3 for file storage instead of the local folder. Adding this issue to 5.0.8

The only way around this at the moment is to use a custom config or to use a minio container

priamai commented 2 years ago

Understood, I will add a Minio service to my docker composer file. Cheers.

vdebergue commented 2 years ago

TheHive 5.0.8 was releases with the fix: https://docs.strangebee.com/thehive/release-notes/release-notes-5.0/#508-15-june-2022

Please reopen the issue if you have more issues with that or other questions. Thanks.

vdebergue commented 2 years ago

Oops just saw that the issue is still there with 5.0.8 (bash is hard), reopening it and fixing it for next release.

It will work correctly by providing the arguments --storage-directory <path_to_storage>

vdebergue commented 2 years ago

This is fixed in 5.0.9