mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #3757] [bug]: I use email , but I am unable to log in #1305
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1305
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pigzhuzhu55 on GitHub (Jan 17, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3757
Is there an existing issue for this?
Current behavior
Steps to reproduce
When I logged in using email, I received a link in my webpage email. By clicking on the link, I was redirected to the page and did not successfully log in.
But I can see 2 account records in the database.
Environment
Production
Version
Self-hosted
@tungtepao commented on GitHub (Jan 19, 2024):
I may have had the same issue as you. i tracked with burp proxy,and found that the cookie of response from magic link was not saved. after Manual copying the two cookie value : access_token,refresh_token, hoppscotch show i am Logged in。
@balub commented on GitHub (Jan 25, 2024):
@pigzhuzhu55 Hoppscotch uses
HTTPSsecure cookies to authenticate itself with the backend because you are running Hoppscotch on just anHTTPnetwork even if you successfully log in the cookies ultimately won't be saved by the browser@TungTePao I believe this is the same reason for your end too.
@tungtepao commented on GitHub (Jan 29, 2024):
3ks!you are right. i solved with configured nginx as an https reverse proxy.
The latest docker image of backend does not expose 443 port, it's hard to think of does not support http.
@balub commented on GitHub (May 14, 2024):
Closing this issue, due to inactivity.