@luckow => here is my slight riff on your great work.

I don't like composer.json and composer.lock to be at the cloudron data root /app/data

So I removed this bullet from the instruction:

* move everything from inside recommended-project into the root of /app/data
mv recommended-project/* . & mv recommended-project/.* .

And then I changed
rm -rf public & ln -s web public
to
rm -rf public & ln -s recommended-project/web public

I find it much easier to manage version control this way.

Your pioneering work made it so much easier for me. Thanks.

@girish Thanks so much for the great answers.

I look forward to installing the cloudron cli on my computer running Linux Mint .

@girish I successfully migrated my Cloudron from one server to another. I followed your directions and updated Cloudron to v 6.0.0 before making my final backup of the old server.

Thank you.

@murgero I had downloaded the zip archive, pushed it to the Cloudron and then unzipped it. I got to the installer by just navigating to the site url. With the original method I never succeeded or figured out what the problem was.

However, I started over and this time used Piwigo's netinstaller option where I only push one php file and then navigate to that file... the install went perfectly, no problems connecting to db.

My next step is to manually go into the config file and replace the credentials there with Cloudron environment variables.

Thanks to you and @scooke and @JLX89 who responded with helpful suggestions.

@girish @murgero,

The problem was the GPG key for yarn.

By adding the following on line 5 of Dockerfile the problem was fixed:

RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -

That line did generate the following warning; you tell me if it is of concern:

Warning: apt-key output should not be parsed (stdout is not a terminal)

I've successfully installed the app on my Cloudron. Now I'm configuring the two dbs.

@girish Thanks so much for the great service! I'm a happy customer.

@girish thx. It was really helpful for you to say that you didn't think the problem was with the cert. It got me thinking outside that box.

The problem was that I hadn't properly set up Nat loopback support on the new router (the config for that was different from the one on the old router).

I had to un-tick the box "Stop DNS Rebind" in order to get my site to resolve on my local computers (access from outside my network was fine --which I hadn't realized at first).

There was a big warning when I unticked that setting. Any thoughts on this. It's possible that I have some other local network or router setting that isn't quite right.

Thx.

@nebulon Great. Thanks. That info should be put into Multiple Databases with Lamp instructions.

• I installed the Cloudron Collabora app.
• I set the Nextcloud domain at the Collabora domain
• In Nextcloud I installed the Collabora online connector app
• In Nextcloud I set the URL of the Collabora instance at: /settings/admin/richdocuments
• When clicking "Save" there I get "Could not establish connection to the Collabora Online server."
• I can successfully connect to a demo server.

Any ideas?

@girish wrote "I remember mentioning NAT loopback in https://blog.cloudron.io/installing-cloudron-on-a-home-server/."

That is indeed where I learned about it and was diligent when I set up the old router... but forgot about it it completely when setting up the new one. Always a good idea to work from docs and not just your own head.

@girish So clever! Worked like a charm.

The only part where I had to fuss for a few minutes is that the app errored on changing to the new domain; it got stuck on de-registering the old domain. I went into the Domain manager and deleted the domain entirely from the Cloudron and then the app was able to receive the new domain without problem.

Thank you so much for writing the steps out in detail. I really appreciate it!

@mehdi Okay. But why would my.example.com work? And it does not. When the registration expired the Registrar disabled the DNS records for that domain which is normal. So how would associating an IP address with the domain name on /etc/hosts help that problem?

now that I think of it I should be able to access the Cloudron from Cloudron CLI. I'll go look to see if I can add domains and associate them to apps with Cloudron CLI.

I'll also look at @girish reference to the dns-sync documents.

Am I missing something?

@msbt thanks so much. My interpretation of the fix suggested didn't work. I have posted a follow-up question there.

@girish I had the same problem as @letecho. @msbt sent me here.

I have tried putting the following into /etc/hosts

my.example.com 123.45.678.901

and

123.45.678.901 my.example.com

Also note that already in the /etc/hosts file, which I left untouched was:

127.0.0.1       localhost

Navigating in a browser to https://123.45.678.901 returns

You are seeing this page because this domain points to Cloudron server IP but no app is installed on that domain.

Ideas? thx.

I have a Cloudron with a WP Cloudron app at example.com and the Cloudron dashboard is at my.example.com. The domain registration for example.com has expired and will not be renewed.

I have full control of the server on which Cloudron is installed.

How can I change the domain for the Cloudron so that I can use this Cloudron and access the WP site again?

Thanks much.

@murgero I had downloaded the zip archive, pushed it to the Cloudron and then unzipped it. I got to the installer by just navigating to the site url. With the original method I never succeeded or figured out what the problem was.

However, I started over and this time used Piwigo's netinstaller option where I only push one php file and then navigate to that file... the install went perfectly, no problems connecting to db.

My next step is to manually go into the config file and replace the credentials there with Cloudron environment variables.

Thanks to you and @scooke and @JLX89 who responded with helpful suggestions.

@scooke I get the error after I've entered the values and clicked "start installation."

Yes, I know that "mysql" is the value for "host" and not "localhost".

Thanks in advance for further troubleshooting.

@jlx89 File ownership is www-data. File permissions are 777 for the config directory.

I'm trying to install the photo management app Piwigo onto a Lamp Cloudron.

The Piwigo web installer is saying it cannot connect to the database.

I can log into the database via phpmyadmin.

On the installer fields on the web form I'm using the explicit credentials for mysql found in /app/data/credentials.txt. (My plan was to manually edit the file created by the installer after installation and replace the explicit credentials with the environment variables. I didn't get that far.)

Upon submit of the web form installer I get the error "Cannot connect to server."

Any ideas?

@girish the local_infile is the approach the app uses to load data sets for optional functionality. I'll go to the forum for OpenEMR and see if there is a way for me to manually upload the data instead of being done through the webapp UI.