Cloudron Forum

Maybe still a bug in the filemanager then. Will look into this. Until this is fixed you can extract it and use the webterminal to change the ownership maybe?

The only message was only related to PTR. And there was no other message. Maybe it was a special case or a problem with the request and the question was whether from my server or on the provider's side.

After I clicked sync DNS, I left it for another 24 hours just to be sure, because the proprogation could have been prolonged. After 24 hours there was still a problem , then I did a record analysis and noticed as I wrote above one record A was not updated.

In general, the situation embraced. You can close the topic 😄 only waiting for the improvement of the results from PTR. Generally I have changed but FCrDNS has not been updated.

We haven't added a way to add custom persistent iptables rules . For SSH though, just move it port 202 and disable root auth and password auth. This usually cuts down all bots to 0.

Just creating multiple VirtualHost should work. Something like below works for me.

ServerName %{HTTP_HOST} <VirtualHost *:80> ServerName main.smartserver.io DocumentRoot /app/data/public/main LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" proxy CustomLog "|/bin/cat" proxy ErrorLog "|/bin/cat" <Directory /app/data/public/main> Options +FollowSymLinks AllowOverride All Require all granted </Directory> # Do not remove this include. It's required for your app to see the Real IP Include "/app/code/apache/rpaf.conf" </VirtualHost> <VirtualHost *:80> ServerName update.smartserver.io DocumentRoot /app/data/public/update LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" proxy CustomLog "|/bin/cat" proxy ErrorLog "|/bin/cat" <Directory /app/data/public/update> Options +FollowSymLinks AllowOverride All Require all granted </Directory> # Do not remove this include. It's required for your app to see the Real IP Include "/app/code/apache/rpaf.conf" </VirtualHost>

Sorry, but I am not following how name resolution is dependent on port 22. Name resolution uses UDP port 52 and is completely different from SSH which is TCP port 22 .

Thanks, it works!

@matix131997 This was a bug in the UI code (setupdns view code). Fixed in https://git.cloudron.io/cloudron/box/-/commit/003bc457bf95a5b555a83d76b36199f3acec8ece

As a workaround:

Setup the DNS as manual or wildcard for a start Then, after you setup admin etc, go to Domains View and change it to Bunny. This view does not have this bug.

Sorry for the previous posts.

It just turns out that something may have been up with Chrome on Windows.
On September 6, they released a new version 117, where they disabled SHA-1 fingerprint, and since then I've had problems with the token on Let's Encrypt certificates with ECC 384bit.
Only today after updating to version 118, it just started working as it should properly even in the „Enchanced protection” mode in the security built into Chrome.

@matix131997 my understanding is that issuance from E1 requires whitelisting of your LE account - https://letsencrypt.org/certificates/ . This is why ISRG Root X2 is still limited availability.

I am back after a small test.

@timconsidine Yes it is a large number of small files.

After checking with different formats. Only started to work as it should with ".tar" format. It works like lightning with a new folder or in the current folder where the application is located.
With this format, the extraction takes in a second and is ready.

And I use a server from Hetzner - CX41 (Intel, 160GB Disk and 16GB RAM).

EDIT:

I would still add that I had resources allocated during the test: 4GB ram and 75% CPU. I still checked with the standard one, i.e. 256MB ram and 50% CPU - with ".tar" format it extracts just as fast.

There were a few bugs with the token display when we moved the dashboard over to OpenID. This is fixed now with https://git.cloudron.io/cloudron/box/-/commit/e9f3f135640f8ee60041a8797b32b62e032201af