-
Notifications
You must be signed in to change notification settings - Fork 48
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
Unable to fetch latest batch #274
Comments
The "context deadline exceeded" is golang's way of saying "request timed out". It sounds like your network connection is slow at times. Are you running Tor only? This could also explain why your order doesn't get matched, you need to be able to connect out to the matched party within a given time or your match will be canceled. |
Yes, connection is Tor only. Are there any settings I can tweak to allow Tor operation? |
@guggero I wasn't sure from your previous response if it's possible to run Tor only with Lightning Pool. Will I need to configure my node to run over clearnet in order to fill orders? |
Are you running all connections through Tor? For example with something like Torify? Because the call that is timing out should normally go through clearnet, even if lnd is using Tor only. You can use a Tor only node with Lightning Pool. But it'll mean that your node needs to connect out to all takers and if that times out the order won't be filled. Try restarting and updating your Tor proxy to make sure you get fresh circuits if you have general connection issues. |
There aren't a lot of batches going on yet. And if your node is T0 people need to opt-in to receive liquidity from your node. So this might take a good while. Also there currently are way more asks than bids. |
Okay, that makes sense. Thanks. I'll read up on ways to increase the tier of my node. |
auctioneerrpc: add REST endpoints
I have Lightning Pool up and running with account funded successfully. I was also able to create an ask order. However, the order is never filled even though the premium is within market range. Periodic errors received through web interface are shown below. Are those errors normal? Is it possible that the order is not being filled due to Node Tier=T0 and offered liquidity is only 400,000 sats?
LIT logs:
Order gets filled.
Order does not get filled.
Hardware: Odroid HC2
Software: Raspiblitz v1.7 running on Armbian Buster OS
The text was updated successfully, but these errors were encountered: