8000 > Has anyone been able to configure `nginx-ingress -> fpm` ? Been unable to configure this · Issue #8207 · kubernetes/ingress-nginx · GitHub
[go: up one dir, main page]

Skip to content

> Has anyone been able to configure nginx-ingress -> fpm ? Been unable to configure this #8207

@viktor-lt

Description

@viktor-lt

Has anyone been able to configure nginx-ingress -> fpm ? Been unable to configure this

Have you managed to do it ? I'm still unable to run a simple website:

php:7.4-fpm -> EXPOSE 4243 -> /var/www/html/index.php -> <?php phpinfo(); ?>

ConfigMap -> SCRIPT_FILENAME: "/var/www/html/index.php"

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
 name: fcgi-ingress
 namespace: website
 annotations:
   kubernetes.io/ingress.class: "nginx"
   nginx.ingress.kubernetes.io/backend-protocol: "FCGI"
   nginx.ingress.kubernetes.io/fastcgi-index: "index.php"
   nginx.ingress.kubernetes.io/fastcgi-params-configmap: "namespace/example-cm"
   cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
  tls:
    - hosts:
        - example.com
      secretName: fcgi-services-tls
 rules:
   - host: example.com
     http:
       paths:
         - path:
           backend:
             serviceName: example-service
             servicePort: 4243
2022/01/30 12:27:19 [error] 3856#3856: *17034482 connect() failed (111: Connection refused) while connecting to upstream, client: 37.120.247.34, server: example.com, request: "GET / HTTP/2.0", upstream: "fastcgi://192.168.75.42:4243", host: "example.com"

Originally posted by @vikomte in #6602 (comment)

Metadata

Metadata

Assignees

Labels

lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.needs-kindIndicates a PR lacks a `kind/foo` label and requires one.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0