starred/hoppscotch

Fork 0

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

[GH-ISSUE #3090] [bug]: Team invitation is not working #1014

New issue

Closed

opened 2026-03-16 18:04:41 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 18:04:41 +03:00

Owner

Originally created by @sugureshs on GitHub (May 29, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3090

Originally assigned to: @balub on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I invite the user to a team user should be able to join the team with the invitation (sent over a mail), but the user is not able to join the team.

Note:
This base URL is replaced with VITE_BASE_URL

Steps to reproduce

Create a team (if not already exist).
Invite the user to a team.
User tries to join the team.
"Something went wrong" is displayed.

Environment

Production

Version

Self-hosted

Originally created by @sugureshs on GitHub (May 29, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3090 Originally assigned to: @balub on GitHub. ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I invite the user to a team user should be able to join the team with the invitation (sent over a mail), but the user is not able to join the team. <img width="1208" alt="Screenshot 2023-05-29 at 20 15 30" src="https://github.com/hoppscotch/hoppscotch/assets/134737239/ee07c658-3158-4e66-b086-0afbdb43b328"> <img width="1680" alt="Screenshot 2023-05-29 at 20 15 55" src="https://github.com/hoppscotch/hoppscotch/assets/134737239/526881c4-1736-49e9-955d-c6ef8cac9bdb"> Note: [This](https://github.com/hoppscotch/hoppscotch/blob/d6c840011616317ba98f143da61b8f38bc1f5fc2/packages/hoppscotch-backend/src/team-invitation/team-invitation.service.ts#L129) base URL is replaced with `VITE_BASE_URL` ### Steps to reproduce 1. Create a team (if not already exist). 2. Invite the user to a team. 3. User tries to join the team. 4. "Something went wrong" is displayed. ### Environment Production ### Version Self-hosted

kerem

2026-03-16 18:04:41 +03:00

closed this issue
added the
bug

need testing

self-host
labels

kerem commented

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

Author

Owner

@balub commented on GitHub (Jun 5, 2023):

@sugureshs is your instance hosted over HTTPS, we use HTTP, secure cookies and the may not function if used over a normal HTTP network.

@balub commented on GitHub (Jun 5, 2023): @sugureshs is your instance hosted over `HTTPS`, we use `HTTP, secure` cookies and the may not function if used over a normal `HTTP` network.

kerem commented

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

Author

Owner

@amishsthapit commented on GitHub (Jun 9, 2023):

Can you please elaborate on this? I have put HTTP, Secure Cookies in reverse proxy config also. But the feature is still not working. Is there any other configuration I need to be aware about?

@amishsthapit commented on GitHub (Jun 9, 2023): Can you please elaborate on this? I have put HTTP, Secure Cookies in reverse proxy config also. But the feature is still not working. Is there any other configuration I need to be aware about?

kerem commented

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

Author

Owner

@balub commented on GitHub (Jun 10, 2023):

@amishsthapit Hoppscotch uses cookie based auth to authorize a user in the backend, since our cookies are secure cookies unless the network is HTTPs the browser does not save the cookies and as such even after successfully logging in we are unable to do anything else because we are not able to authorize you in the BE.

@balub commented on GitHub (Jun 10, 2023): @amishsthapit Hoppscotch uses cookie based auth to authorize a user in the backend, since our cookies are secure cookies unless the network is HTTPs the browser does not save the cookies and as such even after successfully logging in we are unable to do anything else because we are not able to authorize you in the BE.

kerem commented

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

Author

Owner

@sugureshs commented on GitHub (Jun 12, 2023):

@balub sorry for the late reply, yes all three services are deployed on k8s and is exposed to HTTP secure.

@sugureshs commented on GitHub (Jun 12, 2023): @balub sorry for the late reply, yes all three services are deployed on k8s and is exposed to HTTP secure.