Skip to content

warn on connection failure#3

Open
HerrMuellerluedenscheid wants to merge 1 commit intodomschiener:masterfrom
HerrMuellerluedenscheid:info
Open

warn on connection failure#3
HerrMuellerluedenscheid wants to merge 1 commit intodomschiener:masterfrom
HerrMuellerluedenscheid:info

Conversation

@HerrMuellerluedenscheid
Copy link
Copy Markdown

Hey,

This is a pull request and issue at the same time. I'm running the latest IRI version as follows:

java -jar iri-1.4.1.2.jar  -p 14265

on java

openjdk version "1.8.0_144"

Unfortunately, the chrome debugger reports the following when entering and submitting the seed:

localhost:14265/ Failed to load resource: net::ERR_CONNECTION_REFUSED
index.js:48 Account data undefined

At first I forgot to run the IRI and thought it would be nice to have a more self-explanatory error message like it's implemented in this PR:

screenshot from 2017-12-01 10-47-51

However, the problem occurs also when IRI is running. The pyota examples fail as well with response: invalid API version. So, I guess I oversaw something obvious here.

@Twissi
Copy link
Copy Markdown

Twissi commented Dec 7, 2017

However, the problem occurs also when IRI is running. The pyota examples fail as well with response: invalid API version. So, I guess I oversaw something obvious here.

I was running into the same issue. Updating the iota lib worked for me: See pull request #4

@HerrMuellerluedenscheid
Copy link
Copy Markdown
Author

HerrMuellerluedenscheid commented Dec 10, 2017

Thanks. I tested using http://node.iotawallet.info instead of my localhost iri and it works fine with that one. I didn't setup my iri node, properly. I didn't look for any neighbors 😊
Wouldn't it make sense to add a field to switch from localhost to another node like the node.iotawallet.info. Is the leaderboard example actually still used? Is it worth the hassle to extend/improve that example?

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

Successfully merging this pull request may close these issues.

2 participants