AAannnnnd now it is working. I wish I could tell you why, but I don't.

Thanks @robi

Hmm I still have permission denied inside the container to read /media/MyMount
😓

EDIT

This time, it's working, for future reference, only thing I did was to set the home directory properly in the systemD service for each mount, remount them and then systemctl restart box or from the UI restart the box, my mounts are now visible inside the containers and I can read from them

386b79d8-79cb-47db-8687-019194acef53-image.png

@mdc773 the Strict Mode can only be set on the global (whole mysql) level or the session/connection level. There is no way to set this at database level.

We cannot enable NO_AUTO_VALUE_ON_ZERO at the global level. Since this change will then apply to all the apps on Cloudron. This will break things (just like having it disabled breaks your app). AFAIK, there is no way to fix this other then fixing the script itself. Unfortunately, otherwise, you have to host this outside Cloudron since it's not compatible.

Maybe still a bug in the filemanager then. Will look into this. Until this is fixed you can extract it and use the webterminal to change the ownership maybe?

Since the domain of the frontend and the backend differ, the browser will send a preflight check request to the backend for the REST calls, so this means the backend has to respond properly via CORS. In your case do not touch the apache nor nginx configs (anyways nginx is the reverse proxy on Cludron and changes won't persist).

The Laravel app then should respond with the correct CORS messages, however I am no Laravel expert so I don't know how this works with that framework.

Edit: if Laravel needs apache settings, follow the docs at https://docs.cloudron.io/apps/lamp/#apache-settings

@murgero Many thanks for your help.

@girish Thanks for the quick resolution!

@joseph
Oh, okay! That works perfectly.
Thank you for the clarification!

@Robin my bad. The lamp.cloudronapp.php73 and lamp.cloudronapp.php74 are totally different packages! I think you are using the very old php 7.3 package. This is why you are not seeing the update. I don't know why the old one was deprecated though.

@chriskloss said in Connection Problems IWP:

These should be able to connect to each other if I use the FTP and MySQL data from the staging environment, right?

Yes, for MySQL. As long as they are in the same instance, you can use the MySQL credentials from one app into another.

For FTP, I guess you are asking if IWP can access files of another via FTP. This is possible, yes. Just use the SFTP credentials of the app - https://docs.cloudron.io/apps/#sftp-access

Just creating multiple VirtualHost should work. Something like below works for me.

ServerName %{HTTP_HOST} <VirtualHost *:80> ServerName main.smartserver.io DocumentRoot /app/data/public/main 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/main> 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" </VirtualHost> <VirtualHost *:80> ServerName update.smartserver.io DocumentRoot /app/data/public/update 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/update> 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" </VirtualHost>

Considering Turnkey Linux has a container version of LAMP with MariaDB that works great for our software, it is too much to manually setup SSL and other things, this is why we want to use the LAMP in Cloudron to setup our software, but MariaDB is needed.

@CRBear Screenshot of your App Location Settings may help everyone to understand what you have so far, to then help with what you're doing within the LAMP app.

A workaround is to edit the config in the MySQL container:

docker exec -ti mysql /bin/bash Then, edit /run/mysql/my.cnf In the container shell itself, supervisorctl restart mysql

Note that changes are not persistent across updates (but persists across reboots).

@nebulon I think the problem is consistent, thank you I will contact via email.

@shrey This is interesting. I hadn't noticed before that you had a complete different way of authorization. That's why I made an edit to the post and gave you the exact instruction, which is already implemented as standard.

@girish Thanks, that helped!

Thanks, it works!