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

Failed to fetch #46

Open
fsanano opened this issue May 29, 2018 · 2 comments
Open

Failed to fetch #46

fsanano opened this issue May 29, 2018 · 2 comments

Comments

@fsanano
Copy link

fsanano commented May 29, 2018

We add nem to our web app with this package.
On localhost all works fine, but on the production to all request we get:

{
  code: -1,
  data: {
     message: "Failed to fetch"
     stack: "TypeError: Failed to fetch"
}

Tried use endpionts:

nem.model.objects.create('endpoint')(nem.model.nodes.defaultMainnet, nem.model.nodes.defaultPort)

nem.model.objects.create('endpoint')('https://bit.diamonds', 7890);

Safare return this error:

 An SSL error has occurred and a secure connection to the server cannot be made.

if interest application here

@evias
Copy link
Contributor

evias commented Jun 20, 2018

This commit should be merged @QuantumMechanics as I think it improves the way endpoints can be used.

Regarding the HTTPS issue @fsanano, most of the NIS nodes are published on HTTP which means when you try SSL over this connection, it will argue badly. You can ask the community for a few HTTPS nodes, those are usually running HTTP NIS over 7891 (not 7890) and WSS over 7779 instead of 7778 ✌️

@roccomuso
Copy link

too bad http endpoint are still default in 2019. Especially considering that this lib could request to a server for account creation. With plain text privateKey as response.

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

3 participants