starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #3128] [bug]: login server internal error #1032

New issue

Closed

opened 2026-03-16 18:12:21 +03:00 by kerem · 7 comments

kerem commented

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

Owner

Originally created by @talenta-eg on GitHub (Jun 9, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3128

Originally assigned to: @balub on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

Steps to reproduce

I try to login via email but i face this an error , Any Suggestions ?

Environment

Production

Version

SelfHosted

Originally created by @talenta-eg on GitHub (Jun 9, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3128 Originally assigned to: @balub on GitHub. ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior <img width="1336" alt="Screenshot 2023-06-09 at 7 16 44 AM" src="https://github.com/hoppscotch/hoppscotch/assets/4216438/e82c8375-0ee8-49e1-9c24-78c2bd938388"> ### Steps to reproduce I try to login via email but i face this an error , Any Suggestions ? ### Environment Production ### Version SelfHosted

kerem

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

closed this issue
added the
bug

need testing

self-host
labels

kerem commented

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

Author

Owner

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

Did you run the migration? If not please do that. It should fix this issue.

@amishsthapit commented on GitHub (Jun 9, 2023): Did you run the migration? If not please do that. It should fix this issue.

kerem commented

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

Author

Owner

@talenta-eg commented on GitHub (Jun 9, 2023):

@amishsthapit , Awesome right now working i can send an email
but when open email and click to login i face the following

@talenta-eg commented on GitHub (Jun 9, 2023): @amishsthapit , Awesome right now working i can send an email but when open email and click to login i face the following <img width="1436" alt="Screenshot 2023-06-09 at 4 05 10 PM" src="https://github.com/hoppscotch/hoppscotch/assets/4216438/99eaa3a3-0a4f-48c6-b694-5e5459ba23f8">

kerem commented

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

Author

Owner

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

@talenta-eg The error indicates that you have used to sign-in to another device using a magic-link generated from another device, we do not allow for that to happen.

@balub commented on GitHub (Jun 10, 2023): @talenta-eg The error indicates that you have used to sign-in to another device using a magic-link generated from another device, we do not allow for that to happen.

kerem commented

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

Author

Owner

@talenta-eg commented on GitHub (Jun 10, 2023):

@balub First thanks for reply , i know the error content but i have sign-in from these device with same browser many of times but still issues showing i do not know what i cane do to pass this error

Can you help please ?

@talenta-eg commented on GitHub (Jun 10, 2023): @balub First thanks for reply , i know the error content but i have sign-in from these device with same browser many of times but still issues showing **i do not know what i cane do to pass this error** Can you help please ?

kerem commented

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

Author

Owner

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

@talenta-eg The device identifier token is saved in your browser's local storage once you initiate the magic-link auth flow, do you by chance have any extension etc that can prevent that from happening?

@balub commented on GitHub (Jun 15, 2023): @talenta-eg The device identifier token is saved in your browser's local storage once you initiate the magic-link auth flow, do you by chance have any extension etc that can prevent that from happening?

kerem commented

2026-03-16 18:13:03 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Sep 6, 2023):

Closing this issue due to inactivity. If you still face this in 2023.8.0, please do reopen.

@AndrewBastin commented on GitHub (Sep 6, 2023): Closing this issue due to inactivity. If you still face this in 2023.8.0, please do reopen.

kerem commented

2026-03-16 18:13:08 +03:00

Author

Owner

@krystalcode commented on GitHub (May 9, 2025):

@balub I have the same issue running the latest (as of today) official AIO container. I do see the deviceIdentifier and emailForSignIn properties properly stored in local storage. Still getting the "Device identifier not found ..." error.

@krystalcode commented on GitHub (May 9, 2025): @balub I have the same issue running the latest (as of today) official AIO container. I do see the `deviceIdentifier` and `emailForSignIn` properties properly stored in local storage. Still getting the "Device identifier not found ..." error.