I think if mysql container is not running then the inspect command does not print anything.

If we can see the mysql logs that will help.

Yes, there is no need to restart after that.

This is now added for 3.6

@Benoit Thanks for the news! It seems it is S3 compatible, so it should be straight forward for us to support it.

@murgero Yes, we are debating about how we should go about the managed/unmanaged wp internally as well. As you said, the unmanaged app is really just a fork of lamp app that pre-installs wp. It's just for ease of use and nothing else. Talking to a whole bunch of customers what we found is many of them don't know what LAMP even means... Maybe that apps' title has to be changed a bit since only devs understand what LAMP stands for.

Plex+SFTP yes! We also have Emby which is not published for which it will be useful. We thought of adding SFTP to WP app itself but the confusion here was that each app has to have different SFTP port. Instead we decided to have it at platform level where people can login as <username>@<appname> (have to have this format because many SFTP clients do not support virtual host it seems).

For the env var section, can you tell me the use case? In the past, we just made a UI for each app (like the openvpn, minecraft, collabora apps).

Whoops, didn't realize that graphite is actually not listed under services. Will add that for the next release.

@root_iam That's great! Can you give the mysql service a restart? services -> mysql -> restart.

3000 is the port in which the mysql service API runs. 3306 is the actual mysql service itself. It seems that for some reason the box code is unable to reach the mysql service.

If it doesn't work, can you check if docker inspect -f "{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}" mysql prints the IP above (i.e 172.18.0.6).

@rfg This was a bug in our previous version. You can fix this by going to services -> mail -> restart. You have to do this only once, future certificates will be setup correctly.

@jensbee4 If you click on the logs button in the app icon in the dashboard, you will see the access logs. We log in the combined format - "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"". More information about the format is http://httpd.apache.org/docs/current/mod/mod_log_config.html#customlog

Small change in plans for 3.6 - https://forum.cloudron.io/topic/1725/cloudron-3-6-new-plans