hi guys setting up a relay server because i wanted to try out the REST API functions. I followed the instructions for the manual installation of the relay server and then also setup a node for the Laika testnet using the quickstart script.
i run the
tl-relay command and get the following error
File "/home/ubuntu/environment/relay/venv/lib/python3.6/site-packages/psycopg2/__init__.py", line 126, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
ethindex runsyncthough i get a connection refused error
File "/home/ubuntu/environment/relay/venv/lib/python3.6/site-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='127.0.0.1', port=8545): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f149e21af28>: Failed to establish a new connection: [Errno 111] Connection refused',))
tl-relaythrows the same error also
trustlinesfor laika, and open the file
home-node, see https://docs.docker.com/compose/compose-file/#ports for more informations on this.
docker-compose up --build --force-recreate --no-deps -d home-nodewithin folder
Hi, thanks for trying stuff out!
If the quickstart script, throws an error
IsADirectoryError, it usually means the process was interrupted midway through at an unexpected place and was restarted. The script intends to create a file but doesn't have the right to do so / the file was created as a directory. I would try deleting the whole folder (called trustlines or tlbc usually) and restart the process if you do not mind. You can also try to delete only the file/directory it complains about and restart the script.
As for the relay not being able to connect to the node, if you are running the node with docker, by default the ports 8545 and 8546 are not exposed (for security reasons). You would need to open the docker-compose file and add these lines under ports of home-node:
services: home-node: ... ports: 8545:8545 8545:8545/udp 8546:8546 8546:8546/udp
I am working on a way to make this process easier but am also busy with other things and this won't be ready soon enough :/
check eligibility, then click on
claim tokens. It should connect to your web3 provider and you should be able to see the data required to claim the tokens.