starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #3331] [bug]: Collections view does not refresh after creating a collection or adding a new request #1109

New issue

Open

opened 2026-03-16 18:36:31 +03:00 by kerem · 12 comments

kerem commented

2026-03-16 18:36:31 +03:00

Owner

Originally created by @lovaszvencel on GitHub (Sep 8, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3331

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I switch the workspace from my workspace to any other team workspace the collection view top refreshing it after adding items into it.

For example, if I create a new collection and save it it does not appear in the list (list remains empty). I expect to see the newly created collection in the list (as works in my workspace). After I refresh the page the newly created collection appears on the list.
Other example, if I create a new request and save it it does not appear in the list (list contains the collection only). I expect to see the newly created request in the list (as works in my workspace). After I refresh the page the newly created request appears on the list.

Steps to reproduce

Create a new team
Create a new collection
Save the dialog
Actual result: Collection list is empty
Expected result: Newly created collection is appear

Environment

Production

Version

Self-hosted

Originally created by @lovaszvencel on GitHub (Sep 8, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3331 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I switch the workspace from my workspace to any other team workspace the collection view top refreshing it after adding items into it. For example, if I create a new collection and save it it does not appear in the list (list remains empty). I expect to see the newly created collection in the list (as works in my workspace). After I refresh the page the newly created collection appears on the list. Other example, if I create a new request and save it it does not appear in the list (list contains the collection only). I expect to see the newly created request in the list (as works in my workspace). After I refresh the page the newly created request appears on the list. ### Steps to reproduce 1. Create a new team 2. Create a new collection 3. Save the dialog Actual result: Collection list is empty Expected result: Newly created collection is appear ### Environment Production ### Version Self-hosted

kerem added the

bug

need testing

labels

2026-03-16 18:36:31 +03:00

kerem commented

2026-03-16 18:36:42 +03:00

Author

Owner

@frnk01 commented on GitHub (Sep 13, 2023):

Same for me. Need to refresh manually after performing actions. Self hosted.

@frnk01 commented on GitHub (Sep 13, 2023): Same for me. Need to refresh manually after performing actions. Self hosted.

kerem commented

2026-03-16 18:36:47 +03:00

Author

Owner

@JamesSFL commented on GitHub (Nov 17, 2023):

Same here. Occurs in case of team workspace. Self hosted too.

@JamesSFL commented on GitHub (Nov 17, 2023): Same here. Occurs in case of team workspace. Self hosted too.

kerem commented

2026-03-16 18:36:52 +03:00

Author

Owner

@KatyaGolyagina commented on GitHub (Feb 13, 2024):

Same on https://hoppscotch.io/ not only Self hosted.
We're really looking forward to the fix! 😔🙏

@KatyaGolyagina commented on GitHub (Feb 13, 2024): Same on https://hoppscotch.io/ not only Self hosted. We're really looking forward to the fix! 😔🙏

kerem commented

2026-03-16 18:36:57 +03:00

Author

Owner

@buderjoh commented on GitHub (Mar 5, 2024):

I think this might be a configuration issue?

https://github.com/hoppscotch/hoppscotch/issues/3587#issuecomment-1845447776

If its running under https -> VITE_BACKEND_WS_URL=wss://localhost:3170/graphql works for me
and i think it would work the other way around for http -> VITE_BACKEND_WS_URL=ws://localhost:3170/graphql

Nevertheless if you do it with your local workspace there is still this issue: https://github.com/hoppscotch/hoppscotch/issues/3208

@buderjoh commented on GitHub (Mar 5, 2024): I think this might be a configuration issue? https://github.com/hoppscotch/hoppscotch/issues/3587#issuecomment-1845447776 If its running under https -> VITE_BACKEND_WS_URL=**wss**://localhost:3170/graphql works for me and i think it would work the other way around for http -> VITE_BACKEND_WS_URL=**ws**://localhost:3170/graphql Nevertheless if you do it with your local workspace there is still this issue: https://github.com/hoppscotch/hoppscotch/issues/3208

kerem commented

2026-03-16 18:37:02 +03:00

Author

Owner

@KatyaGolyagina commented on GitHub (Apr 18, 2024):

I think this might be a configuration issue?

#3587 (comment)

If its running under https -> VITE_BACKEND_WS_URL=wss://localhost:3170/graphql works for me and i think it would work the other way around for http -> VITE_BACKEND_WS_URL=ws://localhost:3170/graphql

Nevertheless if you do it with your local workspace there is still this issue: #3208

doesn't work

@KatyaGolyagina commented on GitHub (Apr 18, 2024): > I think this might be a configuration issue? > > [#3587 (comment)](https://github.com/hoppscotch/hoppscotch/issues/3587#issuecomment-1845447776) > > If its running under https -> VITE_BACKEND_WS_URL=**wss**://localhost:3170/graphql works for me and i think it would work the other way around for http -> VITE_BACKEND_WS_URL=**ws**://localhost:3170/graphql > > Nevertheless if you do it with your local workspace there is still this issue: #3208 doesn't work

kerem commented

2026-03-16 18:37:07 +03:00

Author

Owner

@AlirezaAbsolution commented on GitHub (Sep 2, 2024):

Hi, i have same problem. I use hoppscotch as reverse proxy for mine. The problem is wss if anyone using reverse proxy add this lines in location / in nginx and problem will be fixed.

location / {
        proxy_pass http://x.x.x.x:3170/;
        include proxy_params;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
    }

#Solved

@AlirezaAbsolution commented on GitHub (Sep 2, 2024): Hi, i have same problem. I use hoppscotch as reverse proxy for mine. The problem is wss if anyone using reverse proxy add this lines in location / in nginx and problem will be fixed. ``` location / { proxy_pass http://x.x.x.x:3170/; include proxy_params; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } ``` #Solved

kerem commented

2026-03-16 18:37:12 +03:00

Author

Owner

@MrNoize commented on GitHub (Oct 15, 2024):

Hi. If you deploy hoppscotch on k8s cluster add this to annotation of ingress(snippets should be enabled):


  annotations:
    nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
    nginx.ingress.kubernetes.io/server-snippets: |
      location / {
        proxy_set_header Upgrade $http_upgrade;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-Host $http_host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $host;
        proxy_set_header Connection "upgrade";
        proxy_cache_bypass $http_upgrade;
        }

(Probably you shouldn't set headers for / location, try /graphql)

@MrNoize commented on GitHub (Oct 15, 2024): Hi. If you deploy hoppscotch on k8s cluster add this to annotation of ingress(snippets should be enabled): ``` annotations: nginx.ingress.kubernetes.io/proxy-read-timeout: "3600" nginx.ingress.kubernetes.io/proxy-send-timeout: "3600" nginx.ingress.kubernetes.io/server-snippets: | location / { proxy_set_header Upgrade $http_upgrade; proxy_http_version 1.1; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header Host $host; proxy_set_header Connection "upgrade"; proxy_cache_bypass $http_upgrade; } ``` (Probably you shouldn't set headers for / location, try /graphql)

kerem commented

2026-03-16 18:37:17 +03:00

Author

Owner

@Systemko commented on GitHub (Oct 30, 2024):

I can confirm that this is a configuration issue. If you are running your hoppscotch instance under https, you have to use secure web socket connection in VITE_BACKEND_WS_URL(wss not ws). But there is still an issue that we've stumbled upon. You really need to delete cookies from your browser because hoppscotch graphql backend path is cached.
P.S. To delete cookies in google chrome you need to proceed to chrome://settings/content/all, find your hoppscotch site address and click the bin icon.

@Systemko commented on GitHub (Oct 30, 2024): I can confirm that this is a configuration issue. If you are running your hoppscotch instance under https, you have to use secure web socket connection in VITE_BACKEND_WS_URL(**wss** not ws). But there is still an issue that we've stumbled upon. You really need to delete cookies from your browser because hoppscotch graphql backend path is cached. P.S. To delete cookies in google chrome you need to proceed to chrome://settings/content/all, find your hoppscotch site address and click the bin icon.

kerem commented

2026-03-16 18:37:23 +03:00

Author

Owner

@am071092 commented on GitHub (Jan 8, 2025):

Hi, I am facing the same issue as above, even after using secure web connection via wss. Is there a fix for this?

@am071092 commented on GitHub (Jan 8, 2025): Hi, I am facing the same issue as above, even after using secure web connection via wss. Is there a fix for this?

kerem commented

2026-03-16 18:37:28 +03:00

Author

Owner

@Systemko commented on GitHub (Jan 9, 2025):

Hi, I am facing the same issue as above, even after using secure web connection via wss. Is there a fix for this?

Did you clear hoppscotch cache in your browser as I had mentioned above?

@Systemko commented on GitHub (Jan 9, 2025): > Hi, I am facing the same issue as above, even after using secure web connection via wss. Is there a fix for this? Did you clear hoppscotch cache in your browser as I had mentioned above?

kerem commented

2026-03-16 18:37:33 +03:00

Author

Owner

@QuentinDEME97 commented on GitHub (Jul 3, 2025):

Using Traefik, the only thing I changed is:

urls:
      base: "https://app.hoppscotch"
      shortcode: "https://app.hoppscotch."
      admin: "https://admin.hoppscotch"
      backend:
        gql: "https://backend.hoppscotch/graphql"
        ws: "wss://backend.hoppscotch/graphql" <-- THIS from ws: to wss:
        api: "https://backend.hoppscotch./v1"
      redirect: "https://app.hoppscotch."
      whitelistedOrigins: "https://backend.hoppscotch.,https://app.hoppscotch.,https://admin.hoppscotch."

@QuentinDEME97 commented on GitHub (Jul 3, 2025): Using Traefik, the only thing I changed is: ``` urls: base: "https://app.hoppscotch" shortcode: "https://app.hoppscotch." admin: "https://admin.hoppscotch" backend: gql: "https://backend.hoppscotch/graphql" ws: "wss://backend.hoppscotch/graphql" <-- THIS from ws: to wss: api: "https://backend.hoppscotch./v1" redirect: "https://app.hoppscotch." whitelistedOrigins: "https://backend.hoppscotch.,https://app.hoppscotch.,https://admin.hoppscotch." ```

kerem commented

2026-03-16 18:37:38 +03:00

Author

Owner

@Moundlen commented on GitHub (Mar 13, 2026):

Hi,

I can confirm the bug is still there but only on desktop client. The web client everything updates properly but on desktop some updates are not refreshed especially duplicating a route or creating a new directory.

Makes it quite hard to properly work on it. And yes wss is properly configured no issue on the webapp.

@Moundlen commented on GitHub (Mar 13, 2026): Hi, I can confirm the bug is still there but only on desktop client. The web client everything updates properly but on desktop some updates are not refreshed especially duplicating a route or creating a new directory. Makes it quite hard to properly work on it. And yes wss is properly configured no issue on the webapp.

kerem referenced this issue

2026-03-17 00:43:02 +03:00

[PR #1109] [MERGED] Typos in spanish translation #3068