Error receiving through Lightning

[razini]

Hello,I created a lightning channel to receive and send bitcoins in the Electrum mobile wallet.  But when to receive Bitcoin;  I create a request and paste it in the exchange.  An error occurs and the transfer fails. 

[igor72]

Once the channel is created, you have no inbound liquidity. To receive a payment you must first send the same amount or more.
If you don't understand what I'm talking about, then you should read how Lightning Network works.

[razini]

Once the channel is created, you have no incoming liquidity. To receive a payment you must first send the same amount or more.
If you don't understand what I'm talking about, then you should read how Lightning Network works.

Thank you for your answer. My wallet has enough balance and I successfully created the channel. But when I enter the payment receipt amount in the sending section and create a request, I copy the Lightning payment receipt and enter it in the exchange. At first, it gives a success message, but after a few minutes, the transaction fails and the amount sent is returned.
How can I attach a screenshot for further explanation?

[BlackHatCoiner]

My wallet has enough balance and I successfully created the channel.

Have you ever paid anything with lightning in this wallet? Simply creating the channel does not mean that you can receive coins. At least, not in this software. In other software, there exists a feature called
"dual-funded channel". In Electrum, however, you have no receiving capacity once you create a channel.

You don't need to post a screenshot. Just tell us what the messages say.

[razini]

My wallet has enough balance and I successfully created the channel.

Yes, I have paid several times with the Lightning network from the Electrom wallet to the exchange. Yes, you are right, after creating the channel I could only send and not receive. But I created the receiving capacity through Lightning Swap.After this, it was possible for me to receive 0.001 bitcoin and send 0.002. Therefore, the lightning option was activated for me in the payment receipt.But unfortunately, I encountered the problem I mentioned earlier.
https://s8.uupload.ir/files/17108133881348291277863669156669_oiwt.jpg
https://s8.uupload.ir/files/17108134224245410258529751796548_ip0.jpg
https://s8.uupload.ir/files/17108140114991615838020057423504_bj4o.jpg

[nc50lc]

-snip-

Since there's high inbound liquidity and there's a previous successful lightning transaction,
This could be a "routing issue" which means that the Exchange's channel cannot find a route to your channel due to liquidity or actual routing.
This may be temporary (at their end) or long term.

Since Electrum uses "trampoline routing" by default and failed at that attempt, try to temporarily disable it in the settings under "Preferences->Trampoline routing".
Then in the main tab, wait for the Lightning icon to get full/quarter yellow, to see its progress, go to 'Network' settings and check the "Gossip" under Lightning.
Once it's fully established (a few minutes), create a new invoice to test a new withdrawal from the Exchange.

BTW, don't close Electrum while waiting for the transaction to finish.
If you did it the first try, then try it again without closing Electrum, and keep trampoline routing since Gossip is quite resource expensive and slow.

[NotATether]

What is the total channel capacity? Found it.

You're not going to be able to send a lot of money if the capacity of the channel is less than that.

Try opening a second channel and see what happens.

Also each channel has its own "reserve balance". This is the amount of sats that need to stay inside the channel throughout its lifetime. So if the amount you're trying to send plus the reserve is greater than the channel receiving capacity you will get this error.

[razini]

-snip-

Since there's high inbound liquidity and there's a previous successful lightning transaction,
This could be a "routing issue" which means that the Exchange's channel cannot find a route to your channel due to liquidity or actual routing.
This may be temporary (at their end) or long term.

Since Electrum uses "trampoline routing" by default and failed at that attempt, try to temporarily disable it in the settings under "Preferences->Trampoline routing".
Then in the main tab, wait for the Lightning icon to get full/quarter yellow, to see its progress, go to 'Network' settings and check the "Gossip" under Lightning.
Once it's fully established (a few minutes), create a new invoice to test a new withdrawal from the Exchange.

BTW, don't close Electrum while waiting for the transaction to finish.
If you did it the first try, then try it again without closing Electrum, and keep trampoline routing since Gossip is quite resource expensive and slow.
[/quote
Thank you for your help, the problem is solved. Got there by disabling Trampoline.

[razini]

-snip-

Since there's high inbound liquidity and there's a previous successful lightning transaction,
This could be a "routing issue" which means that the Exchange's channel cannot find a route to your channel due to liquidity or actual routing.
This may be temporary (at their end) or long term.

Since Electrum uses "trampoline routing" by default and failed at that attempt, try to temporarily disable it in the settings under "Preferences->Trampoline routing".
Then in the main tab, wait for the Lightning icon to get full/quarter yellow, to see its progress, go to 'Network' settings and check the "Gossip" under Lightning.
Once it's fully established (a few minutes), create a new invoice to test a new withdrawal from the Exchange.

BTW, don't close Electrum while waiting for the transaction to finish.
If you did it the first try, then try it again without closing Electrum, and keep trampoline routing since Gossip is quite resource expensive and slow.

It was done once. But it was not done anymore. The same problem is repeated again. Where do you think the problem is?How can I solve it?

[nc50lc]

This could be a "routing issue" which means that the Exchange's channel cannot find a route to your channel due to liquidity or actual routing.
This may be temporary (at their end) or long term.

It was done once. But it was not done anymore. The same problem is repeated again. Where do you think the problem is?How can I solve it?

Since it from an exchange where the actual error message isn't provided, I can only guess,
My best guesses are the usual reasons that I've already provided.

To expand the "liquidity" issue, even famous Exchanges sometimes experience that issue when there's too much volume flowing in their payment channels.
Their channels' amount simply cannot accommodate the requested amount.
To expand the "routing" issue, it could be a combination of your invoice lacking the necessary "route hint" (issue at your end)
and/or their node simply cannot find a route to your channel (issue at either end).

Switching to "Gossip" and waiting for full lightning network connection could get your Electrum better routing but it wont fix the issue if it's the Exchange's channel's fault.

[razini]

This could be a "routing issue" which means that the Exchange's channel cannot find a route to your channel due to liquidity or actual routing.
This may be temporary (at their end) or long term.

It was done once. But it was not done anymore. The same problem is repeated again. Where do you think the problem is?How can I solve it?

Since it from an exchange where the actual error message isn't provided, I can only guess,
My best guesses are the usual reasons that I've already provided.

To expand the "liquidity" issue, even famous Exchanges sometimes experience that issue when there's too much volume flowing in their payment channels.
Their channels' amount simply cannot accommodate the requested amount.
To expand the "routing" issue, it could be a combination of your invoice lacking the necessary "route hint" (issue at your end)
and/or their node simply cannot find a route to your channel (issue at either end).

Switching to "Gossip" and waiting for full lightning network connection could get your Electrum better routing but it wont fix the issue if it's the Exchange's channel's fault.

Thank you for your guidance.