You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.
I was running the "animal-kingdom" locally, as indicated here: "https://docs.blockstack.org/develop/zero_to_dapp_2.html".
The tutorial suggests to start the server with npm start, which seems to default to HTTP. Unfortunately, that causes me an error when I try to sign in to Blockstack.
I get a "Failed to fetch information about the app requesting authentication. Please contact the app maintainer to resolve the issue." message. The reason is that a request was blocked while trying to load mixed content:
Blocked loading mixed active content “http://localhost:3000/manifest.json”
Luckily the workaround is as easy as running HTTPS=true npm start. Maybe that part can be updated here, or in the documents.
The text was updated successfully, but these errors were encountered:
@marcojrfurtado I haven't seen this reported before. Can you tell me what your platform is? I'll add a tip to the docs about this should someone else run into the same problem.
Just wanted to add this reference for anyone running into this issue.
Starting with Firefox 23, Firefox blocks active mixed content by default. This follows a practice adopted by Internet Explorer (since version 9) and Chrome.
This page explains what you should be aware of as a web developer.
Hello,
I was running the "animal-kingdom" locally, as indicated here: "https://docs.blockstack.org/develop/zero_to_dapp_2.html".
The tutorial suggests to start the server with
npm start
, which seems to default to HTTP. Unfortunately, that causes me an error when I try to sign in to Blockstack.I get a "Failed to fetch information about the app requesting authentication. Please contact the app maintainer to resolve the issue." message. The reason is that a request was blocked while trying to load mixed content:
Luckily the workaround is as easy as running
HTTPS=true npm start
. Maybe that part can be updated here, or in the documents.The text was updated successfully, but these errors were encountered: