Glad you are back dude, hey you can type 'exec revivesanc' and it should have the instructional command.
If not, IE if you are missing the blsprivkey, Ive learned its also pretty easy to just spend the output and recreate the sanc. But the bls priv key is in the sanc itself in the config file, and right clicking on the sanc in the home host reveals the pro-tx-id. The Sanc IP is of course, public already.
Sorry, I can’t revive my sanc Nor can I spend the transaction....
cli protx update_service 3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0 45.62.239.200:40001 579fcbc90face5e28d5312a0e0df87606f67adf62d71305701c551133d75c9d9
error code: -32603
error message:
No funds at specified address (special transaction error)
ok - I choose an address with funds
"ye9fvYw4vgHmSrVT8cd8wVLNmSBLZh7ikV": 9.93668000,
cli protx update_service 3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0 45.62.239.200:40001 579fcbc90face5e28d5312a0e0df87606f67adf62d71305701c551133d75c9d9 ye9fvYw4vgHmSrVT8cd8wVLNmSBLZh7ikV
error code: -32603
error message:
Signing transaction failed
cli walletpassphrase
error code: -15
error message:
Error: running with an unencrypted wallet, but walletpassphrase was called.