Taomyn
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
🎉 it's working and no more errors from the container being killed. @Meierschlumpf your fix looks good, thanks.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
I found the issue, my server thought the container was still starting and so killed it. I'm going to re-try the Nextcloud fix and see if that now works now that the container isn't randomly killing itself.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
No, I'm not doing anything myself, but I think you're right that something outside of the container is sending SIGTERM - I'm still looking for the reason. I have 6 or so other containers all running just fine, so it's specific to just this one.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
Seems the data is not the cause of the container error, I reverted to the backup from last night and it's still doing the same. It does complain about network performance and then shuts down
(node:16) [DEP0040] DeprecationWarning: The
punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
(node:17) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
15:M 01 Apr 2025 12:28:46.075 * 1 changes in 60 seconds. Saving...
15:M 01 Apr 2025 12:28:46.076 * Background saving started by pid 53
53:C 01 Apr 2025 12:28:46.078 * DB saved on disk
53:C 01 Apr 2025 12:28:46.078 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
15:M 01 Apr 2025 12:28:46.176 * Background saving terminated with success
2025-04-01T12:29:01.728Z warn: The callback of 'downloads' succeeded but took 37.72ms longer than expected (1000ms). This may indicate that your network performance, host performance or something else is too slow. If this happens too often, it should be looked into.
2025-04-01T12:29:01.729Z warn: The callback of 'dnsHole' succeeded but took 38.41ms longer than expected (1000ms). This may indicate that your network performance, host performance or something else is too slow. If this happens too often, it should be looked into.
Received SIGTERM. Shutting down...
I changed the log level to just warn so I could more easily see the issues.34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
I think I'm going to have to restore the data now, as I keep getting these container errors. Was anything else changed other than for the integration?
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
Back to normal, the log I managed to capture is here: https://pastebin.com/a7kB29mr
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
I'm going to have to revert back to the release container as this test one is still misbehaving and crapping out. I got some more logging which I will go through then post here, but I want to get it stable first.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
I then realised this was caused by an incorrect user name, so I tried again. Another container crash and another retry and this time it worked. Not sure what is causing the container issues. but the SSL connection is fine and also confirms that app passwords work.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
So I made progress, I deployed the new container, it started up as normal. I then tried to add the NC integration and it failed again. The container logged:
2025-04-01T06:34:49.198Z info: SIGTERM
2025-04-01T06:34:49.225Z info: ➖ Connection (1) 1006
2025-04-01T06:34:49.227Z info: ➖ Connection (0) 1006
15:M 01 Apr 2025 06:35:21.032 * 1 changes in 60 seconds. Saving...
15:M 01 Apr 2025 06:35:21.032 * Background saving started by pid 58
58:C 01 Apr 2025 06:35:21.037 * DB saved on disk
58:C 01 Apr 2025 06:35:21.038 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
15:M 01 Apr 2025 06:35:21.133 * Background saving terminated with success
So I opened a separate tab to Homarr to watch the log and this time no crash but it logged:
2025-04-01T06:36:27.482Z info: Dispatching request https://nextcloud.mydomain.com/.well-known/caldav (6 headers)
2025-04-01T06:36:27.542Z info: Dispatching request https://nextcloud.mydomain.com/remote.php/dav/ (9 headers)
2025-04-01T06:36:28.144Z error: tRPC Error with mutation on 'integration.create'
at Object.onError (/app/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:4404)
at Object.onError (/app/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:3561)
at /app/apps/nextjs/.next/server/chunks/4429.js:107:5071
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /app/apps/nextjs/.next/server/chunks/4429.js:107:7031
at async /app/apps/nextjs/.next/server/chunks/4429.js:83:785967
caused by Error: Invalid credentials
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
Sure, I will try it later today and let you know.....
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
@Slimekong did you try an app password (in your account Security section) as I am trying to do? I cannot confirm if it works as I have another issue, but for you it might be workable.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
Bug report submitted
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
Damn, I thought maybe if I uploaded the certificate itself it would work but it doesn't.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
Sure, I'll submit a report.
I also just tested with wget in the container and it fails for all my servers that use that CA. Perhaps adding the CA to the main certificate store of the container would work, as this is how I've seen it done for other projects.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
Name is, nextcloud.mydomain.com, alternates are nextcloud.mydoman.com & nextcloud
There is no subpath, just https://nextcloud.mydomain.com
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
I just double checked, the CA certificate expires 2028, the Nextcloud certificate in 2026
Yes, the same CA
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
I have SABnzbd, qBittorrent, Pi-hole, Home Assistant and Proxmox integrations all accepting certificates generated by the same CA, but of course that only worked once I had upload the CA's certificate to Homarr - which I was glad to see was an option, unlike other projects where I've had to jump through hoops to get my CA into their containers.
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
It is updated otherwise all my other services would show the same. I've seen the same message generated when the certificate CA was not trusted
34 replies
HHomarr
•Created by Slimekong on 3/23/2025 in #💬・get-help
Next Cloud Integration
I was hoping to test if an app password created against my Nextcloud account would work, but it seems the integration is not accepting my server's certificate even though its generator, my local CA's certificate is uploaded to Homarr (which works fine for other integrations)
2025-03-31T11:30:31.495Z error: tRPC Error with mutation on 'integration.create'
....
caused by TypeError: fetch failed
at node:internal/deps/undici/undici:13502:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async A (/app/apps/nextjs/.next/server/chunks/9404.js:91:145950)
at async er (/app/apps/nextjs/.next/server/chunks/9404.js:92:11517)
at async ei (/app/apps/nextjs/.next/server/chunks/9404.js:92:12989)
at async eu.login (/app/apps/nextjs/.next/server/chunks/9404.js:92:17985)
at async iG.testConnectionAsync (/app/apps/nextjs/.next/server/chunks/5537.js:134:4626)
at async nc (/app/apps/nextjs/.next/server/chunks/5537.js:134:21116)
at async /app/apps/nextjs/.next/server/chunks/5537.js:134:24176
at async l.middlewares (/app/apps/nextjs/.next/server/chunks/9404.js:137:445831)
caused by Error: certificate has expired code="CERT_HAS_EXPIRED"
at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34)
at TLSSocket.emit (node:events:518:28)
at TLSSocket._finishInit (node:_tls_wrap:1078:8)
at ssl.onhandshakedone (node:_tls_wrap:864:12)
at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17)
34 replies