Cloudron Forum

Thanks for the tip! I really want to think of the idea of self hosting email but mitigate also downtimes and reputation/spam issues, this otherwise would cause me quite some anxiety and risk my reputation.

@mmtrade the image looks correct . the issue is something else then . if you write to support@cloudron.io, then we have to debug this again .

@joseph No I have not set it to maintenance mode and I have not plugin installed. Just right now I received update notification in Nextcloud I updated it and it worked flawlessly. But this time not mounted nfs volume, it was kept to default. @BrutalBirdie I can confirm 100% that it is working without any problems and updating well when not using nfs volume mount. Next time I will mount nfs volume and check.

@mouse77 you should be able to just use the domain as it is shown in your screenshot, if you own that domain and can change the DNS records for it at your nameserver provider. For wildcard usage, you need to setup 2 DNS A records as a minimum. One for cloudron.indesigner.net and another one (the wildcard) for *.cloudron.indesigner.net . Both are A records and should point to your server's public IPv4 address.

@charlesnw said in What's the largest Cloudron you have seen?: In the process of packaging up a number of applications for Cloudron that a fully self-hosted business would need [image: 1746109026222-theofficemichaelscottgif.gif]

glad it worked out in the end, still pretty rough. I would recommend to take a fresh backup and clone the app instance from that into a new test instance, just to verify if that works then. Otherwise we have to investigate what the root cause is.

The second command seems promising.. It looks like it is writing to a hardcoded file /app/code/wallabag/wallabag-export.json (since it's a very old version maybe it didn't write to stdout) . Put the app in recovery mode - https://docs.cloudron.io/apps/#recovery-mode . this makes the filesystem writable In one web terminal, just run /app/pkg/start.sh . this runs the app and creates paths In another web terminal, try running the second command and check if that /app/code/wallabag/wallabag-export.json was created ... if it was you Download it using the Download button in web terminal ? or copy it to /app/data and use file manager .

@charlesnw Cool, sounds good. CLoudron's a great way to discover and test all these amazing things to FOSS world kindly shares with humanity. OpenWeb UI has recently changed their license model, so that migh become an issue: https://forum.cloudron.io/post/106732 Also, LibreChat is just a ton easier to add all the models to and keep up to dat, as Open WebUI needs continual copy/pasting/checking for updates to tools, functions, models code. It's just time-expensive keeping on top of that with multiple instances, and often doesn't have all the features a model offers kept up to date.

@baris thanks ! chat is re-enabled now. For those who don't want it , there is a setting in the profile: [image: 1746263783316-b642eaa5-6d50-4163-80d8-b28dd7cf100b-image.png]

