AWS NEM node problems

Technical Discussion
#1

Hello, i have a few questions, maybe a dumb questions. But it would help me a lot if you can help me.

  1. I already mount the NEM node in AWS, and i am using a python wrapper in my laptop.
    I want to generate accounts in my laptop connecting to the AWS sever using: ipserver:7890/account/generate. And when I try to do this i got an error: unauthorized.
    how can i authorize my computer in the NEM-AWS node?
    First i thought that i have to change the file config.properties and add my laptop ip, but it ain’t work, cause the following message wrote in the file " NIS usually checks if a request comes from the local machine and if not, certain requests get rejected" this message generate the next question
    2)what kind of request are going to be rejected?
    3)also, when i check out my account (TB5VNY3XIEPTUIQGBSYVZUNVF45JVYKYFPIHSIZR) using the AWS node the json response that my account has a 0 in balance.
    But when i use this ip: http://104.128.226.60:7890/account/get?address=… instead of my AWS node my balance is 309700000 and this ip address i got it from the nanowallet. So i supposed that i have to connect my AWS node to the net, or something like that, and How can i do that?
  2. When you want to make a transaction you need to send a json format like this https://nemproject.github.io/#requestPrepareAnnounce and you have to send your PrivateKey, so in the documentation advertise you “Since this request involves the private key of an account, it should only be sent to a local NIS.” then if i can only sent to local NIS how can i send XEM to friends whom gave their address if they aren’t in my local host? I meant, i want to do this without using the nanowallet, i want to sen XEM to my friend using the json object that I create.
    And i want to do that because iḿ have to use the python wrapper.

I hope you can understand my doubts and someone could help me.

#2

Since this request involves the private key of an account, it should only be sent to a local NIS.

You can still send to any address but only from a local node, that means that if you want to use this request (it is not recommended), you will need to connect to your node with ssh and send the request with curl using localhost:7890/.. . It does not limit which addresses you can send XEM to.

It is not recommended to use those endpoints anymore, is it not possible for you to use the python wrappers signing features and account generation features ? Then you could use /transaction/annouce instead of prepare-announce. Generally, it is better to avoid sending private keys over any network even if it is local I would not advise for that.

1 Like
#3

prepare-announce and keypair generation is available only for local nodes for security reasons.

you can add additional local Ip’s by changing property:
nis.additionalLocalIps =

But I don’t recommend sending private key over network.

You can generate and sign transaction on client side (check https://nemlibrary.com/ or other wrappers nem.io/developers)

1 Like
#4

And do you know if exist any way to send the private key encrypted ?

#5

What do you mean encrypted? Over https is for example encrypted.
If you want be secure you must use announce instead prepare-announce. In first one signing is done on client side.
You can also generate key pair on client side.

1 Like
#6

Actually i want to use https in my node, but i do not know how to configure it, can you help me, i read the config properties, and the port 7891 it’s for the https protocol, but i already configure the https service using: https://www.digitalocean.com/community/tutorials/how-to-create-an-ssl-certificate-on-apache-for-centos-7 this link, and i does not work.

#7

I guess NIS don’t support SSL (installing certificate and so on) from package and you must do it above (apache, nginx). But I’m not sure.
@BloodyRookie I’m wrong?
Indeed as I can see there are nodes working over SSL: https://shibuya.supernode.me:7891/chain/height

#8

You need to ask @gimre, i think he already has one node running over https.

#9

There exist a older blog from Patrick.

" blog.nem.io/https-nis-node/ "

1 Like