-
@malvim arm64 is only available on the rPi 4 as far as I recall.
armhf is for the previous models as they are 32bit ARM chips.It would be cool if both were supported and autodetected, but you should be aware of the arch differences between the different models.
-
@robi Yeah, I don't know much about the different architectures, and at present I don't have access to any earlier armhf model, so I'll keep pushing with what I have for now. Maybe if we can suport the arm64 rPi 4 to start, some modifications (like explicitly handling architecture information, different boot locations and whatnot) will help us deliver cloudron to other models more easily.
-
Just keeping everything relating to the rpi setup in this thread:
So I finished setting up, went to https://<ip> like
cloudron-setupsays, and started domain setup. As per the other thread, I set up my IP to the interface I'm using (wlan0). I'm using Amazon AWS as a domain provider, and set up the keys and such.So cloudron was able to create the DNS records (using a subdomain, like
pi.mydomain.com, which should - and does - create an A recordmy.pi.mydomain.compointing to my192.168internal IP).Afterwards, though, cloudron is never able to check for the records, as I cannot seem to resolve the
my.pidomain from inside the pi.Other stuff that happens:
sudoalways sayssudo: unable to resolve host ubuntu, even though it does change user to root no problem;ubuntuis the default hostname on a bare ubuntu 18.04 install on the pi;- I can
digother domains that are already hosted on my zone, and get corret responses.dig- ing for themy.pidomain either times out with a "no server could be reached" message, or, when I do it RIGHT AFTER a successfuldigto other domain, returns an "empty" response (with a line indicating 0 answers, like this:;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1)
I'm a bit over my skill level on this, so if anyone could chime in, id'd be greatly appreciated. Either with an idea on what might be going on, or maybe something I could do/check/run to get mor info on what might be going on.
Thanks!
-
@malvim said in Cloudron on a Raspberry pi?:
sudo: unable to resolve host ubuntu
This is expected and has nothing to do with arm. To get over that you have to setup the hostname correctly. In your case the hostname is still set to the default
ubuntuwhereas following your example it has to bemy.pi.mydomain.com -
It looks like the blocking issue is the DNS does not work? Does
host my.pi.mydomain.comandhost my.pi.mydomain.com 127.0.0.1work on the pi? -
If there's nothing private in it; could you post your /etc/hosts file?
-
Yup, so I'm testing it again from scratch.
@jamesgallagher, here's the entire contents of my
/etc/hostsright after runningcloudron-setup, but before setting up the domain in the browser:127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts@girish, the record is already there with the previous IP, and right now I'm just after
cloudron-setup, but beforesetupdns.htmlon the browser. I've ran a bunch of commands, here are the results:host my.pi.<mydomain.com>- not foundhost my.pi.<mydomain.com> 127.0.0.1- not foundhost www.google.com 127.0.0.1- ok (huh, unbound seems to be somewhat working)host code.<mydomain.com> 127.0.0.1(gitea instance on production cloudron) - OK!host my.<mydomain.com> 127.0.0.1(production cloudron admin) - NOT FOUND! (wat?)
And I ran
host my.pi.<mydomain.com>on my local machine, outside the pi, and it works and returns the old record (192.168.0.109from my previous attempt).I'm now setting up DNS in the browser, just to check what happens, I'll re-run the commands and post here.
-
Okay, so some weird stuff seems to be going on with the DNS lookup thing, I think. Here's what happened after running cloudron domain setup (
setupdns.htmlon the browser):I ran it pointing to a subdomain of my domain (
pi.<mydomain.com>), and pinted it to a network interface (wlan0, in this pi's case), as @girish suggested. So I'm tailing/home/yellowtent/platformdata/logs/box.log, and here's what I see:2020-10-07T23:43:30.489Z box:dns/waitfordns waitForDns (try 20): my.pi.<mydomain.com> to be 192.168.0.6 in zone <mydomain.com> 2020-10-07T23:43:30.497Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has A record at 205.251.196.70 2020-10-07T23:43:30.498Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has A record at 205.251.199.85 2020-10-07T23:43:30.500Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has A record at 205.251.192.234 2020-10-07T23:43:30.501Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has A record at 205.251.195.139 2020-10-07T23:43:35.499Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has CNAME record at 205.251.196.70 2020-10-07T23:43:35.501Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has CNAME record at 205.251.199.85 2020-10-07T23:43:35.503Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has CNAME record at 205.251.192.234 2020-10-07T23:43:35.504Z box:dns/waitfordns resolveIp: Checking if my.pi.<mydomain.com> has CNAME record at 205.251.195.139 2020-10-07T23:43:35.516Z box:dns/waitfordns isChangeSynced: NS ns-1094.awsdns-08.org (205.251.196.70) errored when resolve my.pi.<mydomain.com> (A): Error: queryCname ENODATA my.pi.<mydomain.com> 2020-10-07T23:43:35.516Z box:dns/waitfordns waitForDns: my.pi.<mydomain.com> not done ns: ["ns-1094.awsdns-08.org","ns-1877.awsdns-42.co.uk","ns-234.awsdns-29.com","ns-907.awsdns-49.net"] 2020-10-07T23:43:35.525Z box:dns/waitfordns isChangeSynced: NS ns-1877.awsdns-42.co.uk (205.251.199.85) errored when resolve my.pi.<mydomain.com> (A): Error: queryCname ENODATA my.pi.<mydomain.com> 2020-10-07T23:43:35.629Z box:dns/waitfordns isChangeSynced: NS ns-234.awsdns-29.com (205.251.192.234) errored when resolve my.pi.<mydomain.com> (A): Error: queryCname ENODATA my.pi.<mydomain.com> 2020-10-07T23:43:35.635Z box:dns/waitfordns isChangeSynced: NS ns-907.awsdns-49.net (205.251.195.139) errored when resolve my.pi.<mydomain.com> (A): Error: queryCname ENODATA my.pi.<mydomain.com>So I go to my LOCAL machine to check the records:
$ host my.pi.<mydomain.com> my.pi.<mydomain.com> has address 192.168.0.6 $ host my.pi.<mydomain.com> ns-1094.awsdns-08.org Using domain server: Name: ns-1094.awsdns-08.org Address: 2600:9000:5304:4600::1#53 Aliases: my.pi.<mydomain.com> has address 192.168.0.6 $ host ns-1094.awsdns-08.org ns-1094.awsdns-08.org has address 205.251.196.70 ns-1094.awsdns-08.org has IPv6 address 2600:9000:5304:4600::1 $ host my.pi.<mydomain.com> 205.251.196.70 ;; connection timed out; no servers could be reachedSo it seems when I look up the records using Amazon's DNS server IP's instead of their names, I can't look them up! EVEN ON MY LOCAL MACHINE! I have no idea what might be going on. Then, going back to the pi:
$ host my.pi.<mydomain.com> ns-1094.awsdns-08.org Using domain server: Name: ns-1094.awsdns-08.org Address: 2600:9000:5304:4600::1#53 Aliases: my.pi.<mydomain.com> has address 192.168.0.6 $ host my.pi.<mydomain.com> 205.251.196.70 ;; connection timed out; no servers could be reached $ host my.pi.<mydomain.com> 127.0.0.1 ;; connection timed out; no servers could be reached $ host my.pi.<mydomain.com> localhost ;; connection timed out; no servers could be reachedSo... Yeah, this is where I'm at right now. Totally at a loss hahah! NO IDEA what might possibly be going on now...
-
@malvim Check the unbound logs maybe? I think in
journalctl -u unbound -
@girish meh, I can't see anything wrong
Oct 08 03:53:12 ubuntu systemd[1]: Started Unbound DNS Resolver. Oct 08 03:53:12 ubuntu unbound[29715]: [29715:0] notice: init module 0: subnet Oct 08 03:53:12 ubuntu unbound[29715]: [29715:0] notice: init module 1: validator Oct 08 03:53:12 ubuntu unbound[29715]: [29715:0] notice: init module 2: iterator Oct 08 03:53:12 ubuntu unbound[29715]: [29715:0] info: start of service (unbound 1.6.7). Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: service stopped (unbound 1.6.7). Oct 08 03:54:49 ubuntu systemd[1]: Stopping Unbound DNS Resolver... Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: server stats for thread 0: 35 queries, 1 answers from cache, 34 recursions, 0 prefetch, 0 rejected by ip ratelimiting Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: server stats for thread 0: requestlist max 18 avg 10.6765 exceeded 0 jostled 0 Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: average recursion processing time 12.169607 sec Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: histogram of recursion processing times Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: [25%]=0.371371 median[50%]=1.375 [75%]=25.3333 Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: lower(secs) upper(secs) recursions Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: 0.131072 0.262144 3 Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: 0.262144 0.524288 3 Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: 0.524288 1.000000 1 Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: 1.000000 2.000000 4 Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: 16.000000 32.000000 3 Oct 08 03:54:49 ubuntu systemd[1]: Stopped Unbound DNS Resolver. Oct 08 03:54:49 ubuntu unbound[29715]: [29715:0] info: 32.000000 64.000000 3 -- Reboot -- Oct 08 03:54:55 ubuntu systemd[1]: Started Unbound DNS Resolver. Oct 08 03:54:56 ubuntu unbound[2090]: [2090:0] notice: init module 0: subnet Oct 08 03:54:56 ubuntu unbound[2090]: [2090:0] notice: init module 1: validator Oct 08 03:54:56 ubuntu unbound[2090]: [2090:0] notice: init module 2: iterator Oct 08 03:54:56 ubuntu unbound[2090]: [2090:0] info: start of service (unbound 1.6.7).I disabled ipv6 on boot just to be sure, but I see nothing. completely at a loss here.
-
So I found this code in
start.sh:echo "==> Setting up unbound" # DO uses Google nameservers by default. This causes RBL queries to fail (host 2.0.0.127.zen.spamhaus.org) # We do not use dnsmasq because it is not a recursive resolver and defaults to the value in the interfaces file (which is Google DNS!) # We listen on 0.0.0.0 because there is no way control ordering of docker (which creates the 172.18.0.0/16) and unbound # If IP6 is not enabled, dns queries seem to fail on some hosts. -s returns false if file missing or 0 size ip6=$([[ -s /proc/net/if_inet6 ]] && echo "yes" || echo "no") cp -f "${script_dir}/start/unbound.conf" /etc/unbound/unbound.conf.d/cloudron-network.confIt says unbound sometimes doesn't resolve names if ipv6 is not enabled? I had it enabled, and then disabled it thinking it might pose problems... The code seems to just set ip6 variable and nothing else, not sure whether this might be related to the problems I'm having or not.
-
@malvim I don't think IPv6 is the issue. IIRC, unbound won't even start without that flag. In your case, unbound is running.
So, I would debug this step by step: First, is DNS working at all? You can do
host my.pi.domain.com 8.8.8.8. This uses Google DNS and skips unbound altogether. Does this work? If not, we have to fix this first. Are you able to run the above command on other machines on the same network as the PI? -
@girish said in Cloudron on a Raspberry pi?:
I'm in the middle of running installation without unbound, and everything worked. I'll re-run it now with unbound again, but
host my.pi.domain.comdoes NOT work from any machine inside my home network, and does work from my main cloudron server, so I think there's more to debug here, unfortunately.
host my.pi.domain.comDOES work from my local machine, but not using Google's server, which is kind of weird.I guess I'll have to solve this issue (maybe with my ISP?) before proceeding with cloudron on the pi. Sucks.
-
Okay, so this was related to my ISP. After a few calls with tech support and buying a new router, DNS issues are gone and I was able to install cloudron from start to finish!
Now I ssh into the pi and, as expected, the first containers (mysql, turn, sftp, graphite) are continuosly restarting, since they're installed from the production amd64 images which won't work.
So now I'm thinking I'll just clone, say, the mysql addon (from
https://git.cloudron.io/cloudron/mysql-addon.git), try to build it for the pi, publish the image on my repo and try to use it, see if mysql works, and go from there. I'll try to do that tonight and get back to you guys.What do you guys say? @girish ? Is that the right path to start on?
Baby steps.
-
@malvim w00t, awesome progress. If you can create a branch of your box changes, that will help others as well. Yes, starting with one of the addon containers is a good start. They all have automatic tests, it's easy to run them as well.
