@cameron @adam I know that if my LAN’s DNS blips Umbrel pretty much shits the bed until a restart….it makes thousands of bad DNS calls until it has been restarted.

@suorcd @cameron I'll try a restart

@adam If you can ssh to your Umbrel, you can try to stop/start ipfspodcasting with...

~/umbrel/scripts/app stop ipfs-podcasting

then...

~/umbrel/scripts/app start ipfs-podcasting

...but if the app is happily trying every 10 minutes, I'd think it's a network issue.

@adam @cameron stopping and starting the umbrel services, pretty much rebuilds the docker network on the computer running the services

@suorcd Good to know. Is it the same as my app killing its main process (which triggers docker to restart the container)?

I've considered a "reset" button in the ipfs podcasting app ui to restart the process. Or if I'm smart enough : ) auto detect a major issue and reset itself.

@cameron that is a tough 1. For me, I don’t like things being too ‘smart’. Though with the audience you’re trying to reach, keeping thing working is more important.

I don’t know what happens to the docker network if the container restarts; in general it can be different than a stop and start.

If possible, try to log when the app has been reset by the button.
And if you get to the point of ‘auto detect’ make sure to log that the state was observed and that corrective actions are happening.

@suorcd I agree on keeping it simple. I've been seeing nodes get "stuck" and stop requesting, but it's hard to know why. For all I know, their cat tripped over the cord.

I've also seen IPFS wait forever when it can't find a file on the network. Need to add some sort of reset after several hours to "kick" the node hoping it will recover.