Hi! We are currently developing a web application using ReactJS and nem-sdk. And I'm currently encountering an error relating to "Mixed Content" in production environment, since we have the web app already have SSL configured, and most of the nem nodes are not https, we encountered "Mixed Content" or something like it blocks the request since it is coming from an HTTPS going to HTTP.Whats the best way to solve this? Do we have a trusted list of SSL enabled NEM NODES? Thanks

Does someone here is working with nem2-sdk-java ? I'm trying to integrate Scala Language, and I have some doubts , maybe you could clarify me those doubts.

Hi, I have the following issue:{ code: 0, data: { timeStamp: 143504855, error: 'Not Found', message: 'invalid address \'TDT3QQ5H34YM425UXGPWEMR3IKF2ZTIQUOFL4PGX\' (org.nem.core.model.Address)', status: 404 } }my code:var express = require('express');var app = express();var nem = require('nem-sdk').default;app.get('/send', function (req, res) { let privateKey = nem.crypto.helpers.derivePassSha('12345', 6000).priv; let keyPair = nem.crypto.keyPair.create(privateKey); let publicKey = keyPair.publicKey.toString(); let common = nem.model.objects.create('common')(publicKey, privateKey); let account = 1; let message = 'test message'; let address = nem.model.address.toAddress( publicKey, nem.model.network.data.testnet.id ); let transferTransaction = nem.model.objects.create('transferTransaction')(address, account, message); let transactionEntity = nem.model.transactions.prepare('transferTransaction')(common, transferTransaction, nem.model.network.data.testnet.id) let endpoint = nem.model.objects.create("endpoint")('', '7890'); nem.model.transactions.send(common, transactionEntity, endpoint).then( res => { // If code >= 2, it's an error if (res.code >= 2) { console.error(res.message); res.send(res); } else { console.log("\nTransaction: " + res.message); res.send(res); } }, err => { console.error(err); res.send(err); }); // --- --- //});

Nop, Actually I'm pretty lost, I've only used nem-sdk and node

So you want use Catapult or NIS1?

If you are using nem-sdk then node is mainnet node and you are using testnet network id.

Testnet nodes list is here http://testnet-explorer.nemtool.com/#/nodelist

Is there a way to recover a wallet with the private key? There used to be but I dont see that option any more.

@JBURG23 In desktop wallet. Sign up > Private key wallet option. Choose mainnet, new password and wallet name and provide private key from backup.

Hello everyone! Help! a need somebody help! )i have set up "remote status" "active" and "harvesting status" "active" too. But when i log out and log in wallet again, "harvesting status" is "inactive"/ How can i fix it?


Yes. But are you using Trezor? I would check if after you login you have same node selected on harvesting view. Not node in top menu but this one you selecting on harvesting view.

Also if you do not want restart harvesting each time node will restart you can use this tool:https://nem-tools.com/#/harvesting/automated-restartTutorial: https://www.youtube.com/watch?v=_m7rvXiEFpo&t=9s

java version "1.8.0_144"Java(TM) SE Runtime Environment (build 1.8.0_144-b01)Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)does this version of JRE works with NEM NIS? seems to have lot of errors lately

Caused by: java.util.concurrent.CancellationException at java.util.concurrent.CompletableFuture.cancel(CompletableFuture.java:2263) ... 21 more (org.nem.core.async.NemAsyncTimerVisitor notifyOperationCompleteExceptionally)

at org.nem.core.async.SleepFuture$1.run(SleepFuture.java:24) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505)Caused by: java.util.concurrent.CancellationException at java.util.concurrent.CompletableFuture.cancel(CompletableFuture.java:2263) at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.cancelled(HttpMethodClient.java:216)

With this stack trace hard to tell sth. It's not complete. Please copy stack in some pastebin and include link here. And also tell what problems with node you have.

quasarblue quasarblue
It works. Try to check your clock time
IMO it is connection problem similar as here:https://forum.nem.io/t/nem-supernode-rewards-program/1735/1792But without full log hard to tell. May be just warning with connection to some other node.

Sometimes that same message is logged by the server when some client i. e. nanowallet is connected and have sent bad time

I have opened an issue in nem core github

J Leon Y
Clock time sync fine

Must check the client clock, could be just a log caused by the client with bad time

- after you restart node it starts syncing after loading chain from disk or not? - I would check also firewall and network settings if it's not blocked.

Been running for a while so firewall setting should be fine, have tried restarted the node

Maybe I shall try to move to other node

How much memory you have allocated in NIS start script?