Hedgedoc Kubernetes

Support
1

My version of HedgeDoc is: hedgedoc:1.9.3

What I expected to happen:

I have Hadgedoc running in a Kubernetes Cluster In Opera Browser it loads the earlier saved documents, in Chrome and Firefox it is stucked in state loading.

What actually happened:

Ingress Configuration:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/proxy-connect-timeout: 3600s
    nginx.ingress.kubernetes.io/proxy-read-timeout: 3600s
    nginx.ingress.kubernetes.io/proxy-send-timeout: 3600s
  creationTimestamp: "2022-08-09T08:10:03Z"
  generation: 1
  name: ingress-hedgedoc
  namespace: hedgedoc
  resourceVersion: "20230831"
  uid: ee62c5a3-3f22-48b8-9920-4f292be54171
spec:
  defaultBackend:
    service:
      name: svc-clip-hedgedoc
      port:
        number: 80
  rules:
  - host: XXXX
    http:
      paths:
      - backend:
          service:
            name: svc-clip-hedgedoc
            port:
              number: 80
        path: /
        pathType: Prefix
      - backend:
          service:
            name: svc-clip-hedgedoc
            port:
              number: 80
        path: /build
        pathType: Prefix
      - backend:
          service:
            name: svc-clip-XXX
            port:
              number: 80
        path: /socket.io
        pathType: Prefix

status:

Hedgedoc Deployment Configuration:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: depl-hedgedoc
  namespace: hedgedoc
  labels:
    app: hedgedoc
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hedgedoc
  template:
    metadata:
      labels:
        app: hedgedoc
    spec:
      containers:
      - name: hedgedoc
        image: quay.io/hedgedoc/hedgedoc:1.9.3
        imagePullPolicy: "IfNotPresent"
        volumeMounts:
        - mountPath: /hedgedoc/public/uploads
          name: volume-hedgedoc
          subPath: hedgedoc
        ports:
        - containerPort: 3000
        env:
        - name: CMD_DB_URL
          value: postgres://hedgedoc:XXXX@svc-clip-postgres:5432/hedgedoc
        - name: CMD_DOMAIN
          value:  <domain>
        - name: CMD_URL_ADDPORT
          value: "false"
        - name: CMD_CSP_ENABLE
          value: "false"
        - name: CMD_PROTOCOL_USESSL
          value: "true"
        - name: CMD_COOKIE_POLICY
          value: "lax"
        - name: CMD_ALLOW_ANONYMOUS
          value: "true"
        - name: CMD_ALLOW_ANONYMOUS_EDITS
          value: "true"
        - name: CMD_SESSION_SECRET
          value: "XXXX"
      volumes:
      - name: volume-hedgedoc
        persistentVolumeClaim:
          claimName: pvc-nfs-hedgedoc
2

In my experience it is rarely the case that there is a server-side problem that distinguishes between one browser and another (unless it is Internet Explorer of course!). In other words, if one browser works properly with your deployment, then the problem in Chrome and Firefox is most likely browser-based.

Start with the basics: Did you try private browser tabs? Did you SHIFT+Reload the page? Did you open the developer panel and delete all localStorage and/or session cookies related to the website? Have you verified there are no browser plugins that may be interfering?