AWS Elastic Beanstalk Django 應用程序健康檢查問題

Question

我遇到了與此處描述的問題非常相似的問題。 由於該問題沒有得到解答，並且我的問題與那里描述的問題之間存在一些差異，因此我決定提出一個新問題。

我設法將我的 Django 后端 API 部署到 AWS Elastic Beanstalk Amazon Linux 2 Python 3.7 平台。 但是，EB 實例的健康狀態為“嚴重”。 它顯示消息：

以下服務未運行：發布。

整體健康狀態為“降級”，消息為

所有實例上的服務受損。

有時會出現一條消息，指出所有響應均為 4xx。 這個消息來來去去。 奇怪的是，我配置了 2 個負載均衡器（一個用於 http，另一個用於 https），並且都具有應用程序中有效 url 的健康檢查路徑 url。

我能找到的唯一相關日志如下：

守護進程日志

F, [2020-11-05T00:07:40.486088 #15846] FATAL -- : /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/launcher.rb:432:in `block in setup_signals': SIGTERM (SignalException)
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/single.rb:117:in `join'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/single.rb:117:in `run'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/launcher.rb:172:in `run'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/puma-4.3.5/lib/puma/cli.rb:80:in `run'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/healthd-1.0.6/bin/healthd:112:in `block in <top (required)>'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/healthd-1.0.6/bin/healthd:19:in `chdir'
    from /opt/elasticbeanstalk/lib/ruby/lib/ruby/gems/2.6.0/gems/healthd-1.0.6/bin/healthd:19:in `<top (required)>'
    from /opt/elasticbeanstalk/lib/ruby/bin/healthd:23:in `load'
    from /opt/elasticbeanstalk/lib/ruby/bin/healthd:23:in `<main>'

標准輸出日志

(...)
Nov  5 09:26:18 ip-172-31-94-128 web: Invalid HTTP_HOST header: '52.86.81.51'. You may need to add '52.86.81.51' to ALLOWED_HOSTS.
Nov  5 09:26:18 ip-172-31-94-128 web: Bad Request: /
Nov  5 09:33:11 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:11 ip-172-31-94-128 web: Bad Request: /console/
Nov  5 09:33:12 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:12 ip-172-31-94-128 web: Bad Request: /index.php
Nov  5 09:33:16 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:16 ip-172-31-94-128 web: Bad Request: /
Nov  5 09:33:16 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:16 ip-172-31-94-128 web: Bad Request: /vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php
Nov  5 09:33:17 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:17 ip-172-31-94-128 web: Bad Request: /api/jsonws/invoke
Nov  5 09:33:20 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:20 ip-172-31-94-128 web: Bad Request: /solr/admin/info/system
Nov  5 09:33:22 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:22 ip-172-31-94-128 web: Bad Request: /vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php
Nov  5 09:33:24 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:24 ip-172-31-94-128 web: Bad Request: /wp-content/plugins/wp-file-manager/readme.txt
Nov  5 09:33:25 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 09:33:25 ip-172-31-94-128 web: Bad Request: /
Nov  5 09:35:29 ip-172-31-94-128 web: Not Found: /boaform/admin/formLogin
Nov  5 09:35:55 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.212.192.113'. You may need to add '18.212.192.113' to ALLOWED_HOSTS.
Nov  5 09:35:55 ip-172-31-94-128 web: Bad Request: /
Nov  5 09:41:21 ip-172-31-94-128 web: Invalid HTTP_HOST header: '54.243.237.110'. You may need to add '54.243.237.110' to ALLOWED_HOSTS.
Nov  5 09:41:21 ip-172-31-94-128 web: Bad Request: /remote/login
Nov  5 09:46:37 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.212.192.113'. You may need to add '18.212.192.113' to ALLOWED_HOSTS.
Nov  5 09:46:37 ip-172-31-94-128 web: Bad Request: /
Nov  5 09:49:41 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.212.192.113'. You may need to add '18.212.192.113' to ALLOWED_HOSTS.
Nov  5 09:49:41 ip-172-31-94-128 web: Bad Request: /
Nov  5 09:58:26 ip-172-31-94-128 web: Not Found: /
Nov  5 09:59:35 ip-172-31-94-128 web: Invalid HTTP_HOST header: '34.236.195.107'. You may need to add '34.236.195.107' to ALLOWED_HOSTS.
Nov  5 09:59:35 ip-172-31-94-128 web: Bad Request: /
Nov  5 09:59:35 ip-172-31-94-128 web: Invalid HTTP_HOST header: '34.236.195.107'. You may need to add '34.236.195.107' to ALLOWED_HOSTS.
Nov  5 09:59:35 ip-172-31-94-128 web: Bad Request: /
Nov  5 10:09:52 ip-172-31-94-128 web: Invalid HTTP_HOST header: '52.86.81.51'. You may need to add '52.86.81.51' to ALLOWED_HOSTS.
Nov  5 10:09:52 ip-172-31-94-128 web: Bad Request: /
Nov  5 10:10:35 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.212.192.113'. You may need to add '18.212.192.113' to ALLOWED_HOSTS.
Nov  5 10:10:35 ip-172-31-94-128 web: Bad Request: /
Nov  5 10:10:38 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.212.192.113'. You may need to add '18.212.192.113' to ALLOWED_HOSTS.
Nov  5 10:10:38 ip-172-31-94-128 web: Bad Request: /
Nov  5 10:20:03 ip-172-31-94-128 web: Invalid HTTP_HOST header: '52.86.81.51'. You may need to add '52.86.81.51' to ALLOWED_HOSTS.
Nov  5 10:20:03 ip-172-31-94-128 web: Bad Request: /
Nov  5 10:23:53 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 10:23:53 ip-172-31-94-128 web: Bad Request: /remote/login
Nov  5 10:36:49 ip-172-31-94-128 web: Invalid HTTP_HOST header: '34.236.195.107'. You may need to add '34.236.195.107' to ALLOWED_HOSTS.
Nov  5 10:36:49 ip-172-31-94-128 web: Bad Request: /
Nov  5 10:38:39 ip-172-31-94-128 web: Invalid HTTP_HOST header: '54.243.237.110'. You may need to add '54.243.237.110' to ALLOWED_HOSTS.
Nov  5 10:38:39 ip-172-31-94-128 web: Bad Request: /
Nov  5 10:42:26 ip-172-31-94-128 web: Not Found: /
Nov  5 10:42:49 ip-172-31-94-128 web: Invalid HTTP_HOST header: '52.86.81.51'. You may need to add '52.86.81.51' to ALLOWED_HOSTS.
Nov  5 10:42:49 ip-172-31-94-128 web: Bad Request: /
Nov  5 10:42:49 ip-172-31-94-128 web: Invalid HTTP_HOST header: '52.86.81.51'. You may need to add '52.86.81.51' to ALLOWED_HOSTS.
Nov  5 10:42:49 ip-172-31-94-128 web: Bad Request: /
Nov  5 11:05:54 ip-172-31-94-128 web: Invalid HTTP_HOST header: '18.210.4.127'. You may need to add '18.210.4.127' to ALLOWED_HOSTS.
Nov  5 11:05:54 ip-172-31-94-128 web: Bad Request: /

我不知道 daemon.log 中的錯誤是什么意思。 我在谷歌上搜索了錯誤並沒有發現任何相關內容。 另一方面，我不明白為什么會發出 web.stdout.log 中出現的請求。 發起請求的 IP 地址都來自美國弗吉尼亞州（我的服務器托管的區域），所以我猜測某些 AWS 資源發出的請求。 奇怪的是發出請求的路由：它們都不存在於我的應用程序中。

很感謝任何形式的幫助。 先感謝您。

Answer 1

快速解決方案：

您需要在項目的settings.py添加* → ALLOWED_HOSTS

ALLOWED_HOSTS = ['*']

長解決方案：

看起來您的IP地址是動態的，因此您需要通過域名而不是IP訪問，或者您需要允許所有IP，這意味着快速解決方案。

此處說明
同樣的問題