Cloudron Forum

I did check and unbound anchor is installed

It looks like when I go into services that Unbound is constantly booting and will not fully boot

@nebulon, yes i have looked into the document link and that is what I have done and still nothing

2025-06-13T13:50:40+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T14:17:54+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T14:47:51+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T15:10:51+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T15:22:49+00:00 cloudron unbound[5840]: [5840:0] info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN
2025-06-13T15:44:49+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T16:17:52+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T16:47:51+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T17:43:33+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T18:17:52+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T18:47:51+00:00 cloudron unbound[5840]: [5840:0] info: generate keytag query _ta-4f66. NULL IN
-- Boot 2d867c0dde664a7e9d66bc2643977b03 --
2025-06-13T18:59:46+00:00 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...

2025-06-13T18:59:46+00:00 cloudron unbound[1139]: [1139:0] notice: init module 1: validator
2025-06-13T18:59:46+00:00 cloudron unbound[1139]: [1139:0] notice: init module 2: iterator
2025-06-13T18:59:46+00:00 cloudron unbound[1139]: [1139:0] info: start of service (unbound 1.19.2).
2025-06-13T18:59:46+00:00 cloudron systemd[1]: Started unbound.service - Unbound DNS Resolver.
2025-06-13T18:59:51+00:00 cloudron unbound[1139]: [1139:0] info: generate keytag query _ta-4f66. NULL IN
-- Boot b2dadc371f7f43ee942b554c9fb98825 --
2025-06-13T19:03:47+00:00 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
2025-06-13T19:03:48+00:00 cloudron unbound[1204]: [1204:0] notice: init module 0: subnetcache
2025-06-13T19:03:48+00:00 cloudron unbound[1204]: [1204:0] notice: init module 1: validator
2025-06-13T19:03:48+00:00 cloudron unbound[1204]: [1204:0] notice: init module 2: iterator
2025-06-13T19:03:48+00:00 cloudron unbound[1204]: [1204:0] info: start of service (unbound 1.19.2).
2025-06-13T19:03:48+00:00 cloudron systemd[1]: Started unbound.service - Unbound DNS Resolver.
2025-06-13T19:03:54+00:00 cloudron unbound[1204]: [1204:0] info: generate keytag query _ta-4f66. NULL IN
2025-06-13T19:30:16+00:00 cloudron unbound[1204]: [1204:0] info: generate keytag query _ta-4f66. NULL IN

@nebulon

Can I get the locations of the unbound logs and the config again?

Hello,

I am having issues with Unbound as I have to constantly restart it to get the PTR4 Record to pass. I did call my ISP who owns the IP I am using and found out the caching DNS Servers I get from them are having issues with PTR, so I am on new DNS Servers now. But the problem is that when I restart unbound, the PTR4 record resolves and is green. But after 1 minute it fails again and I have to keep restarting Unbound, which I think is crazy. What can be done with the unbound service?

I am on Ubuntu Server 24.04.2 LTS with Cloudron Installed version 8.3.2

I can confirm that the cloudron-network.config file is identical to the one you provided.

sudo lsof -i :53
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-r 767 systemd-resolve 14u IPv4 12307 0t0 UDP _localdnsstub:domain
systemd-r 767 systemd-resolve 15u IPv4 12308 0t0 TCP _localdnsstub:domain (LISTEN)
systemd-r 767 systemd-resolve 16u IPv4 12309 0t0 UDP _localdnsproxy:domain
systemd-r 767 systemd-resolve 17u IPv4 12310 0t0 TCP _localdnsproxy:domain (LISTEN)
unbound 1120 unbound 3u IPv4 10993 0t0 UDP localhost:domain
unbound 1120 unbound 4u IPv4 10994 0t0 TCP localhost:domain (LISTEN)
unbound 1120 unbound 5u IPv4 10995 0t0 UDP cloudron:domain
unbound 1120 unbound 6u IPv4 10996 0t0 TCP cloudron:domain (LISTEN)

