-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect to local Liteserver #133
Comments
I think I have the same or a similar issue but for a testnet archive node. I also tried to follow these instructions even though it's not a solution for me since I intend to provide an archive node but with the same result. @jamescarter-le did you ever solve this? I enabled debug logging in the
|
Were you guys able to solve the issue? |
I didn't get this to work by using I'm not sure what was wrong along the way, maybe I just made a mistake or maybe it didn't work until the node was in sync... I can't say what mistake I made except for using |
Hi @jonathanudd , thanks so much for the reply. To briefly explain what our issue is,, We noticed this cause even when we stop the validator-engine container, Grafana still shows that it's fetching the block number.. which seemed a bit strange.. We asked a person at Ton foundation and he said it seems like we're using ton.org/global.config.json instead of our local config. So what we did was.. after setting up our fullnode with liteserver enabled, we got our liteserver info (ip, public id, port) and replaced the My question is, are you also running your own fullnode with liteserver enabled? If so, would you be able to guide us on how we could get this to work? Below is the docker script with liteserver enabled: docker run -d --name ton-full-node \
--restart always \
--mount type=bind,source=$HOST_VOLUME,target=/var/ton-work/db \
--network host \
--security-opt apparmor=unconfined \
-e "PUBLIC_IP=$HOST_IP" -e "CONSOLE_PORT=80" -e "LITE_PORT=81" -e "LITESERVER=true" \
-it $DOCKER_REPO:$MODE-$VERSION Thanks so much again!! |
In the end I created the local config with |
I have a local archive node running liteserver, on IP
192.168.1.122
.Bashing into the ton-http-api container I can ping this address.
I have my
mainnet.json
configured to only use this liteserver:But when trying to execute any operation (try simple one like
getMasterchainInfo
) I get error:No working liteservers with ls_index=None, archival=None
Has anyone experienced this before?
Logs/call stack are not useful:
The text was updated successfully, but these errors were encountered: