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

TX:ERROR Error: Response closed without headers on wallet connect #75

Open
beshup opened this issue Nov 16, 2021 · 1 comment
Open

TX:ERROR Error: Response closed without headers on wallet connect #75

beshup opened this issue Nov 16, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@beshup
Copy link

beshup commented Nov 16, 2021

I've configured my local dApp running on port 3000 to talk to the docker image running on port 8701. Ran into this error when attempting to login.

Screen Shot 2021-11-16 at 12 48 49 AM

I also noticed that the discovery.wallet config url is on port 3000. Confused as to why this is the case?

Screen Shot 2021-11-16 at 12 58 09 AM

@adhurjaty
Copy link

I'm having a similar issue. I'm running the following command

docker run -it \
    -p 8701:8701 \
    -e PORT=8701 \
    -e BASE_URL=http://localhost:8701 \
    -e FLOW_ACCESS_NODE=http://localhost:8888 \
    -e FLOW_ACCOUNT_KEY_ID=0 \
    -e FLOW_ACCOUNT_PRIVATE_KEY=b7196235f20dec86d231e2d303f6deed4dd2b5731a66c4d385a421b66d442ed4 \
    -e FLOW_ACCOUNT_PUBLIC_KEY=f25ec7df228b4b4c750c13d5236f7d5d870902dcad43030d5729ad04e9b5bb13e75e4e3357407e4f4ccdcf4cda30744ea203793b2b46cb1664b3c57022b3d4db \
    -e FLOW_INIT_ACCOUNTS=0 \
    -e FLOW_ACCOUNT_ADDRESS=0xf3fcd2c1a78f5eee \
    -e FLOW_AVATAR_URL=https://avatars.onflow.org/avatar/ \
    -e CONTRACT_FUNGIBLE_TOKEN=0xee82856bf20e2aa6 \
    -e CONTRACT_FLOW_TOKEN=0x0ae53cb6e3f42a79 \
    -e CONTRACT_FUSD=0xf8d6e0586b0a20c7 \
    -e CONTRACT_FCL_CRYPTO=0x74daa6f9c7ef24b1 \
    -e TOKEN_AMOUNT_FLOW=100.0 \
    -e TOKEN_AMOUNT_FUSD=100.0 \
    ghcr.io/onflow/fcl-dev-wallet:latest

When I go to http://localhost:8701/harness, my accessNode.api value is "http://localhost:8080". I expect the port to be 8888. When I try to run the login command, I get the same error as @beshup. I'm guessing the wrong accessNode value is the culprit

@sideninja sideninja added the bug Something isn't working label Mar 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants