Cloudron Forum

@d19dotca right, the 30d one seems to be 54975 size. I have increased the size of the ipset now to 262144 elements. If these things are growing more, we can look into making this size dynamic .

@girish Thank you. Your solution did the trick.
But we needed the ipv6 to be functional.
So what we did to make it work was > reinstall Ubuntu 22.04 LTS OS and didn't install unbound in advance. All is good now.

Cheers, yes I've added the r8125 module to that now. I'll see what happens next time I need to restart. I haven't had to either, must be my cheap hardware choices biting me in the ass.

So I think I've found the solution.
Modify the Proxy Host config > Advanced and paste the following:

set_real_ip_from 03.21.244.0/22; set_real_ip_from 103.22.200.0/22; set_real_ip_from 103.31.4.0/22; set_real_ip_from 104.16.0.0/13; set_real_ip_from 104.24.0.0/14; set_real_ip_from 108.162.192.0/18; set_real_ip_from 131.0.72.0/22; set_real_ip_from 141.101.64.0/18; set_real_ip_from 162.158.0.0/15; set_real_ip_from 172.64.0.0/13; set_real_ip_from 173.245.48.0/20; set_real_ip_from 188.114.96.0/20; set_real_ip_from 190.93.240.0/20; set_real_ip_from 197.234.240.0/22; set_real_ip_from 198.41.128.0/17; #use any of the following two real_ip_header CF-Connecting-IP; #real_ip_header X-Forwarded-For;

this will allow True Client IP Address to be passed to Cloudron.

@ccfu right... if DNS is not mainained by Cloudron, we have to show some message/alert the user. This requires some work, this is why this feature is not done yet 🙂 It seems like quite some work for very little value.

Thanks for your replay. 🙂
This is the third alternative. However, this is linked to a few cons:

Skillgap regarding IPv6 I am using unifi hardware which has a pretty basic IPv6 implementation

@bigvictorio At this point, no. But feel free to open feature requests and we can add firewall features as needed.

@girish ok got it. Thank you.

@AartJansen for new apps, AAAA is automatically added. For existing apps, go to Domains -> Sync DNS.

@AartJansen Ah ok, looks like a limitation of the domain host. You can also just create entries for each (sub)domain you use. If you have an app at foo.domain.com, create an AAAA record for that subdomain. Repeat for every app.

You should also switch to "manual" instead of "wildcard" DNS provider for this. It will remind you to setup A/AAAA records manually when you install an app.

@girish said in IPv6 in automated DNS propagation:

After enabling, click the sync DNS button to make it add the AAAA records for existing apps.

This is what I missed. Thank you so much! Everything works fine now 🙂

@MisterJD see https://forum.cloudron.io/post/40906 and https://www.simplified.guide/ssh/auto-block-failed-attempts

Thanks for the reply @MooCloud_Matt!

Proxmox is set to bridge and works with ipv4 without any problem.

But the problem is probably elsewhere, I tried opening the ipv6 test page on my laptop and it said my provider doesn't support ipv6, which is bullshit. I actually have two public ipv6s assigned from it.

So I would need to somehow run the installation with only ipv4, is it possible to do that?

alt text

You can try ping6 ipv6.api.cloudron.io and see if that works. Without it, IPv6 won't work.

@krumel thanks!

Also, please check if your router supports hairpinning https://en.wikipedia.org/wiki/Network_address_translation#NAT_loopback . This is what loops back a request to a public IP back into your private network.

@nebulon hey there, thanks for your reply, cloudron works now for me. maybe it was a dns propagation issue

@girish So I disabled the port forward rule in my router and it resolved the issue. Thank you!

@alexdimarco said in Does cloudron block bogon networks?:

One of the wifi networks (I do not have control over) uses bogon IP space for addressing. When connected to this network I cannot access any Cloudron servers. Do they block bogon? If so, how can I white list a network - in specific 100.64.0.0/10?

Cloudron blocks nothing by default.