Google cloud platform Kong GCP堆栈问题:代理端口设置

Google cloud platform Kong GCP堆栈问题:代理端口设置,google-cloud-platform,proxy,bitnami,kong,Google Cloud Platform,Proxy,Bitnami,Kong,我使用Kong Bitnami GCP堆栈(版本2.2.0)作为API网关: 它在HTTP端口8000和HTTPS端口8443(默认配置)下运行良好。但是,当我尝试将生产环境的HTTP/HTTPS侦听端口更改为80/443时,通过以下链接:,出现了几个问题: 在我的Kong GCP堆栈中,没有名为“Kong_nginx.tmpl”的文件,因此我无法完全实现作为参考链接 我刚在kong.conf中输入了以下两个问题: 将()绑定到0.0.0.0:80失败(13:权限被拒绝) 绑定()到0.0.

我使用Kong Bitnami GCP堆栈(版本2.2.0)作为API网关:

它在HTTP端口8000和HTTPS端口8443(默认配置)下运行良好。但是,当我尝试将生产环境的HTTP/HTTPS侦听端口更改为80/443时,通过以下链接:,出现了几个问题:

  • 在我的Kong GCP堆栈中,没有名为“Kong_nginx.tmpl”的文件,因此我无法完全实现作为参考链接
  • 我刚在kong.conf中输入了以下两个问题:
    • 将()绑定到0.0.0.0:80失败(13:权限被拒绝)
    • 绑定()到0.0.0.0:443失败(13:权限被拒绝)
以下是我当前的配置步骤:

  • 运行:
    sudo/opt/bitnami/ctlscript.sh stop kong
  • 更改/opt/bitnami/kong/conf/kong.conf: 将
    proxy\u-listen=0.0.0.0:8000,0.0.0.0:8443 ssl更改为
    proxy\u-listen=0.0.0.0:80,0.0.0.0:443 ssl
  • 运行:
    sudo/opt/bitnami/ctlscript.sh
  • 如有任何意见或反馈,我们将不胜感激。非常感谢


    敬请注意,

    此错误的原因应与正在运行流程的用户有关。检查它的模块,我们可以找到

    /root/.nami/registry.json

    "com.bitnami.kong": {
                "id": "com.bitnami.kong",
                "name": "kong",
                "version": "2.2.1",
                "revision": "3",
                "installedAsRoot": false,
                "lifecycle": "installed",
                "installdir": "/opt/bitnami/kong",
                "installPrefix": "/opt/bitnami",
                "values": {
    ...
                    "systemUser": "kong",
                    "systemGroup": "kong",
    ...
    
       "service":     {
            "confFile": "{{$app.confDir}}/kong.conf",
            "pidFile": "{{$app.installdir}}/server/pids/nginx.pid",
            "logFile": "{{$app.installdir}}/server/logs/error.log",
            "ports":         [
                "{{$app.proxyHttpPort}}",
                "{{$app.proxyHttpsPort}}",
                "{{$app.adminHttpPort}}",
                "{{$app.adminHttpsPort}}"
            ],
            "start":         {
                "timeout": 180,
                "wait": 5,
                "username": "kong",
                "command": "{{$app.installdir}}/bin/kong start && tail -f {{$app.installdir}}/server/logs/error.log",
                "env": {"PATH": "{{$app.installdir}}/openresty/bin:{{$app.installdir}}/openresty/luajit/bin:{{$app.installdir}}/openresty/nginx/sbin:{{$global.env.PATH}}"}
            }
        },
    
    这里我们需要将
    'com.bitnami.kong'.values.systemUser
    'com.bitnami.kong'.values.systemGroup
    也更改为
    root

    另外,我们必须在另一个文件中更改它

    /root/.nami/components/com.bitnami.kong/nami.json

    "com.bitnami.kong": {
                "id": "com.bitnami.kong",
                "name": "kong",
                "version": "2.2.1",
                "revision": "3",
                "installedAsRoot": false,
                "lifecycle": "installed",
                "installdir": "/opt/bitnami/kong",
                "installPrefix": "/opt/bitnami",
                "values": {
    ...
                    "systemUser": "kong",
                    "systemGroup": "kong",
    ...
    
       "service":     {
            "confFile": "{{$app.confDir}}/kong.conf",
            "pidFile": "{{$app.installdir}}/server/pids/nginx.pid",
            "logFile": "{{$app.installdir}}/server/logs/error.log",
            "ports":         [
                "{{$app.proxyHttpPort}}",
                "{{$app.proxyHttpsPort}}",
                "{{$app.adminHttpPort}}",
                "{{$app.adminHttpsPort}}"
            ],
            "start":         {
                "timeout": 180,
                "wait": 5,
                "username": "kong",
                "command": "{{$app.installdir}}/bin/kong start && tail -f {{$app.installdir}}/server/logs/error.log",
                "env": {"PATH": "{{$app.installdir}}/openresty/bin:{{$app.installdir}}/openresty/luajit/bin:{{$app.installdir}}/openresty/nginx/sbin:{{$global.env.PATH}}"}
            }
        },
    
    然后我们必须将
    service.start.username
    更改为
    root

    然后,执行您执行的步骤

    请注意,您必须是root用户才能更新这些文件


    希望这对你有帮助

    问题解决了。非常感谢,丹尼尔!