Richard Aarnink

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Richard Aarnink's Achievements


Newbie (1/14)



  1. Looks similar to
  2. I am worried, the slow progress makes me nervously. It is common knowledge that stagnation means decline.
  3. Upgraded from rc1 since release without any problems. Now stable for 1 day and 11 hrs. System is ASRock H410M-ITX/ac with Intel 10400 CPU. I am running several Dockers, but no VM’s. I have 2 SSD’s of which one is dedicated for plex and outside the array. All drive temps are shown correctly. Drives are also spinning down correctly. also installed plugin Dynamix System Temperature v2020-06-20 which detects coretemp nct6775 drivers only remark is the Motherboard temp is not showing (did not work in previous versions either). CPU temp is shown.
  4. Updated from beta 35. Everyting seems to work. Paritycheck is triggered after updating to rc1. In the System Log however I have several wrong csrf_token messages Dec 10 20:37:24 RichTech nginx: 2020/12/10 20:37:24 [error] 11802#11802: *5432 upstream timed out (110: Connection timed out) while reading response header from upstream, client:, server: , request: "POST /plugins/community.applications/scripts/notices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "", referrer: "" Dec 10 20:37:24 RichTech nginx: 2020/12/10 20:37:24 [error] 11802#11802: *5425 upstream timed out (110: Connection timed out) while reading response header from upstream, client:, server: , request: "POST /webGui/include/DashboardApps.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "", referrer: "" Dec 10 20:37:39 RichTech rc.docker: webserver-intern: started succesfully! Dec 10 20:37:39 RichTech rc.docker: webserver-intern: wait 4 seconds Dec 10 20:50:17 RichTech kernel: i2c /dev entries driver Dec 10 21:22:34 RichTech root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Dec 10 21:22:34 RichTech root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Dec 10 21:22:55 RichTech root: error: /webGui/include/DashUpdate.php: wrong csrf_token Dec 10 21:23:56 RichTech root: error: /webGui/include/DashUpdate.php: wrong csrf_token Dec 10 21:24:56 RichTech root: error: /webGui/include/DashUpdate.php: wrong csrf_token Dec 10 21:25:57 RichTech root: error: /webGui/include/DashUpdate.php: wrong csrf_token
  5. Yes, that is a solution, thx, still hope 6.9 will be released soon!
  6. Because I have an ITX board with 1 PCI slot which is already in use... Thus no slot available for an NIC board.
  7. I am also curious. As I updated my motherboard and CPU to an 10th gen Intel CPU, I am now forced to update to 6.9.0 beta 35. This version supports the latest Intel 219v NIC, which is not supported by 6.8.3. Updated without any issues, but I would to run on stable versions only.
  8. Hi Peter, here in the Netherlands power outages are rare. A UPS seems overkill and I was looking for a cheap alternative. Scheduled poerdown from the terminal worked so i guess this is also good for the rare occasions i need to power down. Thanks anyway!
  9. Hi, I have a request for the developer. I would like a plugin (button) which would enable me to shutdown and poweroff the server at a given date/time. Tomorrow morning maintenance is scheduled which means i will lose power. It would be great to have the option to schedule a shutdown in advance, as i am now worried that I oversleep. i tried to do this from the terminal with command shutdown -h 06:45 hope this works! regards Richard
  10. Hi, I have a question on xdebug. I would like to debug my php google assistant project. I read multiple articles referring to using remote xdebug. As far as I understand now, this would require xdebug to be setup inside the docker container. php-xdebug would need to be installed etc. I would like to know if I can use xdebug inside the letsencrypt docker container. I like this container for its swift updates to keep me secure, and I know that acutally installing anything inside the container will break upon the next update. Therefore this question, is xdebug enabled (but hidden from the config) or can it be added in future? Or lastly is there another docker container which I should use if I intent to debug?
  11. I just updated my system to 6.4.0 without any issues, it took approx 10-15 minutes Brief description of my system: - Gigabyte H270N-WIFI motherboard, 16GB DDR4 and an Intel Pentium G4560 (3,5 GHz) - array consists of 5x 3TB WD Red HDD's and a 120GB SSD for caching - use Docker containers for MySQL, Apache webservers, Plex and Duplicati (all work fine) - VM are not in use (currently) Update:--> Docker LetsEncrypt raises some issues, which I need to investigate. The log of this docker now reports [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... sed: /etc/php7/php.ini: No such file or directory sed: /etc/php7/php-fpm.conf: No such file or directory sed: /etc/php7/php-fpm.d/www.conf: No such file or directory sed: /etc/php7/php-fpm.d/www.conf: No such file or directory [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 2048 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d www.<<removed by me before posting log>> E-mail address entered: <<my email>> Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. IMPORTANT NOTES: - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container Found some information here, but I will need to investigate some more. Thank you very much
  12. Still on version 6.3.5 as I need a very stable server. You are now on the 21st version of the release candidate for 6.4. I am following progress closely, however I do not know (and therefore cannot plan) when the stable version of 6.4 will be released. For 6.3 no (security) fixes have been released after 6.3.5. With all the chatter around meltdown I would like to learn the timeline when 6.4 will be released, and if this will take more time, if a 6.3.6 will be released to implement fixes for Meltdown. Regards, Richard
  13. Okay, this is my try to make a change that will survive updates on the docker container. 1. Export the completer docker container contents docker export [containername] > [containername].tar 2. unpack the .tar file and copy the /etc/php7 folder incl. contents to ==> /mnt/user/appdata/[containername]/etc/php7 now we have the php.ini file on outside the docker container. 3. we only have to add an additional path in the docker config (in unRAID) the container path = /etc/php7 will be replaced by the appdata directory provided in the config. to my knowledge I can now safely change the php.ini file in the appdata/[containername]/etc/php7 map. when updates are provided to the docker, my changes will survive. I believe the only problem is when php7 changes are made that do need new files or changes in the /etc/php7 directory. This I do need to test .... could someone provide a sanity check on this? regards, Richard
  14. Hi CHBMB, The installation of WP is not difficult at all, but after the basic install I would like to upload plugins using the normal WP wizards. This is not possible in the standard Apache-PHP or NGINX containers (tried LE also) because the upload is maximum 2MB (as set in the PHP.ini) checkt it with phpinfo() I cannot find a way to change this, is there a way to safely change this parameter? [EDIT] I changed the php.ini file directly by entering the docker container and changed the php.ini file directly in /etc/php7 this works fine for now, but I think that when the container is updated, this change is gone. is there a way to prevent this from happening?
  15. Hi all, I know this is an older topic, but I stepped into unRaid just the other day. After some experimenting I got a Docker container up using chvb Apache-PHP as the basic Docker. Following the directions in this topic I got Wordpress installed just fine, connecting to another MySQL docker, which I use for other stuff as well. (never mind that). However in Wordpress I do have some issues when trying to installing plugins in Wordpress. 1. Wordpress asks for a FTP information --> got this fixed by adding --> define('FS_METHOD', 'direct'); in the wp-config-php file. 2. The issue now that remains (I cannot find a fix) is that I cannot upload new plugins bigger than 2 MB in Wordpress. I do need some help with this 2nd problem. I already discovered that this limit is set in the php.ini file and it is called php_value upload_max_filesize but I cannot change this parameter, as I do not know how to do a change in the Docker container Apache-PHP in a save way (without problems with updates to this container). The other method I tried is changing the .htaccess file in the www root where Wordpress is installed. When I change the .htaccess file I get an error, stating this is not allowed here. The last and 3trd problem I face is that when I try to change the theme for instance, the Wordpress site is not showing the pictures of the themes I have installed already. For some reason Wordpress is not able to show the preview of the installed themes. After installing a new theme, pictures are not shown. Could this be related to the "fix" I implemented for issue 1 ? and how to fix this? Please help, Regards, Richard