starred/hoppscotch

Fork 0

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

[GH-ISSUE #2035] [bug]: Teams:: Self hosted instance sending team add request to api.hoppscotch.io/graphql and fails #663

New issue

Closed

opened 2026-03-16 16:34:45 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 16:34:45 +03:00

Owner

Originally created by @ziaulrehman40 on GitHub (Dec 21, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2035

Is there an existing issue for this?

I have searched the existing issues

Current behavior

On self hosted custom instance, create team request is sent to api.hoppscotch.io/graphql with payload:

{"query":"mutation CreateTeam($name: String!) {\n  createTeam(name: $name) {\n    id\n    name\n    members {\n      membershipID\n      role\n      user {\n        uid\n        displayName\n        email\n        photoURL\n        __typename\n      }\n      __typename\n    }\n    myRole\n    ownersCount\n    editorsCount\n    viewersCount\n    __typename\n  }\n}\n","operationName":"CreateTeam","variables":{"name":"Team12345"}}

Which fails and gives:

{"errors":[{"message":"auth/fail","locations":[{"line":2,"column":3}],"path":["createTeam"],"extensions":{"code":"INTERNAL_SERVER_ERROR"}}],"data":null}

Steps to reproduce

Configure a custom instance, following official guides, setup all new keys in .env, build and deploy
Try to create a new team, no error pops on forntend
Inspecting the network calls i see above behavior

Environment

Production

Version

Self-hosted

Originally created by @ziaulrehman40 on GitHub (Dec 21, 2021). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2035 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior On self hosted custom instance, create team request is sent to `api.hoppscotch.io/graphql` with payload: ``` {"query":"mutation CreateTeam($name: String!) {\n createTeam(name: $name) {\n id\n name\n members {\n membershipID\n role\n user {\n uid\n displayName\n email\n photoURL\n __typename\n }\n __typename\n }\n myRole\n ownersCount\n editorsCount\n viewersCount\n __typename\n }\n}\n","operationName":"CreateTeam","variables":{"name":"Team12345"}} ``` Which fails and gives: ``` {"errors":[{"message":"auth/fail","locations":[{"line":2,"column":3}],"path":["createTeam"],"extensions":{"code":"INTERNAL_SERVER_ERROR"}}],"data":null} ``` ### Steps to reproduce 1. Configure a custom instance, following official guides, setup all new keys in `.env`, build and deploy 2. Try to create a new team, no error pops on forntend 3. Inspecting the network calls i see above behavior ### Environment Production ### Version Self-hosted

kerem

2026-03-16 16:34:45 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 16:35:02 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Dec 21, 2021):

Hi there,

Teams currently is only available for users of the official Hoppscotch instance (https://hoppscotch.io). We are working on a fully self hosted solution but it's further down the line.

@AndrewBastin commented on GitHub (Dec 21, 2021): Hi there, Teams currently is only available for users of the official Hoppscotch instance ([https://hoppscotch.io](https://hoppscotch.io)). We are working on a fully self hosted solution but it's further down the line.

kerem commented

2026-03-16 16:35:07 +03:00

Author

Owner

@ziaulrehman40 commented on GitHub (Dec 22, 2021):

Thanks @AndrewBastin , is there any issue or PR i can track, or anyway i can help speed this process up.
BTW, only reason we are not using official instance is to avoid putting a lot of load on it, and we don't know if there are any limits on usage there, as we intend to use it extensively. So if you can help me understand this aspect as well, would be great.

Thanks.

@ziaulrehman40 commented on GitHub (Dec 22, 2021): Thanks @AndrewBastin , is there any issue or PR i can track, or anyway i can help speed this process up. BTW, only reason we are not using official instance is to avoid putting a lot of load on it, and we don't know if there are any limits on usage there, as we intend to use it extensively. So if you can help me understand this aspect as well, would be great. Thanks.

kerem commented

2026-03-16 16:35:12 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Dec 22, 2021):

@ziaulrehman40 the issue is tracked here #1817.

I don't exactly get by what you meant by not putting more load on it. What do you mean by using it extensively ?

@AndrewBastin commented on GitHub (Dec 22, 2021): @ziaulrehman40 the issue is tracked here #1817. I don't exactly get by what you meant by not putting more load on it. What do you mean by using it extensively ?

kerem commented

2026-03-16 16:35:17 +03:00

Author

Owner

@ziaulrehman40 commented on GitHub (Dec 22, 2021):

@AndrewBastin like collection size limits, users in a team limits etc. As we have huge collections we would like to import from postman to hoppscotch.

@ziaulrehman40 commented on GitHub (Dec 22, 2021): @AndrewBastin like collection size limits, users in a team limits etc. As we have huge collections we would like to import from postman to hoppscotch.

kerem referenced this issue

2026-03-17 00:27:17 +03:00

[PR #663] [MERGED] Feature/mqtt #2776