No, the errors came back. Is it at all possible it‘s connected to Adguard Home running on the same Cloudron (which uses port 53, IIRC)? My /etc/resolv.conf looks like this btw nameserver 127.0.0.53 options edns0 trust-ad search fritz.box My iptables look fine now… Chain INPUT (policy ACCEPT) target prot opt source destination CLOUDRON_RATELIMIT 0 -- 0.0.0.0/0 0.0.0.0/0 CLOUDRON 0 -- 0.0.0.0/0 0.0.0.0/0 Chain FORWARD (policy DROP) target prot opt source destination CLOUDRON_RATELIMIT 0 -- 0.0.0.0/0 0.0.0.0/0 DOCKER-USER 0 -- 0.0.0.0/0 0.0.0.0/0 DOCKER-ISOLATION-STAGE-1 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED DOCKER 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED DOCKER 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED DOCKER 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain CLOUDRON (1 references) target prot opt source destination DROP 0 -- 0.0.0.0/0 0.0.0.0/0 match-set cloudron_blocklist src ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp multiport dports 22,80,202,443 ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:3389 ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:32400 ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:32500 ACCEPT 6 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 3478,5349 ACCEPT 17 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 3478,5349 ACCEPT 17 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 50000:51000 ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 8 ACCEPT 1 -- 0.0.0.0/0 0.0.0.0/0 icmptype 0 ACCEPT 17 -- 0.0.0.0/0 0.0.0.0/0 udp spt:53 ACCEPT 6 -- 172.18.0.0/16 172.18.0.1 multiport dports 3002,3003 ACCEPT 17 -- 172.18.0.0/16 0.0.0.0/0 udp dpt:53 ACCEPT 0 -- 0.0.0.0/0 0.0.0.0/0 LOG 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 2/min burst 5 LOG flags 0 level 7 prefix "Packet dropped: " DROP 0 -- 0.0.0.0/0 0.0.0.0/0 Chain CLOUDRON_RATELIMIT (2 references) target prot opt source destination CLOUDRON_RATELIMIT_LOG 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 flags:0x17/0x02 #conn src/32 > 5000 CLOUDRON_RATELIMIT_LOG 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 flags:0x17/0x02 #conn src/32 > 5000 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 state NEW recent: SET name: public-22 side: source mask: 255.255.255.255 CLOUDRON_RATELIMIT_LOG 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 state NEW recent: UPDATE seconds: 10 hit_count: 5 name: public-22 side: source mask: 255.255.255.255 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:202 state NEW recent: SET name: public-202 side: source mask: 255.255.255.255 CLOUDRON_RATELIMIT_LOG 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:202 state NEW recent: UPDATE seconds: 10 hit_count: 5 name: public-202 side: source mask: 255.255.255.255 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:222 state NEW recent: SET name: public-222 side: source mask: 255.255.255.255 CLOUDRON_RATELIMIT_LOG 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:222 state NEW recent: UPDATE seconds: 10 hit_count: 5 name: public-222 side: source mask: 255.255.255.255 CLOUDRON_RATELIMIT_LOG 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:636 flags:0x17/0x02 #conn src/32 > 5000 CLOUDRON_RATELIMIT_LOG 6 -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:3004 flags:0x17/0x02 #conn src/32 > 5000 CLOUDRON_RATELIMIT_LOG 6 -- !172.18.0.0/16 172.18.0.0/16 tcp dpt:2525 flags:0x17/0x02 #conn src/32 > 50 CLOUDRON_RATELIMIT_LOG 6 -- !172.18.0.0/16 172.18.0.0/16 tcp dpt:4190 flags:0x17/0x02 #conn src/32 > 50 CLOUDRON_RATELIMIT_LOG 6 -- !172.18.0.0/16 172.18.0.0/16 tcp dpt:9993 flags:0x17/0x02 #conn src/32 > 50 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:2525 flags:0x17/0x02 #conn src/32 > 500 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:3002 flags:0x17/0x02 #conn src/32 > 500 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:4190 flags:0x17/0x02 #conn src/32 > 500 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:9993 flags:0x17/0x02 #conn src/32 > 500 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:9995 flags:0x17/0x02 #conn src/32 > 500 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:3306 flags:0x17/0x02 #conn src/32 > 5000 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:5432 flags:0x17/0x02 #conn src/32 > 5000 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:6379 flags:0x17/0x02 #conn src/32 > 5000 CLOUDRON_RATELIMIT_LOG 6 -- 172.18.0.0/16 172.18.0.0/16 tcp dpt:27017 flags:0x17/0x02 #conn src/32 > 5000 Chain CLOUDRON_RATELIMIT_LOG (19 references) target prot opt source destination LOG 0 -- 0.0.0.0/0 0.0.0.0/0 limit: avg 2/min burst 5 LOG flags 0 level 7 prefix "IPTables RateLimit: " DROP 0 -- 0.0.0.0/0 0.0.0.0/0 Chain DOCKER (3 references) target prot opt source destination ACCEPT 6 -- 0.0.0.0/0 172.18.30.4 tcp dpt:2465 ACCEPT 6 -- 0.0.0.0/0 172.18.30.4 tcp dpt:2587 ACCEPT 6 -- 0.0.0.0/0 172.18.30.4 tcp dpt:4190 ACCEPT 6 -- 0.0.0.0/0 172.18.30.4 tcp dpt:9993 ACCEPT 6 -- 0.0.0.0/0 172.18.30.4 tcp dpt:9995 ACCEPT 6 -- 0.0.0.0/0 172.18.0.2 tcp dpt:2003 ACCEPT 6 -- 0.0.0.0/0 172.18.18.225 tcp dpt:53 ACCEPT 17 -- 0.0.0.0/0 172.18.18.225 udp dpt:53 ACCEPT 6 -- 0.0.0.0/0 172.18.18.225 tcp dpt:853 ACCEPT 6 -- 0.0.0.0/0 172.18.0.3 tcp dpt:22 Chain DOCKER-ISOLATION-STAGE-1 (1 references) target prot opt source destination DOCKER-ISOLATION-STAGE-2 0 -- 0.0.0.0/0 0.0.0.0/0 DOCKER-ISOLATION-STAGE-2 0 -- 0.0.0.0/0 0.0.0.0/0 DOCKER-ISOLATION-STAGE-2 0 -- 0.0.0.0/0 0.0.0.0/0 RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-ISOLATION-STAGE-2 (3 references) target prot opt source destination DROP 0 -- 0.0.0.0/0 0.0.0.0/0 DROP 0 -- 0.0.0.0/0 0.0.0.0/0 DROP 0 -- 0.0.0.0/0 0.0.0.0/0 RETURN 0 -- 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-USER (1 references) target prot opt source destination DROP 0 -- 0.0.0.0/0 0.0.0.0/0 match-set cloudron_blocklist src ACCEPT 6 -- 172.30.0.0/16 172.18.0.0/16 tcp spt:3389 ACCEPT 6 -- 172.18.0.0/16 172.30.0.0/16 tcp dpt:3389 RETURN 0 -- 0.0.0.0/0 0.0.0.0/0

