Cloudron Forum

node.js has a "happy eyeballs" quirk. This causes premature network errors when there is no ipv6 and ipv4 is slow. I have fixed this in https://git.cloudron.io/cloudron/box/-/commit/aefa481c43603d284346d58497b6ff5b462efd88

Thanks again for the tips!

Thank you, that is something.

Indeed, after sync I enable the IPv6, the app store works just fine as well as the current apps running, i test a few other case this also resolve issues with sometimes the manifest of the updated apps not shown

From my experience, don't syn the DNS while having the IPv6 Networ Enabled in Cloudron if no AAAA records in apps or domain

I don't know if it happens to anyone else using the Cloudron version 8.x but since I set my networks both work with IPv4 and 6, and it seems everything works normal

Great that you managed to resolve it quickly and thanks for the update here with the solution.

For anyone else out there that is having trouble, I was able to fix this issue by disabling ipv6 within ubuntu.

First I did the curl test as mentioned by @nebulon - it worked as expected, but when adding the --ipv6 option it failed.

When running "ip a" I could see an ipv6 address was present.

Using the link that @playsia supplied, I carried out the steps described in section 1: Disable IPv6 using Sysctl. I didn't need to modify the /etc/rc.local file.

Running "ip a" again, there was no more ipv6 addresses shown.

I only had these issues after upgrading to V8.0.3 and Ubuntu 24.04.1.

@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 ...

Now, combine this with something like Wireguard or Tailscale and limit access to certain apps (Vaultwarden, Nextcloud, etc.) to users connected to such VPN - that would be the dream

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