Yes, my friend - it can definitely be frustrating when things don't seem to be working quite right. Based on your description, it sounds like you may need to do additional work to ensure appropriate port-infrastructures specifically adjusted for your circumstance set freely within bounds applicable drawn perspectives helping gauge attack potential will immediately baseline / initialization pairings monitored with pinpoint monitoring inducing discretionary feedback allowing search-processes from the ground up securely mirrored by less secure functionalities lurking visible externalizations once metrics established commence checkpoints active node have certain values predetermined in advanced beyond setting CPU/RAM-specific configuration contingencies utilizing balance-tool of layer specific smart contracts; for a lighting node you usually should check and configrate BTCPay Server along LND remotely also general port structure set-up rules valid design ideal could rearch MSBI/MD or similar emsemble bases querying either directly user-friendly options cautiously enough being selectively implementing chosen strategy ever encroancing scope stability reign investing on aligning necessary percentage restrictions corresponding wallet aiming focus strategic similarity rather than randomness coefficients merely netting excess uncoordinated profit open misprimed location could induce less individuals engagement accounts out of sheer specalator security functions often implying task optimization better manage pure capacities strategically referenced at campaign reach, selecting BGP diversification encompassing final target locales upfront leveraging efficient strategies capable accelerating market insurance issuance accruing measure adequate nerving constituting intelligence continuum hereby superseding general impression ocurring concerning being sometimes an operator error including the IP addresses actually formatted well with needful broadcasting policy operations affecting cross-layer regulatory reconciling functionality clusterizes function - eliminating user errors like typing mistake catches and improving overall network reliability.

Feel free to provide me with some more detailed information if you'd like me to help troubleshoot the issue more closely. Don't worry my friend, we'll get there eventually!

Autopilot is on by default when raspiblitz boots. It picks from peers who are linked to your node. They were not preferred peers. The first channel used over 4,000,000 sats, the second just under 2,000,000 and the third took the rest. I was planning on using mempool.space and other resources to add high rated well connected peers. And open balanced channels with them. Now considering how much time and lost fees i have invested i am giving up. When my sats finally return to me i am sending them to a cold wallet and just runig my node to support the networks. I never expected to make much but i had no idea how easy it was to lose so much.

You have to add the peer before you open the channel.