sigit/sigit.io
6
2
Fork 0
Code Issues 41 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

Login Page - login with nip05 issue #143

New Issue
Open
opened 2024-08-15 13:05:31 +00:00 by enes · 4 comments
enes commented 2024-08-15 13:05:31 +00:00
Member
Copy Link

Using nip05 (an email) shows No relay found for nsecbunker error, even though network tab shows 200 OK from the domain and response includes names with hex.

Using nip05 (an email) shows `No relay found for nsecbunker` error, even though network tab shows 200 OK from the domain and response includes names with hex.
enes added the
Kind/Bug
Status
Need More Info
 labels 2024-08-15 13:05:31 +00:00
s commented 2024-08-19 07:54:22 +00:00
Owner
Copy Link

The response should also contain a nip46 obj. It must be missing from your nip05 address. Therefore you got the error.
See

The response should also contain a nip46 obj. It must be missing from your nip05 address. Therefore you got the error.[ See](https://git.nostrdev.com/sigit/sigit.io/src/commit/b8ba8d0ab49ee26eda25824361fde72974da84af/src/utils/nostr.ts#L111)
s commented 2024-08-19 08:02:49 +00:00
Owner
Copy Link

However, I got some other issues in the nip05 login. I got stuck after entering the password for my nsecbunker.

However, I got some other issues in the nip05 login. I got stuck after entering the password for my nsecbunker.
b commented 2024-08-19 08:05:11 +00:00
Owner
Copy Link

Maybe the error message can be more descriptive? Eg to tell the user what we are expecting to find in the .well-known/nostr.json ?

Maybe the error message can be more descriptive? Eg to tell the user what we are expecting to find in the .well-known/nostr.json ?
enes commented 2024-08-19 08:27:10 +00:00
Author
Member
Copy Link

Yes, and especially if user is non-technical or just started using nostr like me, the existing toast error doesn't help much.

Yes, and especially if user is non-technical or just started using nostr like me, the existing toast error doesn't help much.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sigit/sigit.io#143
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?