Fresh Graylog on Docker local install cannot connect to API

Graylog Central (peer support)
2

Hey there,

So it’s odd that this isn’t working–I’ve not tested this exact scenario, but I have used compose with success on a Windows box. Here’s my default:

version: '3'
services:
  # MongoDB: https://hub.docker.com/_/mongo/
  mongo:
    image: mongo:4
    container_name: mongodb
    networks:
      - graylog
    ports:
      - 27018:27017
    volumes:
      - ./volumes/mongodb:/var/lib/mongodb
  # Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/6.x/docker.html
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2
    container_name: elasticsearch
    environment:
      - http.host=0.0.0.0
      - transport.host=localhost
      - network.host=0.0.0.0
      - "ES_JAVA_OPTS=-Xms1g -Xmx1g"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    deploy:
      resources:
        limits:
          memory: 1g
    ports:
      - 9200:9200
    networks:
      - graylog
    volumes: 
      - ./volumes/elasticsearch:/var/lib/elasticsearch
  # Graylog: https://hub.docker.com/r/graylog/graylog/
  graylog:
    image: graylog/graylog-enterprise:4.1.3
    container_name: graylog
    environment:
      - GRAYLOG_PASSWORD_SECRET=UNOSEEMYPASSWORDS
      - GRAYLOG_ROOT_PASSWORD_SHA2=SUPERSECRETSHAAAAAAA
      - GRAYLOG_HTTP_EXTERNAL_URI=http://127.0.0.1:9000/
      - GRAYLOG_ELASTICSEARCH_VERSION=7
      - GRAYLOG_HTTP_ENABLE_CORS=true
      - GRAYLOG_METRICS_PROMETHEUS_ENABLED=true
    networks:
      - graylog
    depends_on:
      - mongo
      - elasticsearch
    ports:
      # Graylog web interface and REST API
      - 9000:9000
      # Syslog TCP
      - 1514:1514
      # Syslog UDP
      - 1514:1514/udp
      # GELF TCP
      - 12201:12201
      # GELF UDP
      - 12201:12201/udp
      # Prometheus Endpoint
      - 9833:9833
    volumes:
      - ./archives:/tmp/graylog-archive
networks:
  graylog:
    driver: bridge

From what I’m seeing, there’s not a whole lot of difference. So I suspect there’s probably something earlier in the log that might shed some light. It might also be worth opening your browser’s dev console to see what errors show up there.

1 Like