Cloudron Forum

Fixed it myself. I had to

mv /etc/resolv.conf /etc/resolv.conf.orig

and then add a /etc/resolv.conf with content

nameserver 1.1.1.1
nameserver 8.8.8.8

Hello support,
I am getting a DNS error after I upgraded Ubuntu from 22.04 to 24.04:

root@xxx:~# host releases.cloudron.io 127.0.0.1
;; 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

This is a Hetzner VPS with netplan as follows:

root@xxx:~# cat /etc/netplan/50-cloud-init.yaml 
# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    ethernets:
        eth0:
            addresses:
            - 2a01:xxx:xxxx:xxxx::1/64
            dhcp4: true
            gateway6: fe80::1
            match:
                macaddress: xx:00:00:xx:xx:xx
            set-name: eth0

resolvectl does not run:

root@xxx:~# resolvectl
Command 'resolvectl' not found, but can be installed with:
apt install systemd-resolved  # version 255.4-1ubuntu8.4, or
apt install systemd           # version 255.4-1ubuntu8.4

System info:

root@xxx:~# cloudron-support --troubleshoot
Vendor: Hetzner Product: vServer
Linux: 6.8.0-41-generic
Ubuntu: noble 24.04
Processor: Intel Xeon Processor (Skylake, IBRS)
BIOS NotSpecified  CPU @ 2.0GHz x 2
RAM: 3911724KB
Disk: /dev/sda1        15G
[OK]    node version is correct
[OK]    docker is running
[OK]    MySQL is running
[OK]    nginx is running
[OK]    dashboard cert is valid
[OK]    dashboard is reachable via loopback
[OK]    box v8.0.4 is running
[OK]    netplan is good
[WARN]  systemd-resolved is not in use. see 'systemctl status systemd-resolved'
grep: /etc/resolv.conf: No such file or directory
[WARN]  /etc/resolv.conf is not using systemd-resolved. it is missing the line 'nameserver 127.0.0.53'
[FAIL]  DNS is not resolving
;; communications error to ::1#53: connection refused
;; communications error to ::1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; no servers could be reached

root@xxx:~# systemctl status systemd-resolved
Unit systemd-resolved.service could not be found.
root@warkalla:~#

Kindly help

Thanks, that worked!

I followed the upgrade guide
After a reboot, I get this:

root@xx:/home/yellowtent/box/scripts# ./cloudron-support --troubleshoot
Vendor: Hetzner Product: vServer
Linux: 5.15.0-119-generic
Ubuntu: jammy 22.04
Processor: Intel Xeon Processor (Skylake, IBRS) x 2
RAM: 3907512KB
Disk: /dev/sda1        14G
[OK]    node version is correct
[OK]    docker is running
[OK]    MySQL is running
[FAIL]  nginx is down. Removing extraneous dashboard domain configs ...
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for details.

Systemctl shows this:

root@xxx:/home/yellowtent/box/scripts# systemctl status nginx.service
× nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/nginx.service.d
             └─cloudron.conf
     Active: failed (Result: exit-code) since Tue 2024-08-27 18:58:54 UTC; 8s ago
       Docs: man:nginx(8)
    Process: 6795 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
        CPU: 5ms

Aug 27 18:58:54 xxx systemd[1]: Starting A high performance web server and a reverse proxy server...
Aug 27 18:58:54 xxx nginx[6795]: nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)
Aug 27 18:58:54 xxx nginx[6795]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 27 18:58:54 xxx systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Aug 27 18:58:54 xxx systemd[1]: nginx.service: Failed with result 'exit-code'.
Aug 27 18:58:54 xxx systemd[1]: Failed to start A high performance web server and a reverse proxy server.

Is there a backup of this conf file somewhere or can it be recreated?
Thank you!

@joseph Thanks, that was it! It's all working now.

@joseph there is nothing in /etc/netplan on my host.
I am on a fixed IP set up with /etc/network/interfaces

Hi @joseph, after restarting Unbound, my resolve.conf looks like this:

nameserver 127.0.0.53
options edns0 trust-ad
search .

Name resolution and the appstore work if I change the IP to 127.0.0.1, but not if I leave it at 127.0.0.53
With that temporary manual fix, I was able to upgrade to 8.0.3. Name resolution is not working. However, unbound is working now.

If I reboot with 8.0.3, the /etc/resolv.conf reads 127.0.0.53 again.

My apps are not working now, because they need to download some icons:

An error occurred during the configure operation: Network Error: Network error downloading icon : getaddrinfo EAI_AGAIN api.cloudron.io

How do I fix this please?

@joseph sorry I thought i updated but I did not. So i am still on 7.7.2 (but I cannot change the subject). I just tried to update with the /etc/resolv.conf set to what you suggested, but it failed and is still on 7.7.2

Hey thanks for the quick reply. I am looking at another VM at the same provider, and there is nothing in /etc/netplan either.

In the working machine's resolv.conf I see this:

nameserver 8.8.8.8
nameserver 1.1.1.1

In my Cloudron's resolv.conf, I see this:

nameserver 127.0.0.53
options edns0 trust-ad
search .

Do I overwrite it with your suggestion ("simply use nameserver 1.1.1.1") or do I append it?

Hello, since a few days, my backups are failing and I am getting "Email not configured properly".
Turns out that name resolution does not work at all.

I tried to troubleshot unbound as per the Cloudron docs, but that won't work, as I discovered the /etc/netplan folder is completely empty.

