Cloudron Forum

I wanted to let you know how I got everything to work, it might help other users.

The initial issue was about DNS resolution. The quick fix is indeed to use the forward-everything option in unboud but with the previously used dns server. To find that value you just need to do a resolvectl and look at the value of the Current dns servers. In my case it was 10.0.2.3 (the one that was linked to my vpn on the host machine of the server). That is enough to fix the installation script losing internet.

For the Configuration error: Domain resolves to ["XXX.XXX.XXX.XXX"] instead of IPv4 XX.XX.XX.XX the quick fix in my case (home server not directly exposed to the internet) was to install an openvpn server on the vps server (https://www.cyberciti.biz/faq/ubuntu-22-04-lts-set-up-openvpn-server-in-5-minutes/) and an openvpn client on my home server so that my home server gets the vps's IP address. In this setup you I also need a reverse proxy to expose the 80 and 443 ports from the home server to the vps.

@girish I have mine in France.
I've been able to install Cloudron since, I guess the problem was with the OS they provided, but I still don't understand why apt update only worked after 1 day.

You are welcome @alphy. Enjoy Cloudron!

@girish said in resolvconf failed by Install to Cloudron:

Did I understand correctly, that cloudron-setup is failing and that the error you posted is from /var/log/cloudron-setup.log ? What's the log lines before the error ? See if you can fix those errors manually and run cloudron-setup --redo .

It's not me this time, but I've hit this before yes cloudron-setup does not work at all on Netcup VPS vServers because they are running some custom minimized version of Ubuntu.

See also this previous thread https://forum.cloudron.io/post/74252

Netcup said on Twitter they would look into it here https://twitter.com/netcup/status/1711394283347960098 but presumably they haven't fixed it.

@joack said in Cloudron partial install but server seems active:

I tried installing it on my recently updated ubuntu20.04 desktop

As others warned, don't do this! It's not meant to be run this way. You can create a VM on your desktop and install it in the VM though.

The error itself is happening because you probably are using MySQL already and this is conflicting with Cloudron installation.

@ZZIanis please never do this "solved, thanks anyways" you know what I mean...

At some point someone else will search the same issue and find this topic and has high hopes you know the solution just to read "Nvm it solved, thanks anyways" 😄

Everyone had this, in the search to solve an issue just to find a forum post where someone just wrote "solved" 🙂

@imc67 said in Cannot install Cloudron on Ubuntu 22.04 (DNS Issue):

I recently installed on a NetCup RS Ubuntu minimal and with Cloudron (and Netdata 😉 ) and had no single issue! Also AVX and AVX2 is supported!

Yeah, fair point, their more expensive RS (Root Server, as they call them, although they aren't dedicated but virtualised) product line works fine (I was on one until I upgraded to a dedicated server at Hetzner)

It's the cheaper vServer (VPS) product range which are currently useless for Cloudron.

@girish Thank you!

SERVER! Not a plain old computer. Go back and reread https://docs.cloudron.io/installation/

carefully
fully
completely

when you come to something that you don't understand, come here and ask.
when you come upon terms that are new, google them, read up on them, learn about them.

after 1 month of doing this, THEN try to actually install and use Cloudron.

@ccfu @warg TIL that OpenVZ stands for Open Virtuozzo ! From https://en.wikipedia.org/wiki/OpenVZ . Added to our docs page then.

@nebulon, @BrutalBirdie
Thx to both of you, the call is now working.
curl -kX POST -H "Content-Type: application/json" https://my.smthg.com/api/v1/apps/install?access_token=857f7d7eb583cfb951e5a50c75a762b94304d4ba50d4a0c94950643eaab7959a -d '{"appStoreId": "io.n8n.cloudronapp@2.37.0","subdomain": "workflow","domain": "somethg.com","accessRestriction": {"users":[],"groups":[]}}'
{
"id": "c6c79d78-7c7c-414b-acf7-8b5cc39370ed",
"taskId": "269"
}

It needed obviously the header, but also I thought reading the API specs that accessRestriction could be null. It is not the case, so I used @BrutalBirdie assignment (empty users and groups) and the call succeeded.
Once again thank you very much.

@leefree IAs a first step, are you able to access https://<internal-ip-of-your-vm> ? If that works, it means the VM itself is fine and ports are open. Next step is then to figure why BT home hub is not forwarnding ports correctly.

OK, I have fixed the unbound issue with IPv6. It's an upstream bug but I have made a workaround for the moment. Fix will be part of 7.3.5 (released next week).

okay, i'll try it running on ubuntu using virtual machine.. .

@interface as long as your Cloudron dashboard is reachable you can perform all this from the UI. If your IP has changed by now for the dashboard as well, then initially set your current IP manually for your my.example.com dashboard domain to reach that again.

@madmaneighteen can you share a bit more about your environment? Also when the routing and possible portforwarding are correctly setup, you should hit nginx on your Cloudron there, so for a start check if nginx is running in your Cloudron server systemctl status nginx and also maybe try to curl localhost within the server to ensure nginx is also responding correctly there at least.

This happens every time I rebake posts too

sudo -E -u cloudron bundle exec rake posts:rebake

i Had the same issue... but still works at ubuntu 20.04

@nebulon I hit many road blocks indeed, but managed to move quite well forward
now i'm at the part of the npm rebuild and I can't do the db-migrate because I don't see any npm install being done that provides db-migrate within nodes_modules/.bin folder

I have documented the changes I had to do in the different install files to get it working, i can share this to the support email if you're interested

@jdaviescoates Add Hostinger to the list too. I signed up for a basic web hosting plan with them. I created a secondary user account in their admin panel for my developer so he could have access and it didn't work. I contacted support and it took them weeks to get it sorted. Meanwhile, I ended up sharing my main account credentials. I was asked identical questions by different staff (under the same ticket) and I was tossed around like a beach ball in a techno festival. I had better experiences with EIG owned hosts and those guys absolutely s***.