Fail on AWS (API?)

Bug #1850211 reported by Erik Lönroth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Graylog Charm
Invalid
Undecided
Unassigned

Bug Description

Even if I try to deploy using --constraints "mem=4G", I get this error after deploying this bundle on AWS.

```
series: bionic
applications:
  elasticsearch:
    charm: cs:~elasticsearch-charmers/elasticsearch-20
    num_units: 1
    to:
    - "2"
    constraints: mem=4096
  graylog:
    charm: cs:~graylog-charmers/graylog-50
    num_units: 1
    to:
    - "0"
    expose: true
    constraints: mem=4096
  mongodb:
    charm: cs:~mongodb-charmers/mongodb-11
    num_units: 1
    to:
    - "1"
machines:
  "0":
    constraints: mem=4096
  "1": {}
  "2":
    constraints: mem=4096
relations:
- - graylog:mongodb
  - mongodb:database
- - graylog:elasticsearch
  - elasticsearch:client

```

Revision history for this message
Erik Lönroth (erik-lonroth) wrote :
Revision history for this message
Drew Freiberger (afreiberger) wrote :

You may need to add an apache2 instance on an AWS instance (not container) and review the Reverse Proxy configuration section of the graylog charm documentation here:

https://jaas.ai/graylog

The issue is that your desktop/browser cannot reach the network for the URL of the api service. If you place an apache2 reverse proxy in front of graylog, you can override the API URL and make it an externally accessible service. That 252 address appears to be a FAN network address for AWS.

Changed in graylog-charm:
status: New → Incomplete
Revision history for this message
Drew Freiberger (afreiberger) wrote :

Please provide more information about the provider/cloud/VPC configuration of your AWS environment and whether the 252 address is an accessible/routed network or is a FAN network.

Revision history for this message
Erik Lönroth (erik-lonroth) wrote :

I should have noticed the 252.X.X.X address being a FAN network. I have a default VPC so there is nothing in there besides defaults, so a reverse-proxy would be the way forward here?

I'll give it a go.

Revision history for this message
Erik Lönroth (erik-lonroth) wrote :

Right, by just adding in a reverse proxy, this works for me now.

I used this template for apache2

```
<Location "/">
RequestHeader set X-Graylog-Server-URL "http://{{servername}}/api/"
ProxyPass http://{{graylog_web}}/
ProxyPassReverse http://{{graylog_web}}/
</Location>

<Location "/api/">
ProxyPass http://{{graylog_api}}/api/
ProxyPassReverse http://{{graylog_api}}/api/
</Location>
```

Then I could test it without tls (which I would add in later)

Changed in graylog-charm:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.