How to remove / change my announced Clearnet IP (no static IP)?

Do you really want to update it dynamically? I don't think it's a good idea. Stick to Tor only.

Do you know how to access a file like ~/umbrel/app-data/lightning/data/lnd/lnd.conf ?

Hi there, Thanks for your reply. Exactlly, i do NOT want to update it dynamically. So I do not want to use clearnet at all. (Was just a initial test)
Therefore: I am not running it in Hybrid mode. (option disabled)

I looked it up several times and was directed to the " ~/umbrel/app-data/lightning/data/lnd/umbrel-lnd.conf " but with the note in the file saying:
" # This file is automatically generated by Umbrel, any changes will be overwritten. # Generated at: ..."

So then I was guided to "umbrel/app-data/lightning/data/lnd/umbrel-lnd.conf" but whatever I tried did not take effect... so I removed(/renamed) it again. 
What would you say is needed here?  (listen,nat,upnp,externalip,externalhosts,....) Couldn't figure it out yet.... Or do I have to somehow announce, that my node is now only accessablie through Tor?
Thanks and cheers, Will

For UmbrelOS 1.5, you need a separate lnd.conf file (umbrel/app-data/lightning/data/lnd/) with your specific settings, such as externalhosts=xxx
https://community.umbrel.com/t/can-t-access-lnd-conf/13502/2
Review, remove, or add to your settings in this file and restart Lightning/Node.
If that doesn't help, check your port forwarding settings on your router. Deleting the relevant ones may also help.
✌️

Hey, Thanks for the info. I tried the lnd.conf method. There was no lnd.conf so i created one next to the umbrel-lnd.conf
lnd.conf: 

[Application Options]
nat=false
externalip=

But ended up in LND service not booting with error:

Shutting down due to error in main method rev=b9ea70 err="can't set self node: unable to encode IP <nil>" 
Stopping tor controller lightning_lnd_1 
 [ERR] TORC: DEL_ONION got error: invalid arguments: unexpected code lightning_lnd_1 
 [ERR] LTND: Error stopping tor controller rev=b9ea70 err="invalid arguments: unexpected code" lightning_lnd_1 
 [INF] BTWL: Stopped waiting for wallet sync due to error: wallet shutting down 

So i removed the lnd.conf again and restarted.... so for now . . . my node still announces a old (and not reachable) IP4 address.  :(
What am I doing wrong? Is it a matter of time? Or is an empty "externalip=" wrong?
Any help would be appreciated.
Cheers, Will

Sorry, I thought you wanted to announce a new IP.

externalip must not be empty. Leave the entry blank or comment it out with #. 
Have you reactivated tor only and deactivated hybrid mode?

Check out Github to see if there's anything useful there. Maybe this? https://github.com/lightningnetwork/lnd/issues/1057#issuecomment-381048403
This was a request made in 2018. I have no idea if it was implemented. I have never tried it or found any further information about it. 

Otherwise, I can only recommend waiting and seeing until the gossip network has noticed that the old IP is no longer accessible. 

I don't like this solution either, but it's no different than when you change your fees. The changes take a while to propagate throughout the network. 
But maybe someone here or on GitHub knows more about it. 

By the way, it would probably be easiest and quickest to recreate the node, if that's an option for you.