@saphirata if your IP of your ISP connection (local ip) keeps changing, then you need to keep the DNS records in-sync. So for your use-case it means you have to keep adjusting the settings in Cloudflare. Maybe for a start you could disable Cloudflare proxying and use it normally as a DNS service, then configuring your domain in Cloudron to use our Cloudflare backend and enable https://docs.cloudron.io/networking/#dynamic-dns

FWIW, a great DNS tool for checking on DNS propagation progress is here: https://dnschecker.org

@girish Yes there are definitely more than 20 events, and the Next page still works to load more, it's just that dropdown to change how many records are shown at once which has an issue. I just updated to 7.0.3 so will try soon, unfortunately it seems the email logs were cleared after update, so there's no records in there at all now.

@girish yay! Haha, thank you so much!!! That one was really annoying even though minor. Lol. It happens after a Cloudron migration (not just upgrade) and stuff too FYI but I’m assuming you already knew that. Edit: actually maybe not… I also had upgraded Cloudron the very next day so I likely just saw the result of that instead. Ignore me. glad it’s fixed though!!

@girish Magic, that seems to have worked - thanks! Maybe worth considering adding this advice to the email notifications?

I have added a retry now for the startup tasks on db failures in 7.0.2

@aduthapa can you check the app logs to see if the app keeps restarting? If so try to put it first into recovery mode. In case this is not related to the app itself, do you see any errors in your browser console?

@girish Excellent, as always. Works!

@danielreyes61 If you want to use nginx directly, you should make it do https proxying and not http. nginxproxymanager seems to have generated something like this: # ------------------------------------------------------------ # paste.cloudron.space # ------------------------------------------------------------ server { set $forward_scheme https; set $server "45.63.93.50"; set $port 443; listen 80; listen [::]:80; listen 443 ssl http2; listen [::]:443 ssl http2; server_name paste.cloudron.space; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-2/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-2/privkey.pem; access_log /data/logs/proxy-host-2_access.log proxy; error_log /data/logs/proxy-host-2_error.log warn; location / { # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } And proxy.conf is like this: set $upstream $forward_scheme://$server:$port$request_uri; add_header X-Served-By $host; proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Real-IP $remote_addr; proxy_pass $upstream; Just pasting them to give you some ideas.

@silvermaw no worries, happens to the best

@nebulon thanks, i did get this figured out with zulip's docs on reverse proxying and using certbot on the cloudron host again but I know I'm playing with fire. I get why this isn't a common use case, I can't imagine a lot of people host at home

@khadanja Is your idea to forward all queries ? The example config you pasted will only forward DNS queries for cloudron.lan (sic). You need the config in https://forum.cloudron.io/topic/5756/custom-dns-server-in-local-network/2 to forward all queries to your router.

@savity I can't reproduce this. Do you see any error on the minio side?

@nebulon I updated the server to v7.0.1 and then rebooted, now when I'm login through the incognito tab in chrome browser, user management is working fine, maybe this is due to cacheing...

@ascua If the new instance is in your house then you need to port-forward (or if your router/modem support - DMZ (AKA 1:1 NAT) ) the server.

@fortytwo said in How to delete unused docker images ?: Scaleway S3 Object Storage with 75GB free Is this for your backup? Cloudron does not backup images (and code), just your data. From your screenshot, it's only going to take 1.13G (nextcloud) + 6.5M (bitwarden) + 520K (box) + 212K (email). So, it's way less than 2GB per backup. If you store like 30 full backups, it's still under your object storage. We use what is called immutable infrastructure for this if you want to learn more.

@nebulon Thanks. I have solved this issue. The initial python version is 3.8, after switching to Python 2.7 the issue was solved. Reference this link: https://linuxconfig.org/ubuntu-20-04-python-version-switch-manager

@scooke yes, you can mix between Cloudron's automation and manual DNS changes. In fact, that's the normal and only mode of operation. The automation is only adding and removing things that you would have to do normally outside Cloudron. For example, when you install an app, you have to setup A records. When you uninstall an app, you remove the A records. This is all the automation does. If you try to install an app in a location and there is already a DNS entry in your DNS provider, Cloudron will inform you of the same and let you 'overwrite' it or cancel the app installation. Same goes for email stuff. It sets up things like DKIM/SPF records automatically. These are updated carefully to not collide with existing entries. The MX record is only touch if you enable incoming Cloudron Email. Even in that case, there is a checkbox to not update DNS.

@eddowding If you like you can patch the file in /home/yellowtent/box/src/mail.js and systemctl restart box.

@fbartels Thanks, it working and solved my issue. @girish The issue was that I have not set the provider to No-op, while without this step it was unable to change the location of any apps. Thank you both for the support.