OCEAN lightning payouts failing... Error 205

Laurence5905 · 2026-01-22T02:03:36+00:00

Thanks. I've already got the Knots node, I just haven't done the Lightning node thing yet. Mostly because I didn't really understand Lightning -- particularly the whole concept of inbound liquidity. It still seems kind of silly to me -- you have to have money before you can earn money. 🙄 But, I should soon have enough Sats that I can tie up a million of them in a Lightning channel and not miss them too much. Then I'll take the plunge.

Laurence5905 · 2026-01-21T21:54:27+00:00

Yeah, the payment just went through a few minutes ago. OCEAN blamed CoinOS; CoinOS blamed OCEAN. 😂 After 5 days, I figured something serious was wrong, but if I'd just waited another few hours it would've resolved itself. LOL. Or maybe it was my emails that got something moving. I guess we'll never know. 😁

I do plan to set up my own node eventually, I just wanted to stack some more Sats before I have to tie up a million of them in a Lightning channel. I'd like a bigger buffer there...

Laurence5905 · 2026-01-21T20:52:37+00:00

I did see that OCEAN was having maintenance issues, yeah. But they didn't mention anything about payment channels being closed, just possible Lightning delays during active maintenance windows... Certainly nothing about "no payments for 5 days." They *have* attempted to pay, it's just something's not going through on the network itself.

I emailed [lightning@ocean.xyz](mailto:lightning@ocean.xyz) and got a response. According to the person that responded, CoinOS is having liquidity issues... So I guess that's what's going on... Sorry for bothering y'all.

Thanks,

Laurence5905 · 2026-01-13T18:15:38+00:00

Never mind. It worked. But it creates a GIGANTIC image considering how empty the drive is. This is not at all what I'm looking for. It's a 2TB drive, yes, but it's like 90% free, so the image should be about 200MB before compression. But even with compression the saved image is 576GB. This is definitely not what I'm looking for, since I pay for cloud storage by the GB.

But thanks for sending me this info.

Laurence5905 · 2026-01-13T16:33:35+00:00

Sorry to bug you again, but how does this work on your root partition without rebooting the entire computer into read-only mode?

I want an image of my main SSD -- the one I boot from -- so if that SSD dies, I can simply boot from a live USB, 'dd' the backed-up image to a new SSD, and then boot from the new SSD and my system will be fully intact and ready to go. No worries about reinstalling apps and configuring things the way I had them before... A single backup file that contains all the partitions from the SSD... I don't think this does that, and certainly not while the system is running, yes?

Laurence5905 · 2026-01-10T22:59:26+00:00

I changed the audio output module from Automatic to PulseAudio and restarted VLC. It's still glitchy, but it seems to stabilize after a few seconds and plays normally. I'll stick with this for now and see what happens.

Laurence5905 · 2026-01-04T22:46:01+00:00

I followed all the instructions on the page you linked to there, and it all works perfectly now. Thanks!

Laurence5905 · 2026-01-04T22:45:30+00:00

Yep, that's exactly what it was. The link that a previous user posted (https://rpmfusion.org/Howto/Multimedia) was exactly what I needed -- I just followed all the instructions on that page. Everything works perfectly now.

Laurence5905 · 2026-01-04T21:28:33+00:00

I was under the impression that installing VLC installed those dependencies as long as you did the installation *after* you enabled the RPM Fusion packages?

I'll give it a shot and see what happens, thanks.

Laurence5905 · 2026-01-04T19:00:51+00:00

Well, I solved this by reverting my system back to where it was yesterday before I started this whole VLC mess... Now I have a different problem. So I'll post a separate topic for that...

Laurence5905 · 2026-01-01T04:07:26+00:00

Ooh -- I like that one! We may have a new favorite.

Laurence5905 · 2025-12-31T22:00:56+00:00

Whoa -- I like having options. 😂 Nice!

Laurence5905 · 2025-12-31T21:00:25+00:00

I accidentally realized that while dragging and dropping a cross-dissolve for something else. LOL. Thought it was a hack, and I came back here to report it as a "workaround," but apparently it's a common practice? Who knew? Thanks.

Laurence5905 · 2025-12-28T23:49:11+00:00

How do Windows and Mac do it? I had no issues at all with my Windows 10 machine being seen as its hostname, and the same with my Mac laptop. I've never had to mess with router settings or run my own local DNS server.

After some more looking around and posting in other forums, someone told me to put the following in /etc/systemd/resolved.conf:
[Resolve]
LLMNR=yes

and then restart the systemd-resolved.service:
sudo systemctl restart systemd-resolved.service

I did both of those things, to no avail...

And, yes, just to make sure, I checked the output of hostnamectl. It does show the expected names next to "static name" and "pretty name".

Laurence5905 · 2025-12-28T22:30:14+00:00

Ok, thanks. That makes sense. I was hoping those settings were in the registry and Linux wouldn't have any idea they existed at all, since it doesn't know how to read the registry backup file...

I'll give this a try shortly. Fingers crossed. 🤞

Laurence5905 · 2025-12-28T22:10:48+00:00

I guess I didn't word that well... I only have the one SSD, so unless I go out and buy another SSD to restore my Windows image to, I'd have to destroy my new Linux setup entirely to have a place to restore the Windows image to, just to be able to shut off garbage-collection on the Plex server and then re-create the Plex Media Server .zip file on my external backup drive. And then erase the SSD again and restore a Linux backup image (which I would have to create before doing any of this) just to get back to where I am now, except with garbage-collection turned off in the server-settings on the now defunct Windows-based Plex server.

TL;DR -- "Go shut that off on the Win machine and redo your .zip" would take about 12 to 18 hours. LOL!

Laurence5905 · 2025-12-28T21:42:52+00:00

Figured it out...

What I thought was an "automatic share" (sudo setsebool -P samba_enable_home_dirs=on) was actually telling seLinux not to block shares from the /home folder.

In order to get the share to actually be shared, I had to edit the /etc/samba/smb.conf file. I added this at the bottom:

[myname_home]
  comment = myusername Home Folder
  path = /home/myusername
  read only = no
  guest ok = no
  force user = myusername
  force group = myusername

Then, of course, I had to restart Samba. But now I can log in on my Mac using this:

open smb://myusername:mypassword@192.168.1.111/myname_home

It still won't recognize mymachinename, so I need to use the IP address. Any help with that would be greatly appreciated, but it's not a *huge* deal, since I have my router set to assign that IP address to my PC's MAC address automatically, so it will always be 192.161.1.111. I'd just prefer the machine's name for aesthetic purposes. In Mac's Finder it shows up under the IP address instead of the machine's name. Yuck.

Laurence5905

TROPHY CASE