Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

While connecting to leather wallet it's giving me private key length is not valid (it only happens on react build hosted on server,works fine local ) #366

Open
HEGADE opened this issue Feb 15, 2024 · 1 comment
Assignees

Comments

@HEGADE
Copy link

HEGADE commented Feb 15, 2024

*Describe the bug

Environment: Development environment deployed using Docker on a Digital Ocean droplet. Frontend is a React build.

Expected Behavior: When connecting the wallet to the frontend using stacks.js , the connection should be successful, regardless of whether the frontend is running locally or served from the server itself.

Actual Behavior:
Local Frontend: wallet gets connected successfully

Server-Hosted Frontend: fails with the error message " Error during auth request Error: Improperly formatted private-key. Private-key byte length should be 32 or 33. Length provided: 390".

Request for Assistance
I'd appreciate any help or insights into further troubleshooting this "private key has no valid length" error that specifically occurs when running the React build from the server.

image

Desktop (please complete the following information):

  • Browser [chrome]
  • Version [Latest]
@github-project-automation github-project-automation bot moved this to 🆕 New in DevTools Feb 15, 2024
@HEGADE HEGADE changed the title Leather wallet is giving some error cooccurred msg when deploying contract using openDeploy method of stacks js While connecting to leather wallet it's giving me private key length is not valid (it only happens on react build hosted on server,works fine local ) Feb 16, 2024
@janniks
Copy link
Collaborator

janniks commented Feb 26, 2024

This seems to have been fixed when switching http to https for the site hosting Connect.
This issue will be used to investigate more and figure out if it's possible to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants