!OWtwraqrytakpoHyga:matrix.org

RSKj

119 Members
1 Servers

Load older messages


Timestamp Message
27 Sep 2019
15:17:40@gitter_xirophtenthusi1_twitter:matrix.orgXirophtenthusiast (Gitter) way @sebaleoperez
16:58:17@gitter_alepc253:matrix.orgAlejandro Cavallero (Gitter) @Xirophtenthusi1_twitter do you see any error during the installation?
17:25:38@gitter_sebastianleoperez:matrix.orgsebaleoperez (Gitter)Also, it is a Virtual Machine ?
28 Sep 2019
07:12:56@gitter_xirophtenthusi1_twitter:matrix.orgXirophtenthusiast (Gitter)yes its VM
07:12:59@gitter_xirophtenthusi1_twitter:matrix.orgXirophtenthusiast (Gitter)and no no issues
07:13:05@gitter_xirophtenthusi1_twitter:matrix.orgXirophtenthusiast (Gitter)installation goes fine
30 Sep 2019
18:49:37@gitter_sebastianleoperez:matrix.orgsebaleoperez (Gitter) Hi @Xirophtenthusi1_twitter ! I tested in a ubuntu server 18.04 lts VM using ppa to install and it worked. What version of ubuntu are you using ?
18:53:47@gitter_alepc253:matrix.orgAlejandro Cavallero (Gitter) @Xirophtenthusi1_twitter we definitely need more info about your environment
11 Oct 2019
21:08:22@gitter_boris:matrix.orgBoris Quiroz (Gitter)

hi all, some help is needed here :)
we have a testnet node running behind nginx+openresty and whenever we try to reach for example eth_estimateGas (which is properly whitelisted in nginx) I got a 400 bad request and I can see this in nginx log:

2019/10/11 21:04:46 [error] 5683#5683: *7 [lua] jsonrpc-access.lua:48: invalid JSON request, client: 172.22.1.169, server: 172.1.21.72, request: "POST / HTTP/1.1", host: "172.1.21.72"

Error message seems to be pretty clear, but if I hit 4444 directly, I got the following:

{"jsonrpc":"2.0","id":1,"error":{"code":-32603,"message":"Internal server error"}}

So, in one case I got a 400 which points me to a malformed JSON file but in the other I got a 500. Is this expected/known?
How can I resolve that? Do you think it's recommended to completely remove nginx+openresty from the equation so we can hit rsk directly?

any help and/or comments are welcome.
thanks in advance.

12 Oct 2019
02:14:32@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter) Hi @boris can you share your curl request?
If you hit your node directly you will get 400, that's expected.
15:50:19@gitter_0p1um:matrix.org0p1um (Gitter) joined the room.
15:50:19@gitter_0p1um:matrix.org0p1um (Gitter) Hi all, I'm looking for documentation about the rsk protocol used for communication between nodes
15:51:28@gitter_0p1um:matrix.org0p1um (Gitter)I did not found it on the wiki
15:51:37@gitter_0p1um:matrix.org0p1um (Gitter)Thanks in advance.
14 Oct 2019
12:49:15@gitter_boris:matrix.orgBoris Quiroz (Gitter) @leonelcorso_gitlab this is the request:
curl -v -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_estimateGas","params":[{'chainId': 31, 'from': '0xF9a841d0C7801df36c2487AF89066ad52DEa582c', 'nonce': 0, 'data': '0xDATA HERE', 'to': b''}],"id":1}' http://172.1.21.72
12:50:51@gitter_boris:matrix.orgBoris Quiroz (Gitter)I was wondering if is there any way to fully expose 4444 to all my network, so I can by-pass openresty?
12:51:14@gitter_boris:matrix.orgBoris Quiroz (Gitter)I mean, is there any recommendation not to do that?
14:39:14@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter) @boris does other request work for you?
The recommendation from RSK's wiki is not to expose 4444 directly to public network
14:46:48@gitter_boris:matrix.orgBoris Quiroz (Gitter)when going through nginx+openresty does not work. hitting directly 4444 works
14:49:02@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter)This is a working example that I have
14:49:13@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter) curl http://X.X.X.X:4444 -v -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_estimateGas","params":[{"gasPrice":"0x3b9aca00","from":"0x29D02699195632360D743Eb568fa71B8c8f744dc","gas":"0x21000","data":"0x7b97008d000000000000000000000000000000000000000000000000016345785d8a0000","to":"0xa6Dc5E5B21D32929b4545126ec95670032c0c178"}],"id":1}'
14:49:29@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter) That returns
{"jsonrpc":"2.0","id":1,"result":"0x54d8"}
14:50:53@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter)

when going through nginx+openresty does not work. hitting directly 4444 works

OK, I understand that the JSON request is not the issue. Are you filtering any methonds in lua?

14:51:33@gitter_boris:matrix.orgBoris Quiroz (Gitter) yep, using lua's config from github page
14:53:11@gitter_boris:matrix.orgBoris Quiroz (Gitter)the example you provided returned the same to be in both cases: going directly to 4444 and through nginx. so there might be a problem with my initial request
14:54:37@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter)Let me paste my nginx.conf so you can compare against yours
14:54:41@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter)one sec
14:57:32@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter) this is the relevant part
server_name *****;
    location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
        #try_files $uri $uri/ =404;
        #set $jsonrpc_whitelist 'web3_clientVersion,eth_getTransactionByHash,eth_getTransactionReceipt,eth_sendRawTransaction';
            if ($request_method != OPTIONS ) {
              access_by_lua_file '/usr/local/openresty/nginx/jsonrpc-access.lua';
              }

        proxy_pass http://127.0.0.1:4444;
    }
14:59:11@gitter_boris:matrix.orgBoris Quiroz (Gitter) interesting, I'm using the set $jsonrpc_whitelist. will give it a try with your config
15:01:13@gitter_leonelcorso_gitlab:matrix.orgLeonel Corso (Gitter) Alright
Let me know how that went

There are no newer messages yet.


Back to Room List