sudo netstat -tulpn | grep -i -E '.:53\s+.$'
tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 767/systemd-resolve
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 767/systemd-resolve
tcp 0 0 127.0.0.150:53 0.0.0.0:* LISTEN 1120/unbound
tcp 0 0 172.18.0.1:53 0.0.0.0:* LISTEN 1120/unbound
udp 0 0 172.18.0.1:53 0.0.0.0:* 1120/unbound
udp 0 0 127.0.0.150:53 0.0.0.0:* 1120/unbound
udp 0 0 127.0.0.54:53 0.0.0.0:* 767/systemd-resolve
udp 0 0 127.0.0.53:53 0.0.0.0:* 767/systemd-resolve

@james How do we do a manual restore for the app? Yes, I can download the backup I took from my File Server and make sure it is valid, which I confirmed it is.

@joseph I also noticed that the unbound is stuck in restarting status and will not fully start. Here are the logs for the last 2 minutes:

May 22 13:52:29 cloudron systemd[1]: unbound.service: Deactivated successfully.
May 22 13:52:29 cloudron systemd[1]: Stopped unbound.service - Unbound DNS Resolver.
May 22 13:52:29 cloudron systemd[1]: unbound.service: Consumed 4.835s CPU time, 9.9M memory peak, 0B memory swap peak.
May 22 13:52:29 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
May 22 13:52:29 cloudron unbound[569109]: [569109:0] notice: init module 0: subnetcache
May 22 13:52:29 cloudron unbound[569109]: [569109:0] notice: init module 1: validator
May 22 13:52:29 cloudron unbound[569109]: [569109:0] notice: init module 2: iterator
May 22 13:52:29 cloudron unbound[569109]: [569109:0] info: start of service (unbound 1.19.2).
May 22 13:52:29 cloudron systemd[1]: Started unbound.service - Unbound DNS Resolver.
May 22 13:52:29 29+00:00 cloudron unbound[569109]: [569109:0] info: service stopped (unbound 1.19.2).
May 22 13:52:29 cloudron systemd[1]: Stopping unbound.service - Unbound DNS Resolver...
May 22 13:52:29 cloudron unbound[569109]: [569109:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
May 22 13:52:29 cloudron unbound[569109]: [569109:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
May 22 13:52:29 cloudron systemd[1]: unbound.service: Deactivated successfully.
May 22 13:52:29 cloudron systemd[1]: Stopped unbound.service - Unbound DNS Resolver.
May 22 13:52:29 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
May 22 13:52:29 cloudron unbound[569124]: [569124:0] notice: init module 0: subnetcache
May 22 13:52:29 cloudron unbound[569124]: [569124:0] notice: init module 1: validator
May 22 13:52:29 cloudron unbound[569124]: [569124:0] notice: init module 2: iterator
May 22 13:52:30 cloudron systemd[1]: Started unbound.service - Unbound DNS Resolver.
May 22 13:52:30 cloudron unbound[569124]: [569124:0] info: start of service (unbound 1.19.2).
May 22 13:52:30 cloudron unbound[569124]: [569124:0] info: service stopped (unbound 1.19.2).
May 22 13:52:30 cloudron systemd[1]: Stopping unbound.service - Unbound DNS Resolver...
May 22 13:52:30 cloudron unbound[569124]: [569124:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
May 22 13:52:30 cloudron unbound[569124]: [569124:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
May 22 13:52:30 cloudron systemd[1]: unbound.service: Deactivated successfully.
May 22 13:52:30 cloudron systemd[1]: Stopped unbound.service - Unbound DNS Resolver.
May 22 13:52:30 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
May 22 13:52:30 cloudron unbound[569147]: [569147:0] notice: init module 0: subnetcache
May 22 13:52:30 cloudron unbound[569147]: [569147:0] notice: init module 1: validator
May 22 13:52:30 cloudron unbound[569147]: [569147:0] notice: init module 2: iterator
May 22 13:52:30 cloudron unbound[569147]: [569147:0] info: start of service (unbound 1.19.2).
May 22 13:52:30 cloudron systemd[1]: Started unbound.service - Unbound DNS Resolver.
May 22 13:52:30 cloudron unbound[569147]: [569147:0] info: service stopped (unbound 1.19.2).
May 22 13:52:30 cloudron systemd[1]: Stopping unbound.service - Unbound DNS Resolver...
May 22 13:52:30 cloudron unbound[569147]: [569147:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
May 22 13:52:30 cloudron unbound[569147]: [569147:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
May 22 13:52:30 cloudron systemd[1]: unbound.service: Deactivated successfully.
May 22 13:52:30 cloudron systemd[1]: Stopped unbound.service - Unbound DNS Resolver.
May 22 13:52:30 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
May 22 13:52:30 cloudron unbound[569164]: [569164:0] notice: init module 0: subnetcache
May 22 13:52:30 cloudron unbound[569164]: [569164:0] notice: init module 1: validator
May 22 13:52:30 cloudron unbound[569164]: [569164:0] notice: init module 2: iterator
May 22 13:52:30 cloudron unbound[569164]: [569164:0] info: start of service (unbound 1.19.2).
May 22 13:52:30 cloudron systemd[1]: Started unbound.service - Unbound DNS Resolver.

@james I know about that document for PTR Records, but I called my ISP, since my server is self hosted, and they confirmed that the record is set and is showing correctly. They said since on MXtoolbox, that it shows properly, the issue is with Cloudron. This is why I put in the ticket. What is going on with Unbound to not recognize the PTR record from my ISP.

I did the check with 127.0.0.150 and got the following error:
Using domain server:
Name: 127.0.0.150
Address: 127.0.0.150#53
Aliases:
Host <IP Address>.in-addr.arpa not found: 2(SERVFAIL)

Hello @james

I tried two other backups that are both 12.3GB from my File Server and both got the same error.

I had to remove my server to new hardware as the server died. I took my full back of Cloudron and set it back up again and to fix the issue with Godaddy and the API Keys from not working, I had to create a new file called custom.conf in the Unbound.conf.d folder to get it working again with a restart of unbound.service using the Unbound documentation. Now, I am having the issue with the PTR4 saying it is not setup. When I did a PTR check for my IP, it comes back with my.domain.net.

I did do the following:

host -t PTR <IP address> 127.0.0.1 and it failed with:
communications error to 127.0.0.1#53: Connection refused
communications error to 127.0.0.1#53: Connection refused
No servers could be reached.

Then I did the following:
host -t PTR <IP Address> 8.8.8.8 and passed with:
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
<IP Address>.in-addr.arpa domain name pointer my.domain.net

Since that passes, what is going on with my Cloudron instance? Seems it does not want to talk.

I noticed when I log into the Ubuntu CLI, I do a sudo ufw status, it is inactive. Could that be the issue?

When I setup the new server, I used the same internal IP as the old server and all of my Firewall rules are setup the same as before for Ports 80, 443, 25, 587, and 993.

How do we go about fixing this?

Hello,

I have been restoring my Cloudron instance over to another server due to hardware failure. When I tried to restore my Lampstack App with the 12.3GB Backup, I am getting the External Error - tarExtract pipeline error: invalid stored block lengths. I am using CIFS to do this. Weird part is that it was to be fixed 8.1 and still is not fixed. How do I go about fixing this?

@d19dotca You are right in the aspect of it being a CDN style backup service. It takes your data and splits it up into 64MB segments and disperses it around their different nodes in the world. When you request to download a file from your Storj service, it can rebuild a copy of that file with only 24 of the closest nodes to your location, no matter where you are in the world. Yes, some of those segments will be in Canada.

@girish That is correct. An api module would be best to use. s3 compatible does work, but sometimes, depending on how the module is coded, it can be messy.

@girish They do support multi-part copying. I have been a customer for the past 3 years and it has been a life saver for myself and the company I work for. It is baked in with their processes and is nothing you are have to do. I do have it working using the S3 Compatibility mode and it works, but as Storj will say, it will be buggy and it is. If you talk with their developers they will work with you to add in a native plugin for Cloudron so we can connect to it and go. Trust me, it is fantastic and a great alternative to all of the other Cloud storage solutions.

I have tested the custom.php and tried mirroring the change in there and it did not take at all. This is why I need into the f.php file