I follow the MyEtherWallet: Use Your Own Server Guide to use MyEtherWallet on my private ethereum network. I am doing this setup on my node, where my ethereum node runs. My node runs fine, it can mine and connect to other peers.
error 33 when I try to connect to custom node with MEW on my server.
Started the node on my server like this:
nohup sudo geth --port 30304 --rpc --rpcaddr "0.0.0.0" --rpcport 8101 --rpccorsdomain "*" --rpcapi="eth,net,web3,utils" --datadir myDataDir --networkid 19720502 --bootnodes="enode:////email@example.com:30304" &
On my server I downloaded MEW 3.11.2 changed
nodeIP.json and put in the IP adress
18.104.22.168 instead of
x.x.x.x changed the ports from 8584 to 8101 in the file
response.js made sure ssl is installed (https://sslanalyzer.comodoca.com/?url=22.214.171.124).
Switched off apache (because port 80 was busy) using https://www.cyberciti.biz/faq/ubuntu-linux-start-restart-stop-apache-web-server/
Then I typed:
sudo node runServer.js
it runs without errors however if I try to connect via MEW custom node
https://126.96.36.199 port 8101 clicking on custom and networkid in eip1155
(error_33) Could not connect to the node. Refresh your page, try a different node (top-right corner), check your firewall settings. If custom node, check your configs.
Question: What can I do to find out what the problem could be?
Question: Where can I find the source of this error?
Here is some background information:
However if I do this locally on my machine it all works, I can access the local node when I do this:
nodeIP.json and put in the IP Address
127.0.0.1, change in
response.js the ports to 8101,
sudo node runLocalServer.js and access it by opening MEW locally and using
http://127.0.0.1 port 8101 clicking on custom and typing in the correct networkid in