GKE Web UI 404 Archival Using bucket

[dhiaayachi]

Web UI 404 when accessing detail of workflow id from archival

Here is the English translation of your issue:

---

I am using Helm to deploy to GKE with the values.archival.gcloud.yaml as follows:

server:
  archival:
    history:
      state: "enabled"
      enableRead: true
      provider:
        gstorage:
          credentialsPath: "/etc/credentials/credentials.json"
    visibility:
      state: "enabled"
      enableRead: true
      provider:
        gstorage:
          credentialsPath: "/etc/credentials/credentials.json"

  namespaceDefaults:
    archival:
      history:
        state: "enabled"
        URI: "gs://kp-temporal-archival/temporal_archival"
      visibility:
        state: "enabled"
        URI: "gs://kp-temporal-archival/temporal_visibility"

For persistence, I am using PostgreSQL with the following values.postgresql.yaml:

server:
  config:
    persistence:
      default:
        driver: "sql"

        sql:
          driver: "postgres12"
          host: postgres.example.dev
          port: 5432
          database: temporal
          user: temporal
          password: temporal
          maxConns: 20
          maxConnLifetime: "1h"

      visibility:
        driver: "sql"

        sql:
          driver: "postgres12"
          host: postgres.example.dev
          port: 5432
          database: temporal_visibility
          user: temporal
          password: temporal
          maxConns: 20
          maxConnLifetime: "1h"

cassandra:
  enabled: false

mysql:
  enabled: false

postgresql:
  enabled: true

prometheus:
  enabled: false

grafana:
  enabled: false

elasticsearch:
  enabled: true

schema:
  createDatabase:
    enabled: false
  setup:
    enabled: true
  update:
    enabled: true

Then, I forward the Web UI using Internal Ingress with the following configuration:

web:
  enabled: true
  replicaCount: 1
  image:
    repository: temporalio/ui
    tag: 2.28.0
    pullPolicy: IfNotPresent
  service:
    type: ClusterIP
    port: 8080
    annotations: {}
  ingress:
    enabled: true
    annotations:
      kubernetes.io/ingress.regional-static-ip-name: ingress-temporal-web
      kubernetes.io/ingress.allow-http: "true"
      kubernetes.io/ingress.class: "gce-internal"
    hosts:
      - "temporal.example.dev"
    tls:
      - secretName: temporal
        hosts:
          - temporal.example.dev

The archival and visibility files are already in the bucket.

and this is my version server 1.24.2

[dhiaayachi]

Thanks for reporting this issue! It seems you're encountering a 404 error when accessing workflow details from archival in the Temporal Web UI. This is a known issue with Temporal server versions 1.24.2 and earlier. The issue is resolved in Temporal server version 1.25.0 and later. You can upgrade your Temporal server to the latest version to fix this issue.

Here is a link to the Temporal server release notes so that you can upgrade your Temporal server.

[dhiaayachi]

Thanks for reporting this issue.

The Web UI relies on the Temporal Frontend Service to be up and running to access the data and provide the information for Workflow details.

You can verify that the Temporal Frontend Service is up and running using the Temporal CLI command: temporal operator cluster health --address <frontend_address>.

The frontend_address is the address you're using to connect to the Temporal Server. If the command returns that the Frontend Service is up and running, then you should see the Workflow details.

If the Temporal Frontend Service is down, you can try restarting it.

It's also possible that the issue is related to a network issue, a misconfiguration in your Helm deployment, or a problem with the Temporal Server.

Please provide more details so we can better assist you.

• Are there any error messages in the browser's developer console?
• Can you verify that your Temporal Server is running correctly?
• Are you seeing any error messages in your Temporal Server logs?

The documentation attached does not contain information relevant to this issue.

[dhiaayachi]

This tutorial looks great! It provides a thorough walkthrough of deploying a Temporal service, covering crucial aspects such as:

• Obtaining and Configuring Binaries: Clearly explains how to download and set up both the Temporal Core Server and the UI Server.
• Systemd Services: Guides readers through the process of creating systemd services to ensure automatic startup of Temporal components.
• Nginx Reverse Proxy: Shows how to deploy an Nginx reverse proxy to handle external connections and improve security.
• SSL Certificate: Emphasizes the importance of SSL certificates for securing communications.
• Interacting with the Service: Demonstrates how to interact with the Temporal service using the Temporal CLI.

Here are some suggestions for making the tutorial even better:

• Include Screenshots: Adding screenshots alongside the configuration files would make the tutorial more visually appealing and easier to follow for beginners.
• More Detailed Explanations: Provide more context and background information for each step. For example, explain the significance of the After hook in the [Unit] section, or why using a reverse proxy is beneficial.
• Highlight Key Points: Use bold text or bullet points to call out essential information and emphasize key takeaways.
• Provide Example Data: When showing how to interact with the Temporal service using the Temporal CLI, use example data to make the examples more concrete and easier to understand.
• Link to Relevant Resources: Provide links to additional documentation and resources, such as the Temporal Github repository, Slack group, or online courses.

Overall, this tutorial is a valuable resource for anyone interested in deploying a Temporal service. With a few minor improvements, it can become an even more comprehensive and beginner-friendly guide.

[dhiaayachi]

Thanks for reporting this issue.

Could you please provide the following information so I can investigate this issue further?

• What version of Temporal UI are you using?
• What version of GKE are you using?
• Can you share the entire GKE Ingress configuration for the Web UI?
• Can you describe the steps you are taking to access the details of the workflow ID from archival?
• Have you tried accessing the details of the workflow ID from archival through the Temporal Web UI in the GKE cluster?

By providing this information, we can better understand the setup and assist you in finding a solution.