200 sats \ 5 replies \ @zeRealSchlausKwab OP 18 Jul 2022 freebie \ parent \ on: Publicly exposing lnd's gRPC port from within Umbrel? bitcoin
no i do not see any of my IPs or domains that is provided, interesting.
however i know that the cert was just regenerated because the issuance date got updated (the last one was yesterday). are the entries form tlsextraip and tlsextradomain supposed to be listed in the decoded dataset somewhere?
https://i.ibb.co/XCGcsZ3/Screenshot-2022-07-18-at-10-41-58.png
write
preview
200 sats \ 4 replies \ @lada 18 Jul 2022
Yes your extra IPs and domains you provided in tlsextraip and tlsextradomain config entries should appear in the 'SAN' subject in the certificate. If they are not there, your app will not be able to perform the necessary SSL handshake.
You need to investigate why they are not getting picked up by lnd.
I don't use Umbrel so I do not know if they have hidden config files somewhere that overrides your manual lnd.conf entires. Maybe you can check with them Umbrel folks.
reply
320 sats \ 3 replies \ @zeRealSchlausKwab OP 18 Jul 2022 freebie
dude, thank you. you helped a lot. i've asked a question on umbrel about this because it actually looks like they ignore the lnd.conf entries when generating the cert. waiting for the reply...
btw. i ended up using voltage.cloud and it works like a charm!
reply
200 sats \ 1 reply \ @lada 19 Jul 2022
I did some digging, it looks like it is a known issue with Umbrel after upgrade 0.5.0.
reply
300 sats \ 0 replies \ @zeRealSchlausKwab OP 19 Jul 2022
How the fuck did i miss this... Well, another argument for using voltage. Imagine being reliant on this for a production app and your certificates becoming void after a restart or update.
reply
0 sats \ 0 replies \ @lada 18 Jul 2022
Glad to hear it!
reply