Maarten
I coded a test for the /node/peers to go trough all the testnodes and coming at around 100 nodes where around 50 nodes are unreachable at :3000/node/peers

The current rest gateway on the GitHub doesn't have the node/peers endpoint. If you build your node from the open source code that endpoint is not reachable. If you use the docker image from the bootstrap then you have that endpoint

https-portal doesn't work for my node for some reason. Fyi, I'm using a Comodo PositiveSSL provided by the domain provider instead of using the default let's encrypt self-signed one.

I might just gonna use nginx separately instead of https-portal

https://join.slack.com/t/nem2/shared_invite/enQtMzY4MDc2NTg0ODgyLWZmZWRiMjViYTVhZjEzOTA0MzUyMTA1NTA5OWQ0MWUzNTA4NjM5OTJhOGViOTBhNjkxYWVhMWRiZDRkOTE0YmU

FvM
https-portal doesn't work for my node for some reason. Fyi, I'm using a Comodo PositiveSSL provided by the domain provider instead of using the default let's encrypt self-signed one.

Yes. I added only this section plus I pointed domain to correct server. What exactly doesn't work? Let's encrypt is good. It should be refreshed automatically by https portal.

cryptoBeliever
Yes. I added only this section plus I pointed domain to correct server. What exactly doesn't work? Let's encrypt is good. It should be refreshed automatically by https portal.

I think it's because of the conflicting certificates. https-portal creates and renews the certificate automatically. While in my case, I'm trying to use the one that is purchased and installed by the domain provider.

I'm looking for a way for https-portal to use this certificate instead of its own.

I see now that https-portal allows custom nginx-config as well. Might have to try that out. Thanks.

https://github.com/SteveLTN/https-portal/blob/master/README.md

Don't know why in Node Explorer is not showing my catapult node?

I'm using http://explorer.nemtech.network/nodes

It's because /node/peers endpoint for selected in footer node doesn't return your node (my node is also not visible). Not sure exactly why.http://api-20.us-west-1.nemtech.network:3000/node/peers

Isn't it yours? friendlyName":"crypto-believer-at-digocean"},

JC
Don't know why in Node Explorer is not showing my catapult node?

Yes. I think it's bug in explorer or /node/peers. If your node is syncing and api works all is ok.

I have another peers, if I get my host/node/peers Maybe the near ones are shown

Where can I change the friendly name?

https://node.nembr.io:3001/chain/height Secured connection established! I couldn't get https-portal to use my own DV-certificate that I've purchased. But, for now, this will do. Thanks all. 😊👍

cryptoBeliever
/api-harvest-assembly/api-node/config-input.yaml

I there an explanation what the other inputs from config-input.yaml are?

Maarten
I there an explanation what the other inputs from config-input.yaml are?

It's couple properties from node .properties files. harvest_private_key is your remote delegated account private key for harvesting. Benefitiary public key is account which will receive 25% of reward for harvested block if someone will harvest on your node.*25% is configurable.

Maarten
What about the "boot_private_key" and "public_key"?

I'm not totally sure for what they are used so I leave answer to smarter people. @dgarcia360 ? :)

Whitepaper contains couple refers to this key -> https://nemtech.github.io/catapult-whitepaper/main.pdf
Maarten
What about the "boot_private_key" and "public_key"?

Boot private key is the private key identifying your node. Public key is the corresponding key

Maarten
It doesnt do anything besides that? Just an identification?

And encryption of peer traffic between other nodes and the rest gateway

If you have multiple nodes with the same private key other nodes will throw an error.

So if your node's private key is exposed it could be use to DOS your node by preventing other nodes from connecting to your node

JT
So if your node's private key is exposed it could be use to DOS your node by preventing other nodes from connecting to your node

Hi. Could you explain some about hostname in /node/peers? If a hostname is incorrect (example: monimoni), then other nodes can't connect to the node?

JT
It can't. It will be treated like a passive listening node

Too bad. There can’t be any friendlier name than: “( ^v^ )/ Hello Test node” 😬

There seriously needs to be an easy way to make a list of all the nodes in the network

Maarten
There seriously needs to be an easy way to make a list of all the nodes in the network

following on this too, for the /node/peers it just displays 37 nodes at max, for the explorer, only 27 nodes at max

seems like I was wrong about the max nodes that are being displayed, I just checked today and I see it has 44 node peers, then when I refresh the page, now it's 45.

but the thing is, I cannot see the other nodes that I created. Only 1 of those nodes appear in the list.

I think it depends on latency maybe, the peer's list is slightly different for every node, so if you have two near nodes, I think they should see each other

the /node/peers list returns peers it is connected to, it is not a good metric for network exploration.

your node can be connecting to a different tree of partner nodes

but it will not connect to *all* of them.