I am running on a small VPS on vpshostingservice.co, Ubuntu 22.04. Cloudron 7.7.2 - I cannot upgrade because this is happening

Kindly assist.

Ja Prost dann!

Hey @nebulon thanks for letting us know you can reproduce the issue. I will keep an eye on this thread but probably move away from using Koel for the time being.
Again, thanks for all your help and time!

I installed the koel/docker image on a test system and all works well.
It finds/displays the covers properly. I am not sure if Koel is using the cover.jpg file or the embedded cover file.
I didn't even need to set up Spotify integration.

On this setup, there is a docker volume called docker_covers. In that volume, there are 2 files for each album: *.jpeg and *.thumb.jpeg

I don't know enough about how Cloudron is managing these volumes for Koel - can you tell me where the equivalent folder/volume for covers on a Cloudron would be?

I have followed the steps in
https://docs.koel.dev/3rd-party.html#spotify
but I did not set a callback URL at all.

Maybe it's just Koel not quite working well. Let me set up a non-Cloudron Koel docker instance on another VPS and play around with it.
Generally, all my mp3's contain cover art and each album folder also contains a cover.jpg file, so I shouldn't even need Spotify integration.
I'll report back with my findings

Hi @girish this is unfortunately not quite resolved - the errors are gone, but I do not get any covers showing in Koel. (I only had time to look at this today)

Here's my setup:
S3FS mount point on /mnt/music with the Read-Only flag

In Cloudron->Volumes I have a volume called "music" pointing to /mnt/music

In Koel-Terminal I created a symlink in /app/data/library:

lrwxrwxrwx 1 www-data www-data   13 May  8 16:29 music -> /media/music/

In the Koel admin interface, I have set up the media folder to point to /app/data/library

Scanning the library from Koel-Terminal via

php artisan koel:sync

picks up the mp3s but not the covers.

@girish thank you that did the trick

Hi,
Koel 6.11.2

Enabled Spotify integration as per https://docs.koel.dev/3rd-party.html#spotify

by editing /app/data/env and adding lines for SPOTIFY_CLIENT_ID and SPOTIFY_CLIENT_SECRET

Issue: covers do not show

/app/data/storage/logs/laravel/log shows an error repeatedly:

2023-05-05 21:48:00] production.ERROR: Failed attempt {"error":"[object] (Intervention\Image\Exception\NotWritableException(code: 0): Can't write image data to path (/app/code/public/img/covers/5a1d28813cebd94da689576867f617a31abe3bde.jpeg) at /app/code/vendor/intervention/image/src/Intervention/Image/Image.php:150)
[stacktrace]
#0 /app/code/app/Services/ImageWriter.php(36): Intervention\Image\Image->save()
#1 /app/code/app/Services/MediaMetadataService.php(38): App\Services\ImageWriter->write()
#2 /app/code/app/Helpers.php(50): App\Services\MediaMetadataService->App\Services\{closure}()
#3 /app/code/app/Services/MediaMetadataService.php(46): attempt()
#4 /app/code/app/Services/FileSynchronizer.php(119): App\Services\MediaMetadataService->writeAlbumCover()
#5 /app/code/app/Helpers.php(50): App\Services\FileSynchronizer->App\Services\{closure}()
#6 /app/code/app/Services/FileSynchronizer.php(131): attempt()
#7 /app/code/app/Services/FileSynchronizer.php(94): App\Services\FileSynchronizer->tryGenerateAlbumCover()
#8 /app/code/app/Services/MediaSyncService.php(51): App\Services\FileSynchronizer->sync()
#9 /app/code/app/Console/Commands/SyncCommand.php(68): App\Services\MediaSyncService->sync()
#10 /app/code/app/Console/Commands/SyncCommand.php(46): App\Console\Commands\SyncCommand->syncAll()
#11 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): App\Console\Commands\SyncCommand->handle()
#12 /app/code/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#13 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure()
#14 /app/code/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(37): Illuminate\Container\BoundMethod::callBoundMethod()
#15 /app/code/vendor/laravel/framework/src/Illuminate/Container/Container.php(661): Illuminate\Container\BoundMethod::call()
#16 /app/code/vendor/laravel/framework/src/Illuminate/Console/Command.php(183): Illuminate\Container\Container->call()
#17 /app/code/vendor/symfony/console/Command/Command.php(291): Illuminate\Console\Command->execute()
#18 /app/code/vendor/laravel/framework/src/Illuminate/Console/Command.php(153): Symfony\Component\Console\Command\Command->run()
#19 /app/code/vendor/symfony/console/Application.php(1014): Illuminate\Console\Command->run()
#20 /app/code/vendor/symfony/console/Application.php(301): Symfony\Component\Console\Application->doRunCommand()
#21 /app/code/vendor/symfony/console/Application.php(171): Symfony\Component\Console\Application->doRun()
#22 /app/code/vendor/laravel/framework/src/Illuminate/Console/Application.php(102): Symfony\Component\Console\Application->run()
#23 /app/code/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(155): Illuminate\Console\Application->run()
#24 /app/code/artisan(35): Illuminate\Foundation\Console\Kernel->handle()
#25 {main}
"}

Thanks for looking into it!

@marcusquinn I found it was an issue with idrivee2. Moved bucket and backups to another region and all started to work again

@marcusquinn how happy are you with idrivee2 these days? I started a trial on Thursday and all was working well, but since Friday I am getting errors left right and center. Opened a support call and it's with their back end team. I am waiting for a response from them, hopefully Monday.

i'd love to see this one