@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 .

@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 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.

@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.

@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.

I'm getting the following error when trying to load data from a zip file that is included with the code base.

Error: Loading local data is disabled; this must be enabled on both the client and server sides

/app/data/openemr/library/standard_tables_capture.inc at 558:sqlStatement
/app/data/openemr/interface/code_systems/standard_tables_manage.php at 99:icd_import(ICD10)

The following php.ini setting is in /app/data/php.ini

mysqli.allow_local_infile = On

I've added the following to /etc/mysql/my.cnf

[mysqld]
local_infile=1
[client]
local_infile=1

Apache and Mysql have been restarted. I'm still getting the same error. Any ideas?

@girish Thank you!

I just installed the open source app OpenEMR (an electronic medical records application) using Cloudron's Lamp App.

Set-up note: I symlinked /app/data/public to the OpenEMR root directory by running

ln -s /app/data/openemr /app/data/public

After a successful installation, the following post-install message appeared,

The "/app/data/openemr/sites/*/documents" directory contain patient information, and it is important to secure these directories. Additionally, some settings are required for the Zend Framework to work in OpenEMR. This can be done by pasting the below to end of your apache configuration file:

  <Directory "/app/data/openemr">
      AllowOverride FileInfo
      Require all granted
  </Directory>
  <Directory "/app/data/openemr/sites">
      AllowOverride None
  </Directory>
  <Directory "/app/data/openemr/sites/*/documents">
      Require all denied
  </Directory>

My current /app/data/apache/app.conf looks like this (I have made NO changes to what Cloudron created):

ServerName %{HTTP_HOST}
  
<VirtualHost *:80>
    DocumentRoot /app/data/public

    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>
        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"
    # This line can be commented out, if you do no require PHPMyAdmin Access
    Include "/app/code/apache/phpmyadmin.conf"

</VirtualHost>

Question: do I just add the recommended apache directives at the end of /app/data/apache/app.conf as recommended?

(I'm sorry if this is such a "duh" question. Frankly it was my struggles and ultimate headbanging configuring apache that had me searching for a better way and finding Cloudron. I have about 15 apps installed and I've never had to fuss with apache previously. Thanks for your patience.)

@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.

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