【问题标题】:cloudfoundry bad gateway error on working application工作应用程序上的cloudfoundry错误网关错误
【发布时间】:2020-06-19 12:17:15
【问题描述】:

我将应用程序推送到 CloudFoundry,它在日志中显示应用程序已启动

但是我向 CF 实体发出的每个请求都以 BAD GATEWAY 失败

2020-06-19T14:10:52.67+0200 [RTR/12] OUT app-server-dev.com - 
[2020-06-19T12:10:52.672339821Z] "PUT /v2/service_instances/2bb29af7-c41a-4865-bfb8-a4ef6081438a?accepts_incomplete=true HTTP/1.1" 502 0 67 
"-" "PostmanRuntime/7.24.1" "10.10.2.187:28852" "10.10.17.168:61054" x_forwarded_for:"213.127.57.86, 10.10.2.187" x_forwarded_proto:"http" 
vcap_request_id:"efff0deb-2577-439b-703e-938b07012046" response_time:0.001090 gorouter_time:0.000109 app_id:"170c069e-7824-4dc7-bece-398faff72c92" app_index:"0" x_b3_traceid:"9d92b07d45abbdc9" 
x_b3_spanid:"9d92b07d45abbdc9" x_b3_parentspanid:"-" b3:"9d92b07d45abbdc9-9d92b07d45abbdc9"

在本地运行良好。我的清单看起来像这样

applications:
- buildpack: https://github.com/cloudfoundry/python-buildpack#v1.7.15
  disk_quota: 2G
  health-check-type: process
  command: python -m service
  instances: 1
  memory: 2G
  name: simple-app
  services:
    - dynamodb-service
  stack: cflinuxfs3
  routes:
  - route: app-server-dev.com

我从与清单所在的同一位置执行cf push,因此它从同一文件夹上传应用程序。在本地运行时,相同的命令也有效。

可能有什么问题?

【问题讨论】:

    标签: python flask cloud-foundry


    【解决方案1】:

    问题是在烧瓶中我没有指定主机并且它在主机127.0.0.1 上启动。我切换到0.0.0.0,它开始工作了。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 2019-05-25
      • 1970-01-01
      • 2016-05-20
      • 2016-01-22
      • 1970-01-01
      • 1970-01-01
      • 2013-05-14
      • 1970-01-01
      相关资源
      最近更新 更多