Hey guys, does anyone know if the eth_newFilter RPC method is supported on RSK nodes? https://github.com/rsksmart/rskj/wiki/JSON-RPC-API-compatibility-matrix says it IS, but allowing this method to my Nginx Proxy node (set up using https://github.com/rsksmart/rskj/wiki/Nginx-Proxy-Server-for-JSONRPC-Calls) causes a crash on my RSK node with the following error:

Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: kill: invalid argument U Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: Usage: Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: kill [options] <pid> [...] Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: Options: Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: <pid> [...] send signal to every <pid> listed Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: -<signal>, -s, --signal <signal> Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: specify the <signal> to be sent Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: -l, --list=[<signal>] list all signal names, or convert one to a name Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: -L, --table list all signal names in a nice table Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: -h, --help display this help and exit Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: -V, --version output version information and exit Dec 10 12:13:42 ip-172-31-27-61 kill[7708]: For more details see kill(1). Dec 10 12:13:42 ip-172-31-27-61 systemd[1]: rsk.service: Control process exited, code=exited status=1 Dec 10 12:13:42 ip-172-31-27-61 java[7625]: Exception in thread "Thread-1" java.lang.IllegalAccessError: closed Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at org.mapdb.Store.get(Store.java:237) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at org.mapdb.Engine$CloseOnJVMShutdown.get(Engine.java:455) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at org.mapdb.HTreeMap.getInner(HTreeMap.java:649) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at org.mapdb.HTreeMap.get(HTreeMap.java:583) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at org.ethereum.db.IndexedBlockStore.getChainBlocksByNumber(IndexedBlockStore.java:526) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.core.bc.BlockChainImpl.getBlocksByNumber(BlockChainImpl.java:396) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.core.bc.BlockChainImpl.blockIsInIndex(BlockChainImpl.java:420) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.core.bc.BlockChainImpl.hasBlockInSomeBlockchain(BlockChainImpl.java:409) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.net.BlockSyncService.getParentsNotInBlockchain(BlockSyncService.java:233) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.net.BlockSyncService.processBlock(BlockSyncService.java:118) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.net.SyncProcessor$SyncInformationImpl.processBlock(SyncProcessor.java:395) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.net.sync.DownloadingBodiesSyncState.newBody(DownloadingBodiesSyncState.java:98) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.net.SyncProcessor.processBodyResponse(SyncProcessor.java:141) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.net.NodeMessageHandler.processBodyResponseMessage(NodeMessageHandler.java:411) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.net.NodeMessageHandler.processMessage(NodeMessageHandler.java:116) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at co.rsk.net.NodeMessageHandler.run(NodeMessageHandler.java:211) Dec 10 12:13:42 ip-172-31-27-61 java[7625]: at java.lang.Thread.run(Thread.java:748) Dec 10 12:13:43 ip-172-31-27-61 systemd[1]: rsk.service: Main process exited, code=exited, status=143/n/a Dec 10 12:13:43 ip-172-31-27-61 systemd[1]: rsk.service: Failed with result 'exit-code'. Dec 10 12:13:43 ip-172-31-27-61 systemd[1]: Stopped RSK Node.

Is there a way to get the RSK node to listen on 0.0.0.0 instead of localhost?

Testing

ubuntu@ip-172-31-27-61:/etc/rsk$ curl -s -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"web3_clientVersion", "params": {},  "id":123}' http://127.0.0.1:4444
{"jsonrpc":"2.0","id":123,"result":"RskJ/0.5.3/Linux/Java1.8/ORCHID-37822a6"}
ubuntu@ip-172-31-27-61:/etc/rsk$ curl -s -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"web3_clientVersion", "params": {},  "id":123}' http://0.0.0.0:4444
ubuntu@ip-172-31-27-61:/etc/rsk$

node.conf

blockchain.config.name = "testnet"

database.dir = /var/lib/rsk/database/testnet

rpc {
providers : {
    web: {
        cors: "*",
        http: {
            enabled = true,
            bind_address = "0.0.0.0",
            hosts = ["0.0.0.0", "localhost"],
            port = 4444,
            }
        ws: {
            enabled = true,
            bind_address = "0.0.0.0",
            port = 4445,
            }
        }
    }

    modules = [
        {
            name: "eth",
            version: "1.0",
            enabled: "true",
        },
        {
            name: "net",
            version: "1.0",
            enabled: "true",
        },
        {
            name: "rpc",
            version: "1.0",
            enabled: "true",
        },
        {
            name: "web3",
            version: "1.0",
            enabled: "true",
        },
        {
            name: "evm",
            version: "1.0",
            enabled: "false"
        },
        {
            name: "sco",
            version: "1.0",
            enabled: "true",
        },
        {
            name: "txpool",
            version: "1.0",
            enabled: "true",
        },
        {
            name: "debug",
            version: "1.0",
            enabled: "true",
        },
        {
            name: "personal",
            version: "1.0",
            enabled: "true"
        }
    ]
}

netstat -an | grep "LISTEN "

ubuntu@ip-172-31-27-61:/etc/rsk$ netstat -an | grep "LISTEN "
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp6       0      0 :::4444                 :::*                    LISTEN
tcp6       0      0 :::4445                 :::*                    LISTEN
tcp6       0      0 :::50505                :::*                    LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN

@juli thanks! I tried that and it seems I get 400 Bad Request

Note: Unnecessary use of -X or --request, POST is already inferred.

• Rebuilt URL to: http://0.0.0.0:4444/
• Trying 0.0.0.0...
• TCP_NODELAY set
• Connected to 0.0.0.0 (127.0.0.1) port 4444 ( #0 )

  POST / HTTP/1.1
  Host: 0.0.0.0:4444
  User-Agent: curl/7.58.0
  Accept: /
  Content-Type: application/json
  Content-Length: 72

• upload completely sent off: 72 out of 72 bytes
  < HTTP/1.1 400 Bad Request
• no chunk, no close, no size. Assume close to signal end
  <
• Closing connection 0

curl -v -X POST -H "Content-Type: application/json" -H "Host: localhost"  -d '{"jsonrpc":"2.0","method":"web3_clientVersion", "params": {}, "id":123}' http://0.0.0.0:4444
Note: Unnecessary use of -X or --request, POST is already inferred.
* Rebuilt URL to: http://0.0.0.0:4444/
*   Trying 0.0.0.0...
* TCP_NODELAY set
* Connected to 0.0.0.0 (127.0.0.1) port 4444 (#0)
> POST / HTTP/1.1
> Host: localhost
> User-Agent: curl/7.58.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 71
>
* upload completely sent off: 71 out of 71 bytes
< HTTP/1.1 200 OK
* no chunk, no close, no size. Assume close to signal end
<
{"jsonrpc":"2.0","id":123,"result":"RskJ/0.5.3/Linux/Java1.8/ORCHID-37822a6"}
* Closing connection 0