I need to create a test GSN Relay for Polygon testnet so I dived into opengsn deployment. I’m certainly not the most experienced with VMs on GC and this all a bit of a revelation.
I’ve set up the VM and have SSH access all setup with keys. No problem (appears so…)
Downloaded rdc to my laptop ok but could not connect it to the VM . Permission denied.
Then installed rdc on the VM and will run locally. .env and config files in place. But I get the same thing:
~ $ ./rdc local config -bash: ./rdc: Permission denied
However, after research, I saw another similar post that advised running with bash -x so
bash -x ./rdc local config
It works. So I managed to run bash -x ./rdc local up -d and I have containers running.
Now does it work? No, I get Bad Gateway 502 when accessing https://betenbloc.com/gsn1/getaddr
I see in the router log that there is an issue with the call as follows:
sherringtonian@betenbloc ~ $ wget https://betenbloc.com/gsn1/getaddr --no-check-certificate --2021-10-17 09:46:35-- https://betenbloc.com/gsn1/getaddr Resolving betenbloc.com... 188.8.131.52 Connecting to betenbloc.com|184.108.40.206|:443... connected. WARNING: cannot verify betenbloc.com's certificate, issued by 'CN=(STAGING) Artificial Apricot R3,O=(STAGING) Let\'s Encrypt,C=US': Unable to locally verify the issuer's authority. HTTP request sent, awaiting response... 502 Bad Gateway 2021-10-17 09:46:35 ERROR 502: Bad Gateway.
In the logs…
router | /gsn1/ => http://gsn1/ router | 2021/10/17 09:46:35 [error] 8#8: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.0.3, server: , request: "GET /gsn1/getaddr HTTP/1.0", upstream: "http://172.22.0.2:80/getaddr", host: "betenbloc.com" router | 172.22.0.3 - - [17/Oct/2021:09:46:35 +0000] "GET /gsn1/getaddr HTTP/1.0" 502 157 "-" "Wget/1.21.1"
It’s not the certificate. The same thing was happening when using production certificate. Had to use staging as issuer ran out of patience with me.
Any help most appreciated!