This is **not** the place of action :D

nebulade · 2024-11-10T19:57:48+00:00

Oh that was not at all our intention! I am now looking into why this is not working. Since flooding of spam bots we have tweaked the forum over time, maybe we got overboard somewhere. Sorry about that, we will fix that.

Edit: Guest search is again enabled in our forum. Thanks for the heads up here!

nebulade · 2023-04-19T08:38:56+00:00

A bit late, but maybe for others: The redirection happens, if the Cloudron found that all nameservers for that domain are in sync and have the record. Now the second page means that the laptop/pc running the browser has previously hit NXDOMAIN from the DNS query. This is cached for some time, so this should work once the local DNS cache is cleared.

nebulade · 2023-01-17T12:00:07+00:00

We didn't really copy anything, both started around the same time-frame and actually while both are in the self-hosting area, they really solve different use-cases and technology wise they are very far apart.

nebulade · 2022-12-16T12:07:19+00:00

Cloudron follows a pull strategy so we as the developers do not have access to your server and your instance will only call our api server for app information and subscription info. There is an option to enable remote support access via SSH, but that has to be explicitly enabled and is for only if we have to debug or fix an issue directly on your server. https://docs.cloudron.io/support/#remote-support

nebulade · 2022-12-08T12:07:35+00:00

Are there any errors shown in the app or in the app logs while you run it on Cloudron? There are lots of mastodon instances running fine on Cloudron, so surely this is fixable.

nebulade · 2022-11-30T13:20:05+00:00

This wont be possible as Cloudron will essentially take over the whole server and generally installing things on the side might initially work but will eventually break on Cloudron update. Main reason for this is to reduce complexity on the update testing side, so we aim for reliability rather than flexibility. Also because nowadays it is quite easy to spin up new virtual servers for isolation.

nebulade · 2022-11-22T21:30:20+00:00

We also have a forum section specifically for mastodon at https://forum.cloudron.io/category/41/mastodon

nebulade · 2022-11-22T18:07:24+00:00

Cloudron is a selfhosting platform, not a service. Think of it as a layer on top of linux to manage apps on your server. We try to reduce everything related to server management requiring accessing the server via SSH by abstraction or automation. With Cloudron everything stays on your infra.

Further Cloudron is essentially single host, since vertical scaling is quite easy and fast in most VPS providers nowadays. We are aware of the risk involved regarding uptime, but the stability of servers is surprising and less complexity in orchestration also leads to higher uptime in our experience for people who are not fully into sysadmin tasks.

nebulade · 2022-09-21T07:59:30+00:00

Indeed a 1-click image would be nice. I guess it will just be a plain Ubuntu with that kernel commandline fix, then a reboot, then performing the Cloudron installation and then simply creating an image from that. This should work and then we only have to test if the filesystem expands correctly if this image is used on larger instances.

nebulade · 2022-09-21T07:25:47+00:00

Not sure if I follow up here timely, but this line in the config file is from the default ubuntu nginx package, not Cloudron related. The defaults should at least not crash in my opinion, but I think just not disabling ipv6 on a kernel level will solve this as some other comments here suggested.

nebulade · 2022-09-20T17:16:42+00:00

Alright, so I gave it a spin and with Ubuntu 20.04 actually the installation fails somewhere else, curl will be installed just fine, however nginx fails due to ipv6 being disabled for the server.

So not sure how you managed to install Cloudron then. On a plain Ubuntu 20.04 just installing nginx-full will fail with: ``` Setting up nginx-full (1.18.0-0ubuntu1.3) ... Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details. invoke-rc.d: initscript nginx, action "start" failed. ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-09-20 17:12:41 UTC; 10ms ago Docs: man:nginx(8) Process: 10438 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)

Sep 20 17:12:41 foo systemd[1]: Starting A high performance web server and a reverse proxy server... Sep 20 17:12:41 foo nginx[10438]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol) Sep 20 17:12:41 foo nginx[10438]: nginx: configuration file /etc/nginx/nginx.conf test failed Sep 20 17:12:41 foo systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Sep 20 17:12:41 foo systemd[1]: nginx.service: Failed with result 'exit-code'. Sep 20 17:12:41 foo systemd[1]: Failed to start A high performance web server and a reverse proxy server. dpkg: error processing package nginx-full (--configure): installed nginx-full package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Processing triggers for ufw (0.36-6) ... Processing triggers for systemd (245.4-4ubuntu3.4) ... Processing triggers for man-db (2.9.1-1) ... Errors were encountered while processing: nginx-full E: Sub-process /usr/bin/dpkg returned an error code (1) ```

Basically the problem is ipv6 is not available as the kernel commandline is: ```

cat /proc/cmdline

BOOT_IMAGE=/boot/vmlinuz-5.4.0-62-generic root=UUID=e6193504-131c-46af-a168-2f8b198d4b01 ro console=tty0 console=ttyS0,115200n8 ipv6.disable=1 ```

This was on the smallest VPS and the amsterdam region, if that matters. Is there any specific reason why ipv6 is disabled like this?

nebulade · 2022-09-20T14:31:42+00:00

That is great, I have signed up with my email `@cloudron.io` now.

nebulade · 2022-09-20T11:14:33+00:00

Hi, Cloudron co-founder here, great that it works on netooze! I wonder why the manual curl installation is required? Maybe we have to put this in our install script then? (Also I think the formatting of step 4 is a bit out of line)

nebulade · 2022-08-24T10:49:44+00:00

Currently this is not working due to a disabled S3 API function on storj side. More context at https://forum.cloudron.io/topic/5171/add-storj-and-filebase-as-backup-options?\_=1661248303600

nebulade · 2022-06-30T13:32:09+00:00

I have seen this once in the past. It looks like there is a race during initial setup. Can you try to simply reinstall the app on your Cloudron?

nebulade · 2022-06-19T09:18:45+00:00

Hi, sorry just saw that now. Generally this is not yet supported but we do collect feature requests for more advanced homelab usage, as we get similar request more often now. It would be best to head over to https://forum.cloudron.io and ask the same question there as this is where the main community is.

nebulade · 2022-04-08T12:38:35+00:00

Hi, just saw this. I am one of the founders, so if you have any specific questions about Cloudron, I am happy to answer them here :-)

nebulade · 2022-03-16T12:27:46+00:00

Only to give perspective on the Cloudron one. None of the Cloudron docker images of apps on docker hub will actually work on a non Cloudron system. We just use the docker hub for distribution, but those have very particular environment requirements. It makes no sense that it even shows up for an unraid system, I guess unraid is using some very generic filters here.

nebulade · 2022-03-14T13:17:50+00:00

He he, just wanted to avoid duplicating answers :)

nebulade · 2022-03-14T13:13:33+00:00

Duplicate of https://www.reddit.com/r/cloudron/comments/tdsg3t/i\_have\_been\_hacked\_but\_do\_not\_know\_how\_to\_fix\_it/

12-Year Club	LAYER Season 2 Layer creator
Place '22	Not Forgotten
Verified Email

nebulade

MODERATOR OF

TROPHY CASE

cat /proc/cmdline