@3246 said in URGENT HELP NEEDED - IP Blocked - Unable to remove app: It was convenient for getting customers to share large files and I didn't think somebody outside a very small group would find it. Use something like Nextcloud and setup a public folder where customers can send data into (also no upload limit) but it can be moderated by you. @3246 said in URGENT HELP NEEDED - IP Blocked - Unable to remove app: That was very small minded and ignorant of me! Perhaps, this can serve as a good example of what NOT to do Nah! It is just something that slips past anyone at some point. Since Cloudron does make it so easy to just host something, these things can and will happen. I also had such reports once because I forgot to set up https://docs.cloudron.io/apps/kutt/#registration and anyone could create shortened URLs with MY DOMAIN and serve heinous shit. Did also get flagged for that @3246 said in URGENT HELP NEEDED - IP Blocked - Unable to remove app: I am taking your advice and agree that 'life will find a way'. I will make it harder for it to do that That is the best we all can do @3246 said in URGENT HELP NEEDED - IP Blocked - Unable to remove app: It was simply a temporary lifting of the block for my static IP at the office, so I can access the GUI They are reasonable @3246 said in URGENT HELP NEEDED - IP Blocked - Unable to remove app: It felt like talking to a wall. What is your timezone? Maybe you did hit the skeleton shift @3246 said in URGENT HELP NEEDED - IP Blocked - Unable to remove app: I would improve their process by adding SMS notification or even a call to the number they have on file for me (and customers in general). They have extra contact channels. But only for BIG customers. @3246 said in URGENT HELP NEEDED - IP Blocked - Unable to remove app: For Cloudron, I hope we can add a note to the docu to help anyone who is finding themselves in a similar predicament and don't have you or a member of the community around to remind them of how to find app ID's Indeed! This should be added to the first time setup message screen. Will create a PR for that @3246 said in URGENT HELP NEEDED - IP Blocked - Unable to remove app: I stopped using Docker and Portainer to enjoy SysAdmin life in blissful ignorance by using a GUI. I feel you it can be so cozy. Have a great evening as well.

@girish excellent. And thanks again for all of your help!

I see the latest Cloudron Dolibarr update supports OIDC! Thanks! This is awesome. It was my last app to not support OIDC login.

@nebulon I wish... Guess I will end up removing it from the database, if it will be disturbing me too much Regardless - thank you for the tool!!

Unless you deleted docker storage (or used cloudron-support --recreate-docker and for some reason that was incomplete), I am not sure why the docker network will go missing . I think best to check again here if it happens again in a few days, but it's quite unlikely .

I had this issue for a long time with Cloudron, with both Hostinger and Hetzner as DNS/NS managers. I just check everytime those issues occur of course but I tend to just not trust anymore any Cloudron notifications for Emails config

@necrevistonnezr said in Public collections require login: I can't even connect to https://linkwarden.demo.cloudron.io/public/collections/1? ERR_NAME_NOT_RESOLVED I was able to view it. I wasn't logged in.