Hi @joseph thanks for helping.
It worked indeed: export OPENAI_API_KEY=xx
in the app/data/env.sh
fix the openAI connection.
Hi @joseph thanks for helping.
It worked indeed: export OPENAI_API_KEY=xx
in the app/data/env.sh
fix the openAI connection.
It seems I have lost the backend configuration of Mealie. My OpenAI connection is not active anymore but it was working few days ago, so I guess it has something to do with yesterday update ?
I don't remember how I set up OpenAI the first time, from the doc it seems a variable to be defined in a .env or something but I have no idea where this file is in the cloudron install.
Can some help me ?
@girish I was using Tandoor before but I switched to Mealie. The UI is much better, the application has less bug and the OpenAI integration is amazing.
I haven't found a single thing that Tandoor does better than Mealie
How can I enable debug mode for Tandoor ?
Inside the container there is a dotenv file /app/code/tandoor/.env
with a symlink to /run/tandoor/env
and inside this file there is a DEBUG var:
DEBUG=0
SQL_DEBUG=0
DEBUG_TOOLBAR=0
[...]
I can change the value to 1 there but it get reset to 0 when I restart the app.
How can I start the app in DEBUG mode ?
@girish said in how to change DNS settings of my server ?:
systemd-resolved is not used at all. So, you can ignore all those related threads and configs. I would like to understand how it got to this state though? Do you think it tried to upgrade to v8 and end it up in this state?
That's possible, I don't remember if I first tried to upgrade to v8 or to change the DNS
I updated the /etc/systemd/resolve.conf
and only after did I check the /etc/resolv/conf
file, I don't know what state it was before I updated /etc/systemd/resolve.conf
thanks for the help, but this is not urgent, I can wait for the update to the v8 so I won't have to do this change twice
PS: I sent an email to the support
I tried to run the installer script manually
/tmp/box-1369022860/scripts/installer.sh:
root@4v9c:~# /tmp/box-1369022860/scripts/installer.sh
2024-08-20T20:37:22 ==> installer: Updating from 7.7.2 to 8.0.3
2024-08-20T20:37:22 ==> installer: Making sure apt is in a good state
2024-08-20T20:37:22 ==> installer: Waiting for all dpkg tasks to finish...
dpkg: dependency problems prevent configuration of mysql-server-8.0:
mysql-server-8.0 depends on mysql-server-core-8.0 (= 8.0.35-0ubuntu0.22.04.1); howe
ver:
Version of mysql-server-core-8.0 on system is 8.0.36-0ubuntu0.22.04.1.
dpkg: error processing package mysql-server-8.0 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mysql-server-8.0
2024-08-20T20:37:22 ==> installer: dpkg reconfigure failed (try 1)
Hit:1 http://ubuntu-archive.mirror.serveriai.lt jammy InRelease
Get:2 http://ubuntu-archive.mirror.serveriai.lt jammy-updates InRelease [128 kB]
Get:3 http://ubuntu-archive.mirror.serveriai.lt jammy-security InRelease [129 kB]
Get:4 http://ubuntu-archive.mirror.serveriai.lt jammy-backports InRelease [127 kB]
Get:5 http://ubuntu-archive.mirror.serveriai.lt jammy-updates/universe amd64 Package
s [1,112 kB]
Get:6 http://ubuntu-archive.mirror.serveriai.lt jammy-updates/universe Translation-e
n [260 kB]
Get:7 http://ubuntu-archive.mirror.serveriai.lt jammy-updates/universe amd64 c-n-f M
etadata [26.0 kB]
Get:8 http://ubuntu-archive.mirror.serveriai.lt jammy-security/universe amd64 Packag
es [890 kB]
Get:9 http://ubuntu-archive.mirror.serveriai.lt jammy-security/universe Translation-
en [175 kB]
Get:10 http://ubuntu-archive.mirror.serveriai.lt jammy-security/universe amd64 c-n-f
Metadata [19.0 kB]
Fetched 2,866 kB in 2s (1,742 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
170 packages can be upgraded. Run 'apt list --upgradable' to see them.
dpkg: dependency problems prevent configuration of mysql-server-8.0:
mysql-server-8.0 depends on mysql-server-core-8.0 (= 8.0.35-0ubuntu0.22.04.1); howe
ver:
Version of mysql-server-core-8.0 on system is 8.0.36-0ubuntu0.22.04.1.
dpkg: error processing package mysql-server-8.0 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mysql-server-8.0
2024-08-20T20:37:33 ==> installer: dpkg reconfigure failed (try 2)
Hit:1 http://ubuntu-archive.mirror.serveriai.lt jammy InRelease
Hit:2 http://ubuntu-archive.mirror.serveriai.lt jammy-updates InRelease
Hit:3 http://ubuntu-archive.mirror.serveriai.lt jammy-security InRelease
Hit:4 http://ubuntu-archive.mirror.serveriai.lt jammy-backports InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
170 packages can be upgraded. Run 'apt list --upgradable' to see them.
dpkg: dependency problems prevent configuration of mysql-server-8.0:
mysql-server-8.0 depends on mysql-server-core-8.0 (= 8.0.35-0ubuntu0.22.04.1); howe
ver:
Version of mysql-server-core-8.0 on system is 8.0.36-0ubuntu0.22.04.1.
dpkg: error processing package mysql-server-8.0 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mysql-server-8.0
2024-08-20T20:37:37 ==> installer: dpkg reconfigure failed (try 3)
Hit:1 http://ubuntu-archive.mirror.serveriai.lt jammy InRelease
Hit:2 http://ubuntu-archive.mirror.serveriai.lt jammy-updates InRelease
Hit:3 http://ubuntu-archive.mirror.serveriai.lt jammy-security InRelease
Hit:4 http://ubuntu-archive.mirror.serveriai.lt jammy-backports InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
170 packages can be upgraded. Run 'apt list --upgradable' to see them.
2024-08-20T20:37:42 ==> installer: apt is not ready but proceeding anyway
2024-08-20T20:37:42 ==> installer: disabling unbound
Synchronizing state of unbound.service with SysV service script with /lib/systemd/sy
stemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable unbound
2024-08-20T20:37:43 ==> installer: enabling systemd-resolved
2024-08-20T20:37:43 ==> installer: removing resolvconf
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
mysql-server-8.0 : Depends: mysql-server-core-8.0 (= 8.0.35-0ubuntu0.22.04.1) but 8
.0.36-0ubuntu0.22.04.1 is to be installed
Recommends: libhtml-template-perl but it is not going to be inst
alled
Recommends: mecab-ipadic-utf8 but it is not going to be installe
d
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a
solution).
root@4v9c:~# docker --version
Docker version 23.0.6, build ef23cbc
should I upgrade to v26.0.1 ?
also, no idea if it's related but my mounted volume keep disconnecting (the green led goes to red) and I need to manually click on the "Remount Volume" button
I'm still indeed on v7, but I can't update to v8
https://forum.cloudron.io/post/93010
I have the same issue: BoxError: update exited with code 1 signal null
and cloudron-updater.service: Failed to open /run/systemd/transient/cloudron-updater.service: No such file or directory
How can I fix it ?
I tried to changed the /etc/unbound/unbound.conf.d/cloudron-network.conf
adding this:
# Forward all DNS queries to Quad9 DNS
forward-zone:
name: "."
forward-addr: 9.9.9.9
forward-addr: 149.112.112.112
but request are still going to 212.24.109.143
and not 9.9.9.9
what service is managing the /etc/resolve.conf file ?
here are all my files:
/etc/systemd/resolved.conf:
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the resolved.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
#
# See resolved.conf(5) for details.
[Resolve]
DNS=9.9.9.9 9.9.9.10
/etc/resolv.conf:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
nameserver 212.24.109.143
nameserver 80.208.225.143
/run/systemd/resolve/resolv.conf:
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 9.9.9.9
nameserver 9.9.9.10
search .
Running resolvectl status
yield:
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
DNS Servers: 9.9.9.9 9.9.9.10
Link 2 (ens3)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (docker0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 4 (br-e8030366a286)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 6 (veth13a1cdd)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 8 (vethf77db43)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverT
showing that resolv.conf is in mode: foreign
what service manage resolv.conf
in cloudron ?
How do I do that ? If I change the file /etc/resolv.conf
to add the line
nameserver 127.0.0.53
It get overwritten at reboot and the line is deleted
I did restart systemd-resolved service but doesn't seem to work.
After doing so the content of /etc/resolv.conf
is :
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
nameserver 212.24.109.143
nameserver 80.208.225.143
Shouldn't it be 9.9.9.9 as specified in the /etc/systemd/resolve.conf
file ?
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file, or by creating "drop-ins" in
# the resolved.conf.d/ subdirectory. The latter is generally recommended.
# Defaults can be restored by simply deleting this file and all drop-ins.
#
# Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
#
# See resolved.conf(5) for details.
[Resolve]
DNS=9.9.9.9 9.9.9.10
Cloudron doc says All apps and services use systemd-resolved for name resolution. You can configure systemctl-resolved as required by your network
So the above should have work isn't it ?
no I'm using time4vps.
I tried edit the file /etc/systemd/resolve.conf
with this:
[Resolve]
DNS=9.9.9.9 9.9.9.10
but it doesn't seem to work.
Is there something else I should do? I don't really understand the unbound
DNS configuration in this doc: https://docs.cloudron.io/networking/#dns
This doc seems to be for internal name resolution of my servers apps, like (app1.my-cloudron.com)
What I want is changing the DNS for external name resolution. For instance, instead of using google DNS 8.8.8.8 I want to use 9.9.9.9
I tried to shh and edit the /etc/resolv/conf file but the file does not exists and if I try to create one with sudo vim /etc/resolv/conf
I have a error: E212: Can't open file for writing
When I ssh I see this, so I wonder if it is somehow cloudron also managing the resolv/conf file ?
The list of available updates is more than a week old.
To check for new updates run: sudo apt update
**********************************************************************
NOTE TO CLOUDRON ADMINS
-----------------------
Please do not run apt upgrade manually as it will update packages that
Cloudron relies on and may break your installation. Ubuntu security updates
are automatically installed on this server every night.
Read more at https://docs.cloudron.io/security/#os-updates
For help and more information, visit https://forum.cloudron.io
**********************************************************************
is it something I can do from cloudron or must I ssh into the server ?
The current DNS is blocking a torrent tracker URL.
I need to change the DNS to Quad9:
IP v4: 9.9.9.9 / 9.9.9.10
IP v6: 2620:fe::9 / 2620:fe::10
How can change the DNS for the whole server ? Or for Transmission app ?
docker system prune -a
didn't delete anything
There is only 35 Mb in the /home/yellowtent/platformdata/logs
Any idea what is this docker/overlay2
that is taking all the space in the /var/lib folder ?
I'm going to increase to 80Gb...