Fix NextCloud 11 Security and Setup Warnings on OMV 3

David B · 27. Dezember 2016

My NextCloud 11 installation is showing me the following warnings under the administration panel which I would like to fix, but do not know how to. I have Googled all of these, and the only one that I made some progress on was the Strict-Transport-Security error, which I read could be fixed by adding an entry to the Nginx configuration file. I SSH'd into my RPi and added the entry to the configuration file, but after a reboot, the entry disappeared.

Does anyone have any ideas? Here is the entire list of warnings:

Security & setup warnings

php does not seem to be setup properly to query system environment variables. The test with getenv("PATH") only returns an empty response.
Please check the installation documentation ↗ for php configuration notes and the php configuration of your server, especially when using php-fpm.

The "Strict-Transport-Security" HTTP header is not configured to at least "15552000" seconds. For enhanced security we recommend enabling HSTS as described in our security tips.

No memory cache has been configured. To enhance your performance please configure a memcache if available. Further information can be found in our documentation.

DanieleU. · 27. Dezember 2016

Zitat von David B

The "Strict-Transport-Security" HTTP header is not configured to at least "15552000" seconds. For enhanced security we recommend enabling HSTS as described in our security tips.

Put

Code

add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;";

in your optional field of the server.

For

Zitat von David B

php does not seem to be setup properly to query system environment variables. The test with getenv("PATH") only returns an empty response.
Please check the installation documentation ↗ for php configuration notes and the php configuration of your server, especially when using php-fpm
No memory cache has been configured. To enhance your performance please configure a memcache if available. Further information can be found in our documentation.

you can find solutions here:
https://docs.nextcloud.com/ser…n.html#php-fpm-tips-label
https://docs.nextcloud.com/ser…?highlight=memory%20cache

You can ignore the memory cache warning.

I configured the server from this => Owncloud 8 and MySQL: alternative approach

And sorry for my bad english.

David B · 27. Dezember 2016

Thanks! Your English is great by the way

My config file does not have the variable set yet commented out, so what should I set it as? As for the memory cache warning, I would like to fix it, but I believe that it requires more RAM than a Raspberry Pi has. Perhaps @ryecoaaron could confirm that?

ryecoaaron · 27. Dezember 2016

Zitat von David B

As for the memory cache warning, I would like to fix it, but I believe that it requires more RAM than a Raspberry Pi has. Perhaps @ryecoaaron could confirm that?

DanieleU is correct that you can ignore that. That would be hosting OC/NC with a large amount of people connecting. And you are correct that the RPi isn't even close to having enough memory nor could it host enough users to need memcache.

David B · 27. Dezember 2016

Zitat von ryecoaaron

DanieleU is correct that you can ignore that. That would be hosting OC/NC with a large amount of people connecting. And you are correct that the RPi isn't even close to having enough memory nor could it host enough users to need memcache.

Okay, that's what I had figured.

For anyone that has the PATH error and wants to fix it, here is what I did. (These steps assume you used these directions to set up OwnCloud/NextCloud.)

SSH into your server
Execute the following command: printenv PATH
Copy the output that the command gives you
Log in to the OMV Web UI and navigate to the Pools list in the Nginx plugin
Select the Pool that you created as part of your setup and choose "Edit"
Scroll to the bottom to the "Extra options" box
In the "Extra options" box enter env[PATH] = TERMINAL OUTPUT where TERMINAL OUTPUT is the output from the printenv PATH command
Save and apply your changes

DanieleU. · 27. Dezember 2016

Ah, yes. I forgot the way to fix it.

In the "Extra options" box i have entered the following:

Code

clear_env = no
env[HOSTNAME] = $HOSTNAME
env[PATH] = /usr/local/bin:/usr/bin:/bin
env[TMP] = /tmp
env[TMPDIR] = /tmp
env[TEMP] = /tmp

Thank you.

Jetzt mitmachen!