[bug]: while login via the app, backend hoppscotch shows as 503 service unavailable about hoppscotch HOT 3 OPEN

Hey @mrfzy00 could you share your nginx config file here ?

from hoppscotch.

hi @balub , i'm using the nginx ingress, not using nginx here's the config:

    ingress:
      enabled: true
      className: "nginx"
      annotations:
        #kubernetes.io/ingress.class: nginx
        cert-manager.io/cluster-issuer: letsencrypt-staging
        # kubernetes.io/tls-acme: "true"
      hosts:
        - host: hoppscotch-be.xxx.xxx
          paths:
            - path: /
              pathType: ImplementationSpecific
      tls:
      - secretName: hoppscotch-be-tls
        hosts:
          - hoppscotch-be.xxx.xxx
      service:
        port: 3000

from hoppscotch.

@mrfzy00 could you check if the backend service is up and active, maybe calling the ping route? When we spin up the backend for the first time we populate the DB with config props and terminate it, If it's docker we use the --restart unless-stopped flag to restart the container when we do this, maybe in your case it didn't restart automatically. Could you just check this once?

This explains why you can only see the Hoppscotch app and not the admin app and the Backend because the Hoppscotch app is cached with a service worker so you can use it offline. But can you log in and do other things related to workspaces in it though?

from hoppscotch.