@mattplaygamez might be better next time to create a new forum thread for separate issues.

From your video, I think what is misunderstood is, that the config files for admins will use the user/usernames from your Cloudron, so if you Cloudron user is called foobar then put that username in the config file for the admin role. Maybe we can make this clearer in the docs.

@girish Wow that worked perfectly, thank you so much! 😊

This problem is not reproducible anymore.

@nebulon I was on 6.3.5 at the time. I have since upgraded to 6.3.6.

Restarting the mail service which resolved the issue.

Thanks for the quick response!

@leggias hm getting a SIGSEGV is odd here. If you like you can enable remote SSH support and send us a mail to support@cloudron.io mentioning your dashboard domain. Then we can take a direct look at your setup to get down to the issue.

Thanks very much! I've tested it and now it works ok.

Will you be able to run your tests multi language? 😁

@girish I patched my docker.js manually, and I can confirm that port 53 is now exposed on all interfaces, as I would expect! Thanks!

@girish @nebulon
I did not follow the upgrade tutorial for 16.04 → 18.04 → 20.04 entirely because I have some minor adjustments on the server that were blocking the upgrade. Also, there was a minor issue with docker in the past, where I edited the file /etc/apt/sources.list.d/docker.list so this whole problem was my fault 🙂

@debossnow said in I don't understand Linode install of cloudron:

How do I confine different applications to be installed in the directory of the VPS I am choosing to install into?

Just to re-iterate. This is not possible with linode marketplace images, it's not designed to work that way. You cannot choose "app x" and say install it in this existing VPS. Each app always installs on a fresh linode.

DMARC is about email security. Traditionally this was about inbound protection, where DMARC can be used. Though, DMARC is more about outbound email protection.

@np_cloudron The Cloudron admin credentials and SSH credentials are different. The CLI credentials would have been set when you installed Ubuntu. Not sure where you got the ISO from, but maybe it has some default login?

The enable SSH feature is for Cloudron support team to access your server. You should be able to access your server regardless of that.

As a heads up, you cannot apply the change on your server because it's a migration script which is only run before an update. You should also not alter the database on the server because the migration script will then fail during next cloudron update.

@debossnow said in Cloudron on linode account Email ?:

The fact that Test emails out of my cloudron admin panel were successfully sent and the reply from my other website email was received back DOES THIS MEAN that the 3 email ports in my Linode instance are already OPEN?

I think this is most likely the case. The email was sent straight from your Cloudron server, this means linode opened up the ports.

Cloudron won't bypass linode email server ports unless you setup a relay (Email -> Select a domain -> Outbound). Please see https://docs.cloudron.io/email/#relay-outbound-mails

@savity you have to reboot the server using your VPS control panel or "reboot" via SSH. Do not use the reboot button in Cloudron dashboard, it doesn't work. We will make a new release most likely end of this month (6.4) where it will get fixed.

Created https://git.cloudron.io/cloudron/box/-/issues/802

@debossnow

Do I have to install a particular ADMIN PosgreSQL tool in my Cloudron application to see & administer this Mastadon database?

You can use the Weberminal to get shell like access.
On the top there will be button for Database access.

And to see all my files & their paths in a UI do I need to install a separate directory or file browser in my Cloudron application?

Like the Web Terminal you can use the File Manager to see your files.
The path in the File Manager is always /app/data/.

@fbartels said in Backup Preference: Snapshot vs S3?:

Hi @jordanurbs,

the viability of snapshots for backup has for example been discussed in https://forum.cloudron.io/topic/4161/disc-snapshots?_=1628139201934.

Yes, and to quote what @nebulon pointed out there:

@nebulon said in Disc snapshots:

Disk snapshots or VPS snapshots don't work well with Cloudron, since backups are per-app and not per-server on Cloudron. This is to be able to rollback/restore individual apps without interfering with the system or other apps running on it.

Still for a secondary fallback backup solution this can still be recommended.

That's what I do. I do Cloudron backups to a Hetzner Storage Box, plus pay Hetzner for their automated backups, plus occasionally do a snapshot too.

Although really I ought to backup to another provider too, to avoid the potential issues @girish once had with DO.

I'll probably choose another eco VPS provider to do that at some point https://ud.coop/ecovps

@girish I can't thank you enough. Had some difficulties with the -o /tmp/filename.deb (it wasn't saving the file) so I downloaded and renamed the .deb onto my computer, filezilla'd to my home directory, then used mv filename.deb /tmp

I restarted unbound and everything started running perfectly

Here is the result:
The lib files seemed untouched

root@cloudron0:/var/lib/docker# ls -al total 200 drwx--x--x 14 root root 4096 Aug 6 14:31 . drwxr-xr-x 47 root root 4096 Dec 10 2020 .. drwx------ 2 root root 4096 Dec 10 2020 builder drwx--x--x 4 root root 4096 Mar 15 03:35 buildkit drwx-----x 59 root root 12288 Aug 6 13:32 containers drwx------ 3 root root 4096 Dec 10 2020 image drwxr-x--- 3 root root 4096 Dec 10 2020 network drwx-----x 507 root root 73728 Aug 6 13:57 overlay2 drwx------ 4 root root 4096 Dec 10 2020 plugins drwx------ 2 root root 4096 Aug 6 13:57 runtimes drwx------ 2 root root 4096 Dec 10 2020 swarm drwx------ 2 root root 4096 Aug 6 13:57 tmp drwx------ 2 root root 4096 Dec 10 2020 trust drwx-----x 458 root root 61440 Aug 6 13:57 volumes -rw-r--r-- 1 root root 1394 Aug 6 14:31 'ystemctl status unbound'

I hope this worked the way it should:

root@cloudron0:/tmp# apt install -y /tmp/containerd.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'containerd.io' instead of '/tmp/containerd.deb' The following packages were automatically installed and are no longer required: amd64-microcode aufs-tools cgroupfs-mount golang-docker-credential-helpers intel-microcode iucode-tool libsecret-1-0 libsecret-common pigz python-asn1crypto python-backports.ssl-match-hostname python-cached-property python-certifi python-cffi-backend python-chardet python-cryptography python-docker python-dockerpty python-dockerpycreds python-docopt python-enum34 python-funcsigs python-functools32 python-idna python-ipaddress python-jsonschema python-mock python-openssl python-pbr python-pkg-resources python-requests python-six python-texttable python-urllib3 python-websocket python-yaml Use 'apt autoremove' to remove them. The following NEW packages will be installed: containerd.io 0 upgraded, 1 newly installed, 0 to remove and 43 not upgraded. After this operation, 129 MB of additional disk space will be used. Get:1 /tmp/containerd.deb containerd.io amd64 1.4.3-1 [28.1 MB] Selecting previously unselected package containerd.io. (Reading database ... 151160 files and directories currently installed.) Preparing to unpack /tmp/containerd.deb ... Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'docker-ce-cli' instead of '/tmp/docker-ce-cli.deb' docker-ce-cli is already the newest version (5:20.10.3~3-0~ubuntu-bionic). The following packages were automatically installed and are no longer required: amd64-microcode aufs-tools cgroupfs-mount golang-docker-credential-helpers intel-microcode iucode-tool libsecret-1-0 libsecret-common pigz python-asn1crypto python-backports.ssl-match-hostname python-cached-property python-certifi python-cffi-backend python-chardet python-cryptography python-docker python-dockerpty python-dockerpycreds python-docopt python-enum34 python-funcsigs python-functools32 python-idna python-ipaddress python-jsonschema python-mock python-openssl python-pbr python-pkg-resources python-requests python-six python-texttable python-urllib3 python-websocket python-yaml Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded. root@cloudron0:/tmp# apt install -y /tmp/docker.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'docker-ce' instead of '/tmp/docker.deb' The following packages were automatically installed and are no longer required: amd64-microcode golang-docker-credential-helpers intel-microcode iucode-tool libsecret-1-0 libsecret-common python-asn1crypto python-backports.ssl-match-hostname python-cached-property python-certifi python-cffi-backend python-chardet python-cryptography python-docker python-dockerpty python-dockerpycreds python-docopt python-enum34 python-funcsigs python-functools32 python-idna python-ipaddress python-jsonschema python-mock python-openssl python-pbr python-pkg-resources python-requests python-six python-texttable python-urllib3 python-websocket python-yaml Use 'apt autoremove' to remove them. Recommended packages: docker-ce-rootless-extras The following NEW packages will be installed: docker-ce 0 upgraded, 1 newly installed, 0 to remove and 43 not upgraded. After this operation, 121 MB of additional disk space will be used. Get:1 /tmp/docker.deb docker-ce amd64 5:20.10.3~3-0~ubuntu-bionic [24.8 MB] Selecting previously unselected package docker-ce. (Reading database ... 151174 files and directories currently installed.) Preparing to unpack /tmp/docker.deb ... Unpacking docker-ce (5:20.10.3~3-0~ubuntu-bionic) ... Setting up docker-ce (5:20.10.3~3-0~ubuntu-bionic) ... Processing triggers for systemd (237-3ubuntu10.43) ...#############################.................................] Processing triggers for ureadahead (0.100.0-21) ... root@cloudron0:/tmp# systemctl status box ● box.service - Cloudron Admin Loaded: loaded (/etc/systemd/system/box.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-08-06 18:49:09 UTC; 3min 8s ago Main PID: 21658 (node) Tasks: 11 (limit: 4915) CGroup: /system.slice/box.service └─21658 node /home/yellowtent/box/box.js Aug 06 18:49:09 cloudron0 systemd[1]: Started Cloudron Admin. Aug 06 18:49:16 cloudron0 sudo[24775]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 06 18:49:16 cloudron0 sudo[24775]: pam_unix(sudo:session): session closed for user root Aug 06 18:49:16 cloudron0 sudo[24838]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 06 18:49:16 cloudron0 sudo[24838]: pam_unix(sudo:session): session closed for user root Aug 06 18:49:47 cloudron0 sudo[29454]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 06 18:49:47 cloudron0 sudo[29454]: pam_unix(sudo:session): session closed for user root root@cloudron0:/tmp# systemctl status unbound ● unbound.service - Unbound DNS Resolver Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2021-08-06 14:45:47 UTC; 4h 7min ago Main PID: 1346 (code=exited, status=1/FAILURE) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. root@cloudron0:/tmp# unbound-anchor -a /var/lib/unbound/root.key boundroot@cloudron0:/tmp# systemctl restart unbound root@cloudron0:/tmp# systemctl status unbound ● unbound.service - Unbound DNS Resolver Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-08-06 18:53:01 UTC; 3s ago Main PID: 4506 (unbound) Tasks: 1 (limit: 4915) CGroup: /system.slice/unbound.service └─4506 /usr/sbin/unbound -d Aug 06 18:53:01 cloudron0 systemd[1]: Started Unbound DNS Resolver. Aug 06 18:53:01 cloudron0 unbound[4506]: [4506:0] notice: init module 0: subnet Aug 06 18:53:01 cloudron0 unbound[4506]: [4506:0] notice: init module 1: validator Aug 06 18:53:01 cloudron0 unbound[4506]: [4506:0] notice: init module 2: iterator Aug 06 18:53:01 cloudron0 unbound[4506]: [4506:0] info: start of service (unbound 1.6.7). root@cloudron0:/tmp# systemctl status nginx ● nginx.service - nginx - high performance web server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/nginx.service.d └─cloudron.conf Active: active (running) since Fri 2021-08-06 14:45:45 UTC; 4h 7min ago Docs: http://nginx.org/en/docs/ Main PID: 980 (nginx) Tasks: 5 (limit: 4915) CGroup: /system.slice/nginx.service ├─ 980 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf ├─29499 nginx: worker process ├─29500 nginx: worker process ├─29501 nginx: worker process └─29502 nginx: worker process Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. root@cloudron0:/tmp# systemctl status mysql ● mysql.service - MySQL Community Server Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-08-06 14:45:44 UTC; 4h 7min ago Main PID: 756 (mysqld) Tasks: 32 (limit: 4915) CGroup: /system.slice/mysql.service └─756 /usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

@qimmiq Just quickly reading the upstream docs at https://www.namecheap.com/support/api/methods/domains-dns/get-hosts/ and also the code, it looks like maybe the issue is that the domain is completely empty in namecheap? Can you add a DNS entry in namecheap (any dummy entry is fine) and try if it works after that? If it works, then I think we have to fix our code.

The fix was just to delete those config files and systemctl restart nginx. Then, in Cloudron dashboard, just Repair the app to regenerate those config files.

nginx configs became corrupt. Once we got nginx up, it uninstalled. I am putting notes on why nginx configs were corrupt at https://forum.cloudron.io/topic/5457/site-is-not-reachable

@drzero You can also check if the demo cloudron https://my.demo.cloudron.io works well for you just to rule out some networking issues (username: cloudron password: cloudron)

@mdreira probably a long term solution to embed images is to also embed it inline in the html. You can use a tool like https://base64.guru/converter/encode/image/png

@girish Boom! Back up and running 🙂
Well this was a joyous outcome. Thanks a bunch Girish!

@girish Thanks, I thought maybe I set the DNS wrong but it must be the host then

@shlomi I assume you mean the web server is installed on another server (and not on the same one as Cloudron). If that's the case, then it's fine. Otherwise, we don't support running additional applications on the same server as Cloudron.

(why is cloudron not using DNS-level validation for SSL so we will not need to open posts if we do not want/need. )

This is the case already. You have to use one of the programmatic DNS providers (and not manual or wildcard). If you do this, you don't need to open port 80. Please see https://docs.cloudron.io/certificates/#port-80-requirement

@savity Ah ok, it's fine. We can wait for someone else to report the same issue then.

@locutus said in Amazon SES - DKIM:

@micmc said in Amazon SES - DKIM:

Enter your domain name and click "create identity" that's it. No need to mess with the advanced dkim for now.

So that means I'll have to create the new DKIM DNS records regardless of the existing ones that Cloudron already created previously. Correct?

Not exactly correct 😉
I mean, if you already have "verified identity" domains then just make sure the DKIM DNS records on SES are the same registered at your DNS provider's record.

If you have legacy TXT records they should still work if they're the same. However note that they have changed for CNAME records now and they should be changed to CNAME.

Andy

@michaelf I put some notes on how to read the logs at https://docs.cloudron.io/backups/#cleanup-backups and also replied to your support ticket. Do you see any backups in linode object storage that are not listed in the logs? Otherwise, the logs do look fine to me.