-
@ Dikaios1517
2025-03-03 20:45:53
Alright, having received no response from any members of nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzdmhxue69uhk7enxvd5xz6tw9ec82c30qyfhwumn8ghj7un9d3shjtnxxaazu6t09uq3vamnwvaz7tmjv4kxz7fwdehhxarj9ehx2ap0qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qyw8wumn8ghj7cn4vd4k2apwvdhhyctrd3jjuum0vd5kzmp0qyv8wumn8ghj7un9d3shjtnrw4e8yetwwshxv7tf9uq3jamnwvaz7tmgvfezucm0wfskxmr99eek7cmfv9kz7qpqaghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2q0nxf89 support in their Discord server for the last 3 days, I'll put the question to the #Nostr community instead.
Anyone running an #Umbrel ever tried to update an app and have it sit at 99% for HOURS until you finally decide to reboot your Umbrel, only to have that app show as "Not Running" and you can't interact with it at all through the GUI?
I had this happen with NextCloud last week, and still haven't figured out how to resolve the issue. Looking at the logs for NextCloud shows the following error:
nextcloud_app_proxy_1 | Error waiting for port: "The address 'nextcloud_web_1' cannot be found"
nextcloud_app_proxy_1 | Retrying...
The above just seems to endlessly repeat.
Looking through the Umbrel OS logs for "nextcloud" returned the following result:
Mar 03 20:30:28 umbrel dockerd[503]: time="2025-03-03T20:30:28.630296620Z" level=error msg="[resolver] failed to query DNS server: 1.1.1.1:53, query: ;nextcloud_web_1.\tIN\t A" error="read udp 10.21.0.31:44480->1.1.1.1:53: i/o timeout"
Anyone have an idea of what to try in order to resolve the above?
#asknostr