Fail on AWS (API?)
Bug #1850211 reported by
Erik Lönroth
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:~elasticsear
num_units: 1
to:
- "2"
constraints: mem=4096
graylog:
charm: cs:~graylog-
num_units: 1
to:
- "0"
expose: true
constraints: mem=4096
mongodb:
charm: cs:~mongodb-
num_units: 1
to:
- "1"
machines:
"0":
constraints: mem=4096
"1": {}
"2":
constraints: mem=4096
relations:
- - graylog:mongodb
- mongodb:database
- - graylog:
- elasticsearch:
```
Changed in graylog-charm: | |
status: | Incomplete → Invalid |
To post a comment you must log in.
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.