Solved time4vps installation error

[zylstra]

I got this same error at time4vps with Ubuntu 20.04. So I tried thpuffin's solution but got:

Error: Some packages like nginx/docker/nodejs are already installed. 
Cloudron requires specific versions of these packages and will install them as part of it's installation. 
Please start with a fresh Ubuntu install and run this script again.

It took about 20 minutes for "Installing base dependencies and downloading docker images" but I'll try it again. But this time I'll create that file first.

So I created that file before running cloudron-setup. Now I get an error, and the log says:

Running cloudron-setup with args : --                        
Hit:1 http://ubuntu-archive.mirror.serveriai.lt focal InRelea
se                                                           
Hit:2 http://ubuntu-archive.mirror.serveriai.lt focal-updates
 InRelease                                                   
Hit:3 http://ubuntu-archive.mirror.serveriai.lt focal-securit
y InRelease                                                  
Hit:4 http://ubuntu-archive.mirror.serveriai.lt focal-backpor
ts InRelease                                                 
Hit:5 http://archive.canonical.com/ubuntu focal InRelease    
Reading package lists...                                     
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held
 by process 1231 (unattended-upgr)                           
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lo
ck-frontend), is another process using it?

I'm a newbie. Is there a command I can run for a work-around?

[nebulon]

@zylstra looks like that VPS was still busy installing updates on first boot, which is why the dpkg lock is still held by some other process. In such cases letting the VPS settle after first boot for some time helps until it is fully provisioned by the VPS provider.

The actual first message about the installed packages is more of an issue though. Did you happen to install anything prior to Cloudron or ran a manual server update?

[zylstra]

@nebulon Yes, waiting for the server to complete upgrades, etc. allowed me to continue with the Cloudron installation.

I did not think I ran any commands before the Cloudron installation commands, but I was not 100% sure, so I ordered another VPS and tried it again. I get the same error. I can give you access to the server if you would like.

[girish]

@zylstra Can you try if a apt update and then apt upgrade works? (also, i made a new topic to avoid confusion).

You can also drop us a mail at support@cloudron.io and we can take a look.

[zylstra]

I tried apt update and then apt upgrade. Although those upgrades worked, I still received the Cloudron error.

No need to take a look at this error since I found a work-around as mentioned here, https://forum.cloudron.io/topic/4068/installation-failed-on-20-04-server?_=1632810595887 . Thanks.

[murgero]

@zylstra The more likely scenario is they have the VPS pre-programmed to update on first boot. It's unlikely you did anything before hand.

[girish]

@zylstra thanks, I have made a fix in our next release in any case - https://git.cloudron.io/cloudron/box/-/commit/73315a42fef03bc144fdfd707b8a6d5905733109