starred/hoppscotch
1
0
Fork 0
mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00
Code Issues 711 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #4938] [bug]: Deploy with Helm charts hoppscotch with image: hoppscotch/hoppscotch and tag 2025.2.3 #1866

New issue
Closed
opened 2026-03-16 22:09:55 +03:00 by kerem · 6 comments
kerem commented 2026-03-16 22:09:55 +03:00
Owner
Copy link

Originally created by @oo00spy00oo on GitHub (Mar 26, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4938

Is there an existing issue for this?

  • I have searched existing issues and this bug hasn't been reported yet

Current behavior

I've tried with these configuration when install with Helm charts with image: hoppscotch/hoppscotch and tag 2025.2.3. When the application are deployed, I cannot access the application via domain, I also try to forward traffic from Kubernetes server to my local machine but have no available server to access. The deployment logs looks fine:

Image

Steps to reproduce

Solution 1: with subpath diable:

community:
  replicas: 1
  image:
    repository: hoppscotch/hoppscotch
    tag: 2025.2.3
    pullPolicy: IfNotPresent
  migration:
    upgradeEnabled: true
  config:
    database:
      external: true
      url: "<REDACTED>"
    rateLimit:
      ttl: 60
      max: 100
    authjwt:
      sessionSecret: "<REDACTED>"
      jwtSecret: "<REDACTED>"
    auth:
      allowedProviders: "GITHUB"
      github:
        clientId: "<REDACTED>"
        clientSecret: "<REDACTED>"
        callbackUrl: "http://hoppscotch-backend.example.com/v1/auth/github/callback"
        scope: "user:email"
    community:
      enableSubpathBasedAccess: false
    urls:
      base: "https://hoppscotch.example.com"
      shortcode: "https://hoppscotch.example.com"
      admin: "https://hoppscotch-admin.example.com"
      backend:
        gql: "https://hoppscotch-backend.example.com/graphql"
        ws: "wss://hoppscotch-backend.example.com/graphql"
        api: "http://hoppscotch-backend.example.com/v1"
      redirect: "https://hoppscotch.example.com"
      whitelistedOrigins: "https://hoppscotch-backend.example.com,https://hoppscotch.example.com,https://hoppscotch-admin.example.com,http://hoppscotch-backend.example.com,http://hoppscotch.example.com,http://hoppscotch-admin.example.com"
service:
  ingress:
    enabled: true
    className: traefik
    mainHost: hoppscotch.example.com
    adminHost: hoppscotch-admin.example.com
    backendHost: hoppscotch-backend.example.com

Solution 2: With subpath enable

community:
  replicas: 1
  image:
    repository: hoppscotch/hoppscotch
    tag: 2025.2.3
    pullPolicy: IfNotPresent
  migration:
    upgradeEnabled: true
  config:
    database:
      external: true
      url: "<REDACTED>"
    rateLimit:
      ttl: 60
      max: 100
    authjwt:
      sessionSecret: "<REDACTED>"
      jwtSecret: "<REDACTED>"
    auth:
      allowedProviders: "GITHUB"
      github:
        clientId: "<REDACTED>"
        clientSecret: "<REDACTED>"
        callbackUrl: "http://hoppscotch.example.com/backend/v1/auth/github/callback"
        scope: "user:email"
    community:
      enableSubpathBasedAccess: true
    urls:
      base: "https://hoppscotch.example.com"
      shortcode: "https://hoppscotch.example.com"
      admin: "https://hoppscotch.example.com/admin"
      backend:
        gql: "https://hoppscotch.example.com/backend/graphql"
        ws: "wss://hoppscotch.example.com/backend/graphql"
        api: "http://hoppscotch.example.com/backend/v1"
      redirect: "https://hoppscotch.example.com"
      whitelistedOrigins: "https://hoppscotch.example.com,https://hoppscotch.example.com/admin,https://hoppscotch.example.com/graphql"
service:
  ingress:
    enabled: true
    className: traefik
    mainHost: hoppscotch.example.com
    adminHost: hoppscotch.example.com/admin
    backendHost: hoppscotch.example.com/backend

Logs and Screenshots

Environment

Production

Hoppscotch Version

Self-hosted

Interceptor

Not Applicable - Issue not related to network requests

Browsers Affected

No response

Operating System

None

Additional Information

No response

Originally created by @oo00spy00oo on GitHub (Mar 26, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4938 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior I've tried with these configuration when install with Helm charts with image: hoppscotch/hoppscotch and tag 2025.2.3. When the application are deployed, I cannot access the application via domain, I also try to forward traffic from Kubernetes server to my local machine but have no available server to access. The deployment logs looks fine: <img width="1026" alt="Image" src="https://github.com/user-attachments/assets/648904c9-f6ec-4052-b90c-e843147d15f7" /> ### Steps to reproduce Solution 1: with subpath diable: ```yaml community: replicas: 1 image: repository: hoppscotch/hoppscotch tag: 2025.2.3 pullPolicy: IfNotPresent migration: upgradeEnabled: true config: database: external: true url: "<REDACTED>" rateLimit: ttl: 60 max: 100 authjwt: sessionSecret: "<REDACTED>" jwtSecret: "<REDACTED>" auth: allowedProviders: "GITHUB" github: clientId: "<REDACTED>" clientSecret: "<REDACTED>" callbackUrl: "http://hoppscotch-backend.example.com/v1/auth/github/callback" scope: "user:email" community: enableSubpathBasedAccess: false urls: base: "https://hoppscotch.example.com" shortcode: "https://hoppscotch.example.com" admin: "https://hoppscotch-admin.example.com" backend: gql: "https://hoppscotch-backend.example.com/graphql" ws: "wss://hoppscotch-backend.example.com/graphql" api: "http://hoppscotch-backend.example.com/v1" redirect: "https://hoppscotch.example.com" whitelistedOrigins: "https://hoppscotch-backend.example.com,https://hoppscotch.example.com,https://hoppscotch-admin.example.com,http://hoppscotch-backend.example.com,http://hoppscotch.example.com,http://hoppscotch-admin.example.com" service: ingress: enabled: true className: traefik mainHost: hoppscotch.example.com adminHost: hoppscotch-admin.example.com backendHost: hoppscotch-backend.example.com ``` Solution 2: With subpath enable ```yaml community: replicas: 1 image: repository: hoppscotch/hoppscotch tag: 2025.2.3 pullPolicy: IfNotPresent migration: upgradeEnabled: true config: database: external: true url: "<REDACTED>" rateLimit: ttl: 60 max: 100 authjwt: sessionSecret: "<REDACTED>" jwtSecret: "<REDACTED>" auth: allowedProviders: "GITHUB" github: clientId: "<REDACTED>" clientSecret: "<REDACTED>" callbackUrl: "http://hoppscotch.example.com/backend/v1/auth/github/callback" scope: "user:email" community: enableSubpathBasedAccess: true urls: base: "https://hoppscotch.example.com" shortcode: "https://hoppscotch.example.com" admin: "https://hoppscotch.example.com/admin" backend: gql: "https://hoppscotch.example.com/backend/graphql" ws: "wss://hoppscotch.example.com/backend/graphql" api: "http://hoppscotch.example.com/backend/v1" redirect: "https://hoppscotch.example.com" whitelistedOrigins: "https://hoppscotch.example.com,https://hoppscotch.example.com/admin,https://hoppscotch.example.com/graphql" service: ingress: enabled: true className: traefik mainHost: hoppscotch.example.com adminHost: hoppscotch.example.com/admin backendHost: hoppscotch.example.com/backend ``` ### Logs and Screenshots ```shell ``` ### Environment Production ### Hoppscotch Version Self-hosted ### Interceptor Not Applicable - Issue not related to network requests ### Browsers Affected _No response_ ### Operating System None ### Additional Information _No response_
kerem 2026-03-16 22:09:55 +03:00
kerem commented 2026-03-16 22:10:11 +03:00
Author
Owner
Copy link

@g3Bg2 commented on GitHub (Mar 26, 2025):

@oo00spy00oo

To access you have to add your domain name.

Replace,
hoppscotch.example.com with hoppscotch.yourdomainname.com
hoppscotch-admin.example.com with hoppscotch-admin.yourdomainname.com
hoppscotch-backend.example.com with hoppscotch-backend.yourdomainname.com

To attach the IP address to your domain.
kubectl get ingress (this command will provide the IP address of you cluster)

<!-- gh-comment-id:2753497599 --> @g3Bg2 commented on GitHub (Mar 26, 2025): @oo00spy00oo To access you have to add your domain name. Replace, hoppscotch.example.com with **hoppscotch.yourdomainname.com** hoppscotch-admin.example.com with **hoppscotch-admin.yourdomainname.com** hoppscotch-backend.example.com with **hoppscotch-backend.yourdomainname.com** To attach the IP address to your domain. `kubectl get ingress ` (this command will provide the IP address of you cluster)
kerem commented 2026-03-16 22:10:16 +03:00
Author
Owner
Copy link

@oo00spy00oo commented on GitHub (Mar 26, 2025):

@oo00spy00oo

To access you have to add your domain name.

Replace,
hoppscotch.example.com with hoppscotch.yourdomainname.com
hoppscotch-admin.example.com with hoppscotch-admin.yourdomainname.com
hoppscotch-backend.example.com with hoppscotch-backend.yourdomainname.com

To attach the IP address to your domain.
kubectl get ingress (this command will provide the IP address of you cluster)

I know that, guy

I replaced my real domain by example.com

<!-- gh-comment-id:2753514140 --> @oo00spy00oo commented on GitHub (Mar 26, 2025): > @oo00spy00oo > > To access you have to add your domain name. > > Replace, > hoppscotch.example.com with **hoppscotch.yourdomainname.com** > hoppscotch-admin.example.com with **hoppscotch-admin.yourdomainname.com** > hoppscotch-backend.example.com with **hoppscotch-backend.yourdomainname.com** > > To attach the IP address to your domain. > `kubectl get ingress ` (this command will provide the IP address of you cluster) I know that, guy I replaced my real domain by example.com
kerem commented 2026-03-16 22:10:21 +03:00
Author
Owner
Copy link

@g3Bg2 commented on GitHub (Mar 26, 2025):

@oo00spy00oo

Have you applied?

# Install NGINX Ingress
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/do/deploy.yaml
<!-- gh-comment-id:2753532446 --> @g3Bg2 commented on GitHub (Mar 26, 2025): @oo00spy00oo Have you applied? ``` # Install NGINX Ingress kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/do/deploy.yaml ```
kerem commented 2026-03-16 22:10:26 +03:00
Author
Owner
Copy link

@oo00spy00oo commented on GitHub (Mar 26, 2025):

@oo00spy00oo

Have you applied?

# Install NGINX Ingress
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/do/deploy.yaml

@g3Bg2

As I mentioned in my Helm configuration, I use Traefik instead of Nginx, but no matter about the Ingress Controller, it still work. Focus on my highlight here: I also try to forward traffic from Kubernetes server to my local machine but have no available server to access

<!-- gh-comment-id:2753684504 --> @oo00spy00oo commented on GitHub (Mar 26, 2025): > [@oo00spy00oo](https://github.com/oo00spy00oo) > > Have you applied? > > ``` > # Install NGINX Ingress > kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/do/deploy.yaml > ``` @g3Bg2 As I mentioned in my Helm configuration, I use Traefik instead of Nginx, but no matter about the Ingress Controller, it still work. Focus on my highlight here: `I also try to forward traffic from Kubernetes server to my local machine but have no available server to access`
kerem commented 2026-03-16 22:10:31 +03:00
Author
Owner
Copy link

@g3Bg2 commented on GitHub (Mar 26, 2025):

@oo00spy00oo

I was able to replicate your problem on my end. When using the traefik

After some troubleshooting, I’ve resolved the issue where the Hoppscotch application couldn’t be accessed via the domain when using Traefik as the Ingress Controller. The root cause was that Traefik wasn’t installed in the cluster, which meant there was no Ingress Controller to route external traffic to the hoppscotch-community service

  • Ran kubectl get pods -n traefik and kubectl get svc -n traefik, both returned "No resources found in traefik namespace," confirming Traefik wasn’t deployed.
  • Confirmed the Hoppscotch app was running fine internally (hoppscotch-community-5c5cfdd6c6-lwfpx pod was Running and service hoppscotch-community was up with ClusterIP), but it wasn’t accessible externally without an Ingress Controller.

Installed Traefik
Used Helm to install Traefik, which is a clean and manageable approach:

helm repo add traefik https://helm.traefik.io/traefik
helm repo update
helm install traefik traefik/traefik --namespace traefik --create-namespace

Verified Traefik deployment:

kubectl get pods -n traefik
kubectl get svc -n traefik

This showed a Traefik pod running and a LoadBalancer service with an EXTERNAL-IP (e.g., 203.0.113.10), indicating Traefik was now exposed externally.

Note: Remove this line(kubernetes.io/ingress.class: nginx) from ingress.yaml file. If you are using traefik.

<!-- gh-comment-id:2754041501 --> @g3Bg2 commented on GitHub (Mar 26, 2025): @oo00spy00oo I was able to replicate your problem on my end. When using the **traefik** After some troubleshooting, I’ve resolved the issue where the Hoppscotch application couldn’t be accessed via the domain when using Traefik as the Ingress Controller. The root cause was that Traefik wasn’t installed in the cluster, which meant there was no Ingress Controller to route external traffic to the hoppscotch-community service - Ran `kubectl get pods -n traefik `and `kubectl get svc -n traefik`, both returned "No resources found in traefik namespace," confirming Traefik wasn’t deployed. - Confirmed the Hoppscotch app was running fine internally (hoppscotch-community-5c5cfdd6c6-lwfpx pod was Running and service hoppscotch-community was up with ClusterIP), but it wasn’t accessible externally without an Ingress Controller. Installed Traefik Used Helm to install Traefik, which is a clean and manageable approach: ``` helm repo add traefik https://helm.traefik.io/traefik helm repo update helm install traefik traefik/traefik --namespace traefik --create-namespace ``` Verified Traefik deployment: ``` kubectl get pods -n traefik kubectl get svc -n traefik ``` This showed a Traefik pod running and a LoadBalancer service with an EXTERNAL-IP (e.g., 203.0.113.10), indicating Traefik was now exposed externally. **Note**: Remove this line(kubernetes.io/ingress.class: nginx) from ingress.yaml file. If you are using traefik.
kerem commented 2026-03-16 22:10:37 +03:00
Author
Owner
Copy link

@oo00spy00oo commented on GitHub (Mar 26, 2025):

@oo00spy00oo

I was able to replicate your problem on my end. When using the traefik

After some troubleshooting, I’ve resolved the issue where the Hoppscotch application couldn’t be accessed via the domain when using Traefik as the Ingress Controller. The root cause was that Traefik wasn’t installed in the cluster, which meant there was no Ingress Controller to route external traffic to the hoppscotch-community service

  • Ran kubectl get pods -n traefik and kubectl get svc -n traefik, both returned "No resources found in traefik namespace," confirming Traefik wasn’t deployed.
  • Confirmed the Hoppscotch app was running fine internally (hoppscotch-community-5c5cfdd6c6-lwfpx pod was Running and service hoppscotch-community was up with ClusterIP), but it wasn’t accessible externally without an Ingress Controller.

Installed Traefik Used Helm to install Traefik, which is a clean and manageable approach:

helm repo add traefik https://helm.traefik.io/traefik
helm repo update
helm install traefik traefik/traefik --namespace traefik --create-namespace

Verified Traefik deployment:

kubectl get pods -n traefik
kubectl get svc -n traefik

This showed a Traefik pod running and a LoadBalancer service with an EXTERNAL-IP (e.g., 203.0.113.10), indicating Traefik was now exposed externally.

Note: Remove this line(kubernetes.io/ingress.class: nginx) from ingress.yaml file. If you are using traefik.

@g3Bg2 Many thanks, but this is not the main point of this issue.

After reviewing the whole helm charts source, I found this:

# Service configuration
service:
  apiVersion: v1
  name: hoppscotch-community
  app: hoppscotch-community

It meant in the helm chart the name is fixed with hoppscotch-community.

Solution 1: The install command must change from helm install community-hoppscotch ./charts/shc -f values.yaml -n hoppscotch to helm install hoppscotch ./charts/shc -f values.yaml -n hoppscotch

Solution 2: If you are installing with the name differrent from hoppscotch (eg: community-hoppscotch), you must change the section service in values.yaml with format: $releaseName-community.

Eg:

service:
  name: community-hoppscotch-community
  app: community-hoppscotch-community
<!-- gh-comment-id:2754505971 --> @oo00spy00oo commented on GitHub (Mar 26, 2025): > [@oo00spy00oo](https://github.com/oo00spy00oo) > > I was able to replicate your problem on my end. When using the **traefik** > > After some troubleshooting, I’ve resolved the issue where the Hoppscotch application couldn’t be accessed via the domain when using Traefik as the Ingress Controller. The root cause was that Traefik wasn’t installed in the cluster, which meant there was no Ingress Controller to route external traffic to the hoppscotch-community service > > * Ran `kubectl get pods -n traefik `and `kubectl get svc -n traefik`, both returned "No resources found in traefik namespace," confirming Traefik wasn’t deployed. > * Confirmed the Hoppscotch app was running fine internally (hoppscotch-community-5c5cfdd6c6-lwfpx pod was Running and service hoppscotch-community was up with ClusterIP), but it wasn’t accessible externally without an Ingress Controller. > > Installed Traefik Used Helm to install Traefik, which is a clean and manageable approach: > > ``` > helm repo add traefik https://helm.traefik.io/traefik > helm repo update > helm install traefik traefik/traefik --namespace traefik --create-namespace > ``` > > Verified Traefik deployment: > > ``` > kubectl get pods -n traefik > kubectl get svc -n traefik > ``` > > This showed a Traefik pod running and a LoadBalancer service with an EXTERNAL-IP (e.g., 203.0.113.10), indicating Traefik was now exposed externally. > > **Note**: Remove this line(kubernetes.io/ingress.class: nginx) from ingress.yaml file. If you are using traefik. @g3Bg2 Many thanks, but this is not the main point of this issue. After reviewing the whole helm charts source, I found this: ```yaml # Service configuration service: apiVersion: v1 name: hoppscotch-community app: hoppscotch-community ``` It meant in the helm chart the name is fixed with `hoppscotch-community`. Solution 1: The install command must change from `helm install community-hoppscotch ./charts/shc -f values.yaml -n hoppscotch` to `helm install hoppscotch ./charts/shc -f values.yaml -n hoppscotch` Solution 2: If you are installing with the name differrent from `hoppscotch` (eg: community-hoppscotch), you must change the section `service` in `values.yaml` with format: `$releaseName-community`. Eg: ```yaml service: name: community-hoppscotch-community app: community-hoppscotch-community ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
chore/security-fix-2026-4-0
next
fix/mockserver-env-set-url-priority
feat/rest-gql-merge
refactor/workspaces
fix/onboarding-mass-assignment
desktop-settings-phase-0-schema-bridge-shell
patch
test-webhook
pr/johnan319/5745
tembo/optimize-performance-db-queries
add-claude-github-actions-1772782423108
fix/code-scanning-103
fix/mock-server-example-endpoint-match-v2
fix/rate-limit-on-health-route
hotfix/api-doc-collection-deletetion
cd-test
fix/mock-server-backend-followup
chore/code-scanning-52
chore/verion-addition-check
nested-migrations
scripting-system-updates-worker-setup
scripting-system-updates
pr/shipko/4367
ci-test
feat/user-delete-condition
feat/user-workspace-stats-api
chore/collection-export-addition
fix/import-file-size-limit-flow
feat/dashboard-common
feat/sort-environment-alphabetically
feat/infra-config-encryption
refactor/team
feat/collection-duplicationn
feat/secure-cookies-toggle
pr/pavog/4195
pr/pavog/4196
test/patch-demo
feat/native-interceptor-updates
pr/AndrewBastin/4111
feat/user-last-active-on
fix/codemirror-large-text-scroll-bug
fix/precision-lost-beautify
fix/env-diff-test-schema-error
fix/email-case-sensitive
release/2024.3.3
refactor/workspace-login-conversion
feat/node-apline-version-upgrade
feat/seed
release/2024.3.2
fix/sh-email-handlebar-issue
feat/app-experiment-animation
release/2024.3.1
release/2024.3.0
pr/jamesgeorge007/3937
experiment/deploychan
feat/github-enterprise-auth
refactor/collection-search-query
hotfix/infra-config-reset-bug
fix/secret-var-bug
hotfix/full-text-search
hotfix/request-variable-version-syncing
feat/request-variable
feat/server-config-additional-properties
pr/JoelJacobStephen/3845
release/2023.12.6
fix/safari-codemirror-perf-bug
release/2023.12.5
release/2023.12.4
fix/secret-env-bugs-tooltip
release/2023.12.3
fix/shared-request-bug
fix/disable-context-menu-option
release/2023.12.2
release/2023.12.1
fix/shared-request-bugs
release/2023.12.0
fix/gql-history-schema
fix/actions-not-working-without-sidebar
pr/jamesgeorge007/3665
chore/desktop-app-corrections
fix/auth-headers-in-coll
fix/embed-url
improve/placeholder
add-realtime-logos
feat/shared-request-embeds
feat/collection-headers
revamp/header
release/2023.8.4
refactor/interceptor-error-display
feat/subpath-based-access
release/2023.8.3
feat/shared-requests
feat/desktop
fix/nodemailer-templates-issue
feature/upgrade-graphql-ws
fix/graphql-crashing
fix/set-environments-when-no-env-selected
refactor/pre-prisma-bump-setup
release/2023.8.2
pr/danitherex/3216
perf/raw-db-query
release/2023.8.1
revert-3348-perf/reduce-backend-calls
fix/incorrect-tab-count-close-all-tab
fix/duplicate-tab-bug
release/2023.8.0
hotfix/fetch-shortcode
fix/tab-right-click-rename-bug
chore/docker-fixes
pr/JoelJacobStephen/3178
feat/fe-accessible-auth-provider-env
feat-cherry-pick/conditional-auth-select
feat/conditional-auth-select
release/2023.4.8
fix/generate-sitemap-issue
test/backend-test-case
refactor/team-invitation
pr/AndrewBastin/3171
release/2023.4.7
fix/duplicate-team-invite
fix/unified-bg-color-coll-tree
fix/shortcode-screen-stuck
release/2023.4.6
revert-3117-patch-3
fix/env-selector-bg
fix/db-url
release/2023.4.4
fix/sync-popup-bug
fix/team-env-set-test
chore/wss-to-ws-on-env
fix/prettify-xml-response
feat/db-volume-addition
feat/env-selector-tabs-ui
bug/broken-env
release/2023.4.2
fix/switch-workspace-env-bug
fix/magic-link
fix/cookie-handler
HPS-OSS-1
staging
revert/auth-issue
feat/export-env
refactor/commons
reference/path-variables
orphan-pr/2243
feat/realtime-search
fix/save-override
refactor/strategies
feat/embeds
bug/withDefaults
feat/show-keys
refactor/toast
2026.3.1
2026.3.0
2026.2.1
2026.2.0
2026.1.1
2026.1.0
2025.12.1
2025.12.0
2025.11.2
2025.11.1
2025.11.0
2025.10.1
2025.10.0
2025.9.2
2025.9.1
2025.9.0
2025.8.1
2025.8.0
2025.7.1
2025.7.0
2025.6.1
2025.6.0
2025.5.4
2025.5.3
2025.5.2
2025.5.1
2025.5.0
2025.4.2
2025.4.1
2025.4.0
2025.3.2
2025.3.1
2025.3.0
2025.2.3
2025.2.2
2025.2.1
2025.2.0
2025.1.1
2025.1.0
2024.12.2
2024.12.1
2024.12.0
2024.11.0
2024.10.2
2024.10.1
2024.10.0
2024.9.3
2024.9.2
2024.9.1
2024.9.0
2024.8.3
2024.8.2
2024.8.1
2024.8.0
2024.7.2
2024.7.1
2024.7.0
2024.6.1
2024.6.0
2024.3.4
2024.3.3
2024.3.2
2024.3.1
2024.3.0
2023.12.6
2023.12.5
2023.12.4
2023.12.3
2023.12.2
2023.12.1
2023.12.0
2023.8.4
2023.8.3
2023.8.2
2023.8.1
2023.8.0
2023.4.8
2023.4.7
2023.4.6
2023.4.5
2023.4.4
2023.4.3
2023.4.2
2023.4.1
2023.4.0
v3.0.1
v3.0.0
v2.2.1
v2.2.0
v2.1.0
v2.0.0
v1.12.0
v1.10.0
v1.9.9
v1.9.7
v1.9.5
v1.9.0
v1.8.0
v1.5.0
v1.0.0
v0.1.0
Labels
Clear labels   
CodeDay

   
a11y

   
browser limited

   
bug

   
bug fix

   
cli

   
core

   
critical

   
design

   
desktop

   
discussion

   
docker

   
documentation

   
duplicate

   
enterprise

   
feature

   
feature

   
fosshack

   
future

   
good first issue

   
hacktoberfest

   
help wanted

   
i18n

   
invalid

   
major

   
minor

   
need information

   
need testing

   
not applicable to hoppscotch

   
not reproducible

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
refactor

   
resolved

   
sandbox

   
self-host

   
spam

   
stale

   
testmu

   
wip

   
wont fix
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#1866
No description provided.