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

Persistent crash upon switching networks to OysterLending #57

Open
jordaaash opened this issue Feb 8, 2021 · 2 comments
Open

Persistent crash upon switching networks to OysterLending #57

jordaaash opened this issue Feb 8, 2021 · 2 comments

Comments

@jordaaash
Copy link
Contributor

Steps to reproduce:

  1. Run locally with HTTPS=true npm start
  2. Open https://localhost:3000
  3. Open settings menu
  4. From Networks select, choose "OysterLending"

Screen Shot 2021-02-08 at 2 36 35 PM

Because the chosen network is set in localStorage, the crash will persist upon reloading the page, and clearing localStorage is the only way to recover.

From my debugging, it looks like the root issue is this:

Mixed Content: The page at 'https://localhost:3000/#/' was loaded over HTTPS, but requested an insecure resource 'http://oyster-dev.solana.com/'. This request has been blocked; the content must be served over HTTPS.

Mixed Content: The page at 'https://localhost:3000/#/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://oyster-dev.solana.com/'. This request has been blocked; this endpoint must be available over WSS.

@jordaaash
Copy link
Contributor Author

Access over HTTPS is required for WebUSB support (e.g. #56)

@jordaaash
Copy link
Contributor Author

Promixate cause is probably HTTP access of this link:

endpoint: "http://oyster-dev.solana.com/",

However, the HTTPS version of this link doesn't resolve.

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

No branches or pull requests

1 participant