tillkrueger

Thanks for that instruction, uldise, but as easy as that may be for you, I still struggle very much with the correct syntax of how (and where exactly) paths like that are added and referenced... So, as for "map you unraid folder to docker path in your Nextcloud docker settings.", I would need to use the "+Add another Path..." link at the bottom and add it there? I have been there before and tried my luck, but was confused about the difference between the "Container Path" and "Host Path" fields...my unRAID user share lives at /mnt/user/unRAID, so that goes into the "Host Path" field, I take it, since one can actually select it with the shown directory structure that pops up? if that is correct, then what goes into the "Container Path"? The Nextcloud container path? (which would be /mnt/user/nextcloud/) Once I filled that in correctly, I can move on to the second part of your instructions, which I am also somewhat confused about. To add to my confusion, when I last tried these instructions, which I also found somewhere else, on reddit maybe, and I added those paths (probably incorrectly) and hit "Add", the Docker showed me some verbose feedback of restarting itself with these new settings, and then disappeared entirely...gone, even from the Dashboard, leading me to having to re-install it from scratch.

Ok, since I didn't get any responses to my question above, I ended up deleting and re-installing the Nextcloud Docker into its own subfolder, and it all seems to work as intended so far, so that part of my question is now solved. But even after following along to various instructions given in online videos and forum threads, what I am still stuck on is properly configuring the "External storage" feature to point to my unRAID user share (or any of its sub-folders)...I have tried "Local", and "SMB/CIFS" unsuccessfully...after clicking the checkmark on the right, the icon to the left of the folder name field spins, initially, but always results in the red exclamation mark icon. What am I doing wrong?

Thanks for creating this! Finally tried to tackle the install of this, following along SpaceInvader's install video, and after some initial troubles, got it to work. What I do notice is that even though I configured NextCloud's data to resolve to my main unRAID user share containing all of my production data (/mnt/user/unRAID/), I cannot see that data when I log into NextCloud. When I followed SpaceInvader's instructions, I left the "Data Folder" field at just /data as per his instructions, but was that really the correct thing to do? I should add that I did *not* create a new share for nextcloud, as per his instructions, thinking that I'd want nextcloud to use my existing unRAID user share instead. Since I don't like to see all of NextCloud's files in the root of my unRAID user share, where and how would I be able to change this, after the fact, or would I have to re-install the Docker entirely to change this now? But since I would really like to let NextCloud see and use my entire unRAID user share, how would I accomplish that? Could I have NextCloud *both* keep all of its own files in a user share called "nextcloud", *and* allow it to see my entire unRAID user share? I hope that wasn't too confusing of a question. 😕

Stumped about what happened, but when I first set up ZeroTier, I was able to see my unRAID in the MacOS Finder's Network section. At some point, I don't know when and why, it disappeared from Network again. Now, many months later, I am trying to see what can be done to connect to unRAID again from within Finder, but even after re-tracing all configuration steps, I fail to succeed. The ZeroTier app on my Mac shows Status as OK after I solved a PORT_ERROR message, and I double-checked all network id settings and such in the ZeroTier settings on unRAID, restarted it numerous times, made sure it shows as "Online" in my.zerotier.com account, but nothing seems to bring my unRAID sytem back into my Network. Where to go from here?

3 days ago I posted a question here, about how Nginx in the letsencrypt docker can be made to do what the .htaccess files on Apache does. My programmer is moving a database driven site of mine from Bluehost to my unRAID server, running the letsencrypt and maridb dockers, and had this .htaccess file: <ifmodule mod_rewrite.c> RewriteEngine on RewriteBase / RewriteCond %{REQUEST_URI} ^system.* RewriteRule ^(.*)$ /index.php/$1 [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php?/$1 [L] </ifmodule> until realising that Nginx does not read/obey .htaccess (at least that's how I understood it). I think he said that he needs to enable mod_rewrite. does anyone know how this can be accomplished with Nginx? I hope to find an answer soon, as I don't want to have to pay for yet another month of Bluehost cloud hosting. 😕

feels a little weird to be posting new issues into this mammoth discussion, but so far, miraculously, most if not all issues seem to be addressed...so here I go again: I have been trying to move an important development website from Bluehost to my unRAID server. The site uses MySQL databases. The programmer I have used to help me develop this site has been trying to get it to run from within my letsencrypt docker, but has informed me that Nginx ignored the htaccess file. I can only acknowledge what he tells me, as I simply don't understand enough about what differentiates Apache and Nginx to help him with this part. He created the following .htaccess file: <ifmodule mod_rewrite.c> RewriteEngine on RewriteBase / RewriteCond %{REQUEST_URI} ^system.* RewriteRule ^(.*)$ /index.php/$1 [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php?/$1 [L] </ifmodule> What needs to be done in order for Nginx to work the same way as Apache does with this .htaccess file?

Might u have a way of setting up a VPN on your server, to separate the public and internal parts of your unRAID system, Tabasaki? I have my unRAID webUI running at port 8008 of my VPN, so I can access it at (in my case) 10.0.195.2:8008 *only* after connecting with OpenVPN, and as far as public access goes, *only* port 80 is exposed for my static IP address which points to letsencrypt’s Nginx server. That way you could safely SFTP, SSH, and do everything you need to do “under the hood”, with minimal public exposure of your unRAID server.

when you say "unraid side" and "container side", do you mean that I need to use the "+ Add another Path, Port..." option in the Advanced settings of the Docker's "Edit" page? (see attached) And then choose "Path"? so if I wanted to move the www folder to - say - unRAID/Sites/avpmatrix/, what would the correct settings/syntax be for those input fields?

thanks, aptalca! I shall try to wrap my head around that after this new IT guy I hired is done migrating my Bluehost account to my unRAID server.

I think I asked this question before but still fail to understand: could someone explain to me, step-by-step, how to move/redirect the letsencrypt/appdata/www folder from my SSD cache drive, where it is now, to the unRAID array?

I noticed that when I go into PMA (phpmyadmin), it says "Server connection: SSL is not being used". Not sure whether I tried the right thing, but after a few Google searches, I installed the Really Simple SSL plugin, which first warned me: "You run a Multisite installation with subdomains, but your site doesn't have a wildcard certificate. This leads to issues when activating SSL networkwide since subdomains will be forced over SSL as well while they don't have a valid certificate. Activate SSL per site or install a wildcard certificate to fix this." which is curious, as I installed WP Multi with the subdirectories option, which is also reflected in in my wp-config.php file: define('MULTISITE', true); define('SUBDOMAIN_INSTALL', false); define('DOMAIN_CURRENT_SITE', 'collabatory.com'); define('PATH_CURRENT_SITE', '/'); define('SITE_ID_CURRENT_SITE', 1); define('BLOG_ID_CURRENT_SITE', 1); why would that be? In any case, just to give it a try, and weary of the wildcard certificate warning, recommending not to activate networkwide, I chose "Activate SSL per site"...after going back to PMA, though, I still get then "Server connection: SSL is not being used" warning. Am I thinking too simplistically here? Are there other steps required to have all aspects of my Wordpress site (and all sites, if I can get it to work networkwide) be recognised as being SSL?

thanks for that link, zandrsn...a thorough treatment of this challenge, indeed, albeit too late for me. I managed to get it to work by scouring for disparate pieces of information, and piecing it together that way, plus some guidance from aptalca, but this link should be displayed prominently on the top of this thread, maybe, as it skilfully addresses one of the more popular reasons why people may want to run a server on their unRAID system. Thanks again!

bingo! it is finally resolving without the www...thanks so much for your guidance, aptalca!

so, going by their instructions, anywhere in the db tables they pointed out (wp_blogs | wp_options | wp_site | wp_sitemeta) where I now see https://www.mydomainname.com", I can just delete the www. and save the table, and that should solve my issue? I just exported the database, as it is now, which should allow me to re-import it, should anything not work right anymore, afterwards, right? well, here we go...crossing my fingers that this will do it.

that sounded straightforward, but apparently it isn't as easy as that when you have a WP multi setup like I do. I found this link with instructions, and just installed the phpmyadmin plugin, but am somewhat apprehensive about doing this for a first time...hope I won't break anything! https://wpengine.com/support/how-to-change-a-multi-site-primary-domain/

When going to mydomain.com in a Safari private window, it still resolves to www.mydomain.com. Yes, WP is set up in the root of the letsencrypt www folder. I don't remember explicitly telling WP to use "www.mydomain.com" during install. If I inadvertently did, where would I be able to check and change that?

I see...ok, here is what's in mine...my un-schooled eyes don't see something that looks like a re-direct in there, though: ## Version 2018/09/12 - Changelog: https://github.com/linuxserver/docker-letsencrypt/commits/master/root/defaults/default # listening on port 80 disabled by default, remove the "#" signs to enable # redirect all traffic to https #server { # listen 80; # server_name _; # return 301 https://$host$request_uri; #} # main server block server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name _; # enable subfolder method reverse proxy confs include /config/nginx/proxy-confs/*.subfolder.conf; # all ssl related config moved to ssl.conf include /config/nginx/ssl.conf; # enable for ldap auth #include /config/nginx/ldap.conf; client_max_body_size 0; location / { try_files $uri $uri/ /index.html /index.php?$args =404; } location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } # sample reverse proxy config for password protected couchpotato running at IP 192.168.1.50 port 5050 with base url "cp" # notice this is within the same server block as the base # don't forget to generate the .htpasswd file as described on docker hub # location ^~ /cp { # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; # include /config/nginx/proxy.conf; # proxy_pass http://192.168.1.50:5050/cp; # } } # sample reverse proxy config without url base, but as a subdomain "cp", ip and port same as above # notice this is a new server block, you need a new server block for each subdomain #server { # listen 443 ssl; # # root /config/www; # index index.html index.htm index.php; # # server_name cp.*; # # include /config/nginx/ssl.conf; # # client_max_body_size 0; # # location / { # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; # include /config/nginx/proxy.conf; # proxy_pass http://192.168.1.50:5050; # } #} # sample reverse proxy config for "heimdall" via subdomain, with ldap authentication # ldap-auth container has to be running and the /config/nginx/ldap.conf file should be filled with ldap info # notice this is a new server block, you need a new server block for each subdomain #server { # listen 443 ssl; # # root /config/www; # index index.html index.htm index.php; # # server_name heimdall.*; # # include /config/nginx/ssl.conf; # # include /config/nginx/ldap.conf; # # client_max_body_size 0; # # location / { # # the next two lines will enable ldap auth along with the included ldap.conf in the server block # auth_request /auth; # error_page 401 =200 /login; # # include /config/nginx/proxy.conf; # resolver 127.0.0.11 valid=30s; # set $upstream_heimdall heimdall; # proxy_pass https://$upstream_heimdall:443; # } #} # enable subdomain method reverse proxy confs include /config/nginx/proxy-confs/*.subdomain.conf; # enable proxy cache for auth proxy_cache_path cache/ keys_zone=auth_cache:10m;

Is there a site config file inside letsencrypt (and if so, where?), or you mean at my domain host?

I have three A-records (empty, *, and "www"), and deleting the A-record for "www" did not lead to the desired result...typing in just mydomainname.com resolves to www.mydonmainname.com. How can I avoid that? I just selected for Wordpress multi sites to go into subfolders, rather than subdomains...not my preferred way of doing this, but so be it, for now. I'd still like to know how to have it resolve to my domain name without the www, though, if anyone knows.

not to digress too much, but does anyone know how to change my domain name from "www.domainname.com" to just "domainname.com"? It's probably something I'll have to do at the DNS settings of my domain provider, right? what exactly needs to be done?

I followed instructions on a Wordpress forum about how to increase the upload limit for a single site (since I am planning to set it up as multi-site), which said that one should create a php.ini file in the wp-anim folder. So, I deleted that one and restarted the docker, and lo and behold, it says Maximum upload file size: 2 GB although I now wonder whether it said that even on my last restart, because I was about to write "it says "2MB" again, because my eyes saw 2MB when really it said 2GB. does php-local.ini always override any other php.ini? I am asking because I'd like to assign different upload limits to different sites which will be hosted under WP multi-site. thanks for your help, aptalca!

I set WP up inside the www folder of the letsencrypt folder, so that means it's set up in the container, right? I still don't really understand what reverse proxy is and does, but shall research that soon...comes up so often, here, that it must be something I will also have to deal with sooner or later. not sure why it works for you and not for me...is the syntax I used correct? 2048M would be 2GB, and that is how I would write it, right? and 3600 would be an hour in seconds, correct? just trying to prepare for some rather large video renders that need to be uploaded from time to time. hmm, what else could I do to trouble-shoot this? restarting the Docker is usually enough to activate changes made in the ini files, correct? do I need to change both the php-local.ini *and the php.ini file that I created, or will php-local.ini override the php.ini file inside of the wp-admin folder anyway?

sorry to butt in, but could someone tell me what I have to do to increase the max upload limit with letsencypt and Wordpress? I added the following to both a php.ini file that I created inside the wp-admin folder, as well as adding it to the php-local.ini file inside letsencrypt/php, and restarting letsencrypt: upload_max_filesize = 2048M post_max_size = 2048M max_execution_time = 3600 Wordpress still limits me to a max upload size of 2MB, though. What am I doing wrong?

after some searching, I found references that suggested the mariaDB docker, and instructions on how to configure it and set up a database via terminal: https://technicalramblings.com/blog/how-to-set-up-a-wordpress-site-with-letsencrypt-and-mariadb-on-unraid/ it really made me sweat to do this, knowing so pathetically little about terminal commands and just blindly following instructions, then getting an error about it not being able to find/connect to the database (I used "localhost") until just taking a chance with using the VPN assigned IP address and the port I set up as per the instructions. I am now happy to report that I was able to install Wordpress and log into its admin panel...so far so good!

tried both of those ways of formatting the date, but no change when restarting Krusader. I have USA as us already. I'll put this on the back-burner for the moment, as it's not a show-stopper, but will come back to it when I have to. thanks, binhex!