Kru-x

Wonder if you got it to work? It shouldn't be needed to do any CPU pinning, as you pointed out it won't use much overhead at all. My server is a 8mb ram micro server and it doesn't grunt at all. But I am not sure why yours is slow, it shouldn't be and I doubt it is the connection between the containers. Is others working as they should? Sorry, i'm not sure!

I'm not sure, that problem usually indicates that WP can't reach wordpress.org server due to internet connection. I don't think it's a docker/unraid problem and the only problem I can think of is if you have changed network type (normal is "Bridge") so your container can't reach internet.

That is exactly what I meant 🙂, now both "server" and "www" as subdomains get directed to your server. AND, not that I have anything to do with it but what's the deal with the "server" as the subdomain, not thinking about getting "unraid" on that one I hope. :~( Kru-x

Hi Nelinski, This docker is only changing the ip address for your GoDaddys domain when your ip address changes and you only have one (per domain). You will have to add your subdomains in GoDaddy, Ex. I have my main domain "mysite.com" and my subdomains like "cloud.mysite.com", "music.mysite.com" etc. those subdomain's is added in Godaddy. GoDaddy is directing ANY request to *.mysite.com to my server's IP address where Nginx Proxy Manager takes care of the directing the request to appropriate container. Hope I understood right and that it helps, let me know, Kru-x

Sorry for the late reply, are the domain name filled in properly in the template? Seems like it complains about that?

Corecctemundo, you can fire up as many instances of WP as you like and NPM can direct to each and everyone of them on a new domain. Or like me, just add a subdomain at your domain provider ex. mysite.com, cloud.mysite.com, music.mysite.com, todo.mysite.com etc etc. and issue a new certificate for each of them. Kru-x

Yea, in NPM just add a Redirection Host with domain name "www.yoursite.com" and redirect to "yoursite.com" and under SSL request a new let's encrypt certificate, then you get a new certificate for "www.yoursite.com", then if anyone uses www.yoursite.com they will be redirected to the right address. On the other hand why would you need to :~), if a user use www just polity ask him not to, just an interesting exercise though! 🙂 Kru-x

I have my sites registered with Godaddy and they have added www as a subdomain already, guess yours is the same. www in front is "old school" and is not much in use today, but some use it and therefore the domain registrar add it automatically. You should be able to redirect your www.yoursite.com to yoursite.com and you have to ask letsencrypt for a new cert for www.yoursite.com, that is how yo do it with a subdomain. I was curious about the problem and it worked fine doing it with mine Kru-x

What I gather is that the https://www.yoursite.com is another domain, so it is directing to a site that wont exist (remember I said that I have a domain called cloud.mysite.com that I have NextCloud on, just the same). If you feel that is a problem you can redirect that site to yoursite.com.

Puhh, I am glad it worked! No worries, have fun "home site'ing"!

If you go to 10.10.7.4:8085 in your browser what happens, WP installation screen? or? Forget about the proxy!

Each container and the folder for that container in app data, depending on how you named them, marked in blue! Eg. both WordPress and the WordPress mariaDB.

Then it must work, delete BOTH folder again, reinstall and see if you can connect locally. Do not start installation at this time just close it. Then try to adjust the proxy the same as for nextcloud. When you can see the WP installation with your external address you should be good to go!

I think this could be your problem, there was another guy trying and I am not sure if the WP container can talk to the DB on different network types, this is over my head. But I don't understand that people do, I have all my containers on bridge'd network. But strange thing is that you sent a screenshot where it looked liked you could connect to the wordpress installation, have you ever got that far? Eg. been able to connect to it by using 10.10.7.4:8080 in your browser?

Then the proxy is working as it should. A WordPress address has nothing to do with it, you can direct any address to any container so you can use whatever. let say you have youraddress.com directed to the WordPress container, then you have yourcloudaddress.com (or as me cloud.myaddress.com) directed to the nextcloud container etc. etc. But it is important that you start the WordPress installation when your address is working, not before. Else WordPress redirects (thinks) it is on the internal address eg. 10.10.7.4:8080/mypage and then you will get a 404 error or proxy error.

What is proxynet in the above screen shot? Is it your container? Should be bridge and use another port as I think the port is used by unraid interface!

Yea you should, is nextcloud working and you can connect to it with your external address(through proxymanager)?

But you have time to "sudo" install packages? That's when my head starts spinning. For simple things like using standard containers in unraid, you really don't need to know much about it, just the settings. But you'll love docker and the power of it if you dig in to it and you get the hang of it!

Ok, Is your unraid server IP 10.10.7.4 ? What container port are you using for WordPress? the port 9999 was just an example and should be the port of your WordPress container (or any container port that you forward to). Only use Forward SSL check until you have it working Have you redirected your routers port 443 & 80 to NginxProxyManager's ports? And do not start the WordPress installation until you have this above working and you can connect to it with your google address, eg. delete both folders and reinstall bot containers as per what I mentioned earlier.

NginxProxyManager is a reverse proxy manager with nginx & letsencrypt built in, it can handle all your proxies, read up about it at https://nginxproxymanager.com/guide/ Add your domain name and direct it to your internal WordPress container, Scheme: http, Forward Hostname / IP: "server IP (ex. 192.168.1.100)", Forward Port: 9999 then request a new SLL cert with letsencrypt and away you go. Its easy as that! Kru-x

You can have as many as you like, just add a new one with a different name ex. my-wordpress-MariaDB then you have to choose a different port. All containers have to have different ports, then in the WordPress template add the ip:port of the DB container. See post: for explanation of settings. Hope it helps, Kru-x

I get that, but it is better to separate the different systems and pair them together eg my-wordpress & my-wordpress-MariaDB. Then you can toss it away/copy and without risking to bugger up the other one. NginxProxyManager will sort out all your proxied redirections and it is really easy. Kru-x

Don't use the same DB, just add a MariaDB with another name and port.

Did you delete the folder for the MariaDB as well?

Get this question ones a a while and I am not that confident in NGINX proxy settings, I recommend using "NginxProxyManager", spare you a lot of headaches. If you still want to take the more manual route please ask the question in the "Letsencrypt" container support, but one thing I see is that you are redirecting to a https address when the redirection should be internally to ex. http://192.168.1.100:8080