Cloudron Forum

@mmtrade yeah, that's the problem. IPv6 is not working on the server. Can you also try ping6? $ ping6 ipv6.api.cloudron.io PING ipv6.api.cloudron.io (2604:a880:800:10::b66:f001) 56 data bytes 64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=1 ttl=45 time=122 ms 64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=2 ttl=45 time=235 ms

Yup, you are right that Cloudron needs IPv4 currently. IPv6 only setup is coming only in Cloudron 8

@mmtrade Okay, after a thorough analysis of my account. I have a VPS the cheapest, where I could not change the IP address. It remains technical support to solve this and as you in which you manage the server you have the task of securing the server.

@girish Finally, I would like to say that I haven't quite figured out what the problem was. I had used Cloudron bare metal. In the last few days I switched to Windows Server and have Cloudron running in a Linux VM via Hyper V. I then assigned a manual IP there and the problem no longer occurs. I guess it would have been fixed before with a manual IP as well.

@estudios507 If you want to open up an arbitrary port like 8000 from your server, then you have to build a custom app for this . See https://docs.cloudron.io/packaging/tutorial/ . The custom app has to expose 8000 using https://docs.cloudron.io/packaging/manifest/#tcpports . There is no other way on Cloudron for an app to expose a custom port.

@girish Thanks for answering, I will try it and if I still face any issue, I will update by starting my own thread.

It is as @humptydumpty said. Cloudron 8 (not yet released) has IPv6 only support.

@thoresson yes. If you have a Cloud firewall, you can also whitelist just your IP for port 222.

@girish Thanks you for your quick answer. Works great now.

@tgatellier I had to activate a Cloudflare DNS Proxy to achieve this on one Wordperss instance. Now I'm testing 8G Firewall suggested from @jagan . I think Cloudron should have some feature to achieve this ...

@imc67 said in Per-application access rules: @umnz said in Per-application access rules: @imc67 I'm not sure what you mean, Cloudron does have a Trusted / Blacklisted IPs and Fail2Ban support. https://docs.cloudron.io/security/ You are answering your own question: look at the subject of this future request and then the docs. What you mentioned is on server level .... not app level Oops, my bad! Take my +1 instead lol.

Yes you are right, the host has it installed. I tried it from a terminal within one of our apps. There it probably would be overkill.

@d19dotca said in Blocked IP addresses in Cloudron but still able to access WordPress sites: I know that this feature was likely originally intended to be a manual update rather than importing a giant list and works well for that, but as threats/spam become more common place, I think we’ll need Cloudron to keep up. Is it possible to prioritize improving this feature soon for us to allow thousands of IP addresses being added? Fully agree! A strong network filter / block would be another USP

@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