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.

We detect the IP using curl https://api.cloudron.io/api/v1/helper/public_ip . Can you check what this returns and why this doesn't return your public IP? You can also use something like https://whatismyipaddress.com/ which should return the same value.

@hendrikvl It's not a problem to have local network specific configuration in unbound. See https://docs.cloudron.io/networking/#private-dns .

As for the motivation, we use unbound because the mail server needs to do DNSBL queries. Most of the DNSBL servers like Zen SpamHaus will not respond if the queries originate from Google/Cloudflare DNS. This forces us to run our own DNS server.

The other motivation was also to log DNS lookups by apps to identify any malicious use but we never got around to this (this was initially designed for a setup where we expected all app packages to be done by 3rd party).

Finally, the unbound server should not be used much at all because most of the apps should not be querying anything external.

As of now, Im not having this issue anymore. I really dont know what would have caused this.

Im thinking of setting up an opnsense firewall, not sure if it would help though

@nebulon I find the solution taking infos from this forum .

In fact, I opened port 53 TCP and UDP and Cloudron can resolve domain names.

Configuration now is:

firewall template.png

All seems to working fine... I marked this thread as "Solved" 🙂

@nebulon Fantastic, thank you!

@odie Still stuck on this. The culprit is definitely that the usb network card fails to receive its configuration on boot. I cannot get netmanager to configure and initialize it at all. Only the two manual commands seem to work:

sudo ip addr add 192.168.9.101/24 dev enxc4411eb4c476 sudo ip link set dev enxc4411eb4c476 up

I have tried various thing with network manager, and I've tried adding a config file to systemd-networkd under /etc/systemd/network/ - the only thing I achieved, was to have every network freeze when I inserted the usb ethernet adapter (only to unfreeze as soon as I disconnected it). Tried keeping it disconnected for longer, just to see, but connections were frozen until I unplugged the usb network card. So I had to remove these config files.

Can anyone offer suggestions? I don't know where to even look for assistance on this now... Thanks!

Tha

@d19dotca said in Why does cloudron block ports?:

@cumpal Cloudron expects to be the only one running on the server, so for security reasons it locks it down unless needed by Cloudron or any of the apps on it. If you need to modify it, I think you can just update the firewall rules manually in Ubuntu, though I've not done that part myself as no need for it yet. but hopefully that at least explains why it's locked down. You may want to review the Cloudron docs on security features too.

@girish said in Why does cloudron block ports?:

In addition to what @d19dotca said, you can whitelist extra ports using https://docs.cloudron.io/networking/#whitelist-ports . Please use this at your own risk, we don't recommend installing other software alongside cloudron .

Thanks for these replies! I got them working.

There is an allow list file, but you have to access it from ssh. It should be in the docs.

Thank you all for your answers! Yes i was curious if cloudron did something special with the networking. I will contact the network administrators and try to fix the issue with them.

@robi Wow Robi, this is a great feature request!!! Just yesterday one of my Cloudron instances got a lot of traffic to email for a bruteforce attack.

@girish I think this feature have to put on the top of the list to improve safety but also to reduce workload of instances and network traffic...

Schermata 2021-01-13 alle 09.49.21.png

This is a statping how network performances was impacted before and later bruteforce.

Also, need a robust alert system - email or other - to let us know that something is happens.

@dkdkdkk what I do in similar cases is quite simple : allow routing between the 2 VLANs on the router.

So, your Cloudron and the camera would be able to talk to each other directly. And you can still only allow the first VLAN to route to the internet. That's what I'm doing for my "smart home" stuff. This should check all your boxes 🙂

Looks like this is fixed upstream with next release then https://github.com/nextcloud/richdocuments/pull/1412

@shai said in Format for IP Blocking:

If you are curious, blocking China and Russia came to 19,000 rows. Cloudron didn't stutter.

The firewall does. It will take progressively longer to make fw changes as you keep adding IP blocks. Not an issue for one time things, but something to keep in mind.

@hillside502 yes, would be cool to map home networks and the upcoming Cloudron Multiserver.. and any ActivityPub App federations.

Follow up from the customer: "The issue here turned out to be that in Wordpress, WP Rocket caching plugin was used. This plugin automatically starts to preload the cache of each page once something in the site has been updated. The preload itself causes some stress on the CPU and maybe some other processes. Turning off the plugin, the products were sent for less than 2 mins."

They are working with the WP Rocket team to find a workaround.

@girish I did not know the term. I certainly did know the effect ^^ (I might have to invest in an actual rubber duck... maybe they are especially effective)

@girish Hey, did just that, and I'm having trouble resolving names AFTER setting them. Cloudron is able to set dns records on aws just fine, but then the check to see if the records are created never gets done. Checked the logs and it's server timeouts. Tried running an nslookup query, to no avail as well.

Kinda weird, seems like the same problem I had on the hosting provider, with unbound, maybe? When I try to sudo, it also says sudo: unable to resolve host ubuntu: Resource temporarily unavailable, but it gets me to root anyway.

I'm a bit beyond my skills here, though, if anyone would like to chime in, I'd appreciate it.

Oh, interesting, I hadn't thought of those other use cases for this, but I really like that you brought them up, thanks for the feature request! I'll keep this thread updated with any development on that end if @girish doesn't beat me to it! ☺️

@robi Ahh, i completely understand now. This is a much complex level of what @girish and I are building right now with the VPN Client being one network you can choose to connect multiple other networks to. We’ve scoped that out pretty well so as we work on that and as it gets more fleshed out, I’ll update this ticket with advancements of how we might be able to have take this “sharing networks” basic concept further. I really like this train of thought though so I won’t forget it! ☺️

@girish https://www.ipdeny.com/ipblocks/data/countries/all-zones.tar.gz

But I did get that from your blog post for 5.6: https://blog.cloudron.io/cloudron-5-6-released/ so maybe you're looking for better ones?

@lonk said in VPN tunnel for apps:

Oh, and it may require like 4 or 5 patches to box code. Forgot about that. 😅It's fully functional tho, a little unpolished, a lot unpolished. But everything works. @girish and I will work together to integrate it properly at some point after 6.0. My patches run at "start" time, so the fact they're inefficient isn't too big of a deal, but just know that somewhere down the line, @girish and I will add it properly into a stable version of Cloudron.

What an accomplishment this was for me back then. I like that my first post in the forums is this crazy hellscape of Cloudron and Docker development jargon. I also wonder if this will ever help anyone down the road. Either way, I'm glad this whole thing is archived, it's p nostalgic for me. ☺️

@girish stellar service as usual, of course it was the old node version, login works as expected now!

@girish confirmed - it works now. thanks.

@girish So, it was the TLS. Changed it to 1.2 and the requests went smooth and fast. Thanks for the tips 🙂

Hi @abasitali Cloudron will attempt to resolve the DNS records with regards to the public IP address. Since you said you have an internal DNS server and hosting on-premise, can you give a bit more information about the setup? It could also help if you send a quick mail to support@cloudron.io with mentioning the domain, if you don't want to have it publicly known here, that way we can maybe see if things resolve correctly from our side.

If this is not a public server, please checkout the docs at https://cloudron.io/documentation/networking/#private-dns