Kru-x

Hi sjoerd, I can follow your thinking and I wonder myself, but WordPress updates internally and gets updated on the fly, thus you always have the latest version keeping it like it is. Guess they update the docker container for a new install. I think you get in to more trouble to do it that way, than not. Question back, as I see that you are installing new instances. Do you get a problems in "Site Health" on a new install? Eg. open tools/settings/Site Health and see if you get any recommendations of faults, I have a few pesky ones that I don't know how to solve. like "The REST API encountered an unexpected result" & "your site could not complete a call back", doing my head in! Regards, Kru-x

Try the .htaccess method, if it is not in your root folder you can add it. Kru-x

Yea that's correct, I'll "pair" one MariaDb container for each of my application/container that needs it (and I have 10 of them by now). It might seem like an overkill, but it is little overhead to run a DB container and it is more hassle/error prone to use one container for all. Maybe it is due to my lack of DB knowledge, but when you bugger one up, you are going to be happy that the other ones are running like nothing have happened. Promise! Kru-x

Hi mjeshurun, My bet it is a DB problem, eg username, permission problem or similar. Try to login to that DB with that username/password with adminer, (not with full admin access) If it works WordPress should work. But I recommend as in many previous posts, not to use the same DB instance, it's easier and less error prone to fire up a second DB container and pair it with the Wordress instance with a different port number. Kru-x

HI Rocka374, Not sure what you mean connecting via Nginx by socket, wordpress connects directly to the DB and I dont know any other way to do it, so im not sure how to answer that one. The docker container used is this official one https://hub.docker.com/_/wordpress/. You can use any version of it and if you add the flag "wordpress:<version>-fpm" in the template you get the FastCGI implementation for PHP, it says furter down on the page for the container in docker hub. Hope it helps, Kru-x

Yea that's what I am doing with my router. But the VM might not be able to use 80 or 443 depending on your setup. My unraid interface is using port 80 and 443 is used by other container. But just forward 80 to say 88 and use 88 on your VM, same with 443. But it depends on your setup, they might be free. Kru-x

Whoooa, That's a request and a half and I am not sure about the answer. I doubt that you would have a stack for that. I know Redis can be used as a separate docker container in Unraid. I am using Nginx Proxymanager, but you would have to have a container with Nginx and fastCGI + PHP-FMP as I understand it. There is a way as I understand it, read quickly about it https://blog.joshwalsh.me/docker-nginx-php-fpm/ if you could use that container and make your own template for it in Unraid it could be possible I guess. You would be running each site in a separate container + DB and possible Redis in one and the Nginx as per above in one. but this is way over my head. Hope it gives you a few ideas but sorry I couldn't help more, Kru-x

Sorry, I am the worst person to ask about premission's, still after all these years I am still just 777 everything! Kru-x

Sorry for the late reply, but I think you are on the right track. The container needs to have write and read privileges, so chmod should do it. Kru-x

Reinstall from the beginning on the new port and/or change the site adress to ip:port-number Kru-x

Hi, There is some things to try, Change it back in wp-config.php Clear your cache There is heaps of info on it doing a Google search, here is one https://wp-me.com/cant-access-wordpress-after-changing-site-url/ Hope it helps, Kru-x

Clear the browser cache? Try your site in a private window in your browser.

Did you start to install WP on your local address? Start your install after making sure you can connect to the installer through your Domain, then you shouldn't need to do the steps above. Kru-x

Glad that you figured it out and thank you for sharing you findings, Kru-x

The log would be in the container itself, sorry not sure but still think it is a permission error. Try the migration tool, usually solves any problems, especially DB troubles. Kru-x

Have u tried to use a migration tool, such as wp-migration? Seems to be a permission problem. Kru-x

Halloj KilianDee, I use the .htaccess method and it works great. Just toss a .htaccess file in to your root folder. Eg where your docker container mounts, most likely in your appdata/yourcontainer, and in the file add: #If more upload capacity is needed, my addition php_value upload_max_filesize 64M php_value post_max_size 128M php_value memory_limit 256M php_value max_execution_time 300 php_value max_input_time 300 kru-x

You just open the template file in your list for ex. wordpress (if that what you have named it) and rename the next template to wordpress2, then you have to choose a different folder. I name the folder exactly the same as the container eg "wordpress2" and the port number. The newly named template will be saved in your list of templates you have, the old still remains. You could also choose the app from the comunity app page, same same and this can be done with all containers in the same way. It is just how unraid templates and docker works. Kru-x

And I guess after reading your post through properly 😏 I didn't actually answered your question. Hups. But you just name the second wordpress installation differently and use a different folder for the installation as well as a different port offcourse. Then install it as you did with the first one pointing it to the db of your choice. Then you should be up and running. Kru-x

I do backups of all my containers and it might seem like it is complexed but it isn't. I name them the same as the application container eg - I pair them like, wordpress and wordpress-db than they show up next to eachother. Easier to just add a new db container than add/delete db's in one container and I believe it makes it more readable and they might even work better on their own. There was one guy earlier in the thread that got a corupt db and he didn't know when it started, thus he had to remake his whole setup. But it is as I mentioned a personal preference, it will works either way. There is no reason why you couldn't add a separate db in your already existing container, it's just to point the second wordpress application to that db name. Kru-x

Hi, Yes you just start a new db container. But it is a preference and personally I have one db container for each application. The problem is if that db fails you loose all your data for each application whilst if you have one for each only that one fails. There is not much overhead to run one for each and I all the time trying out other applications, crank up two containers and when I am done I just toss both of them. kru-x

Hi darrenyorston, This is talked about before in this thread, have a quick skim throught them and most of the answers are there. But in short: its actually really easy, but dont use the same DB for two different sites, you can get in to a lot of headace. Just do as you did with the first one, spin up a new MariaDB with a diffrent folder and Port number, and the same with your second Wordpress site, then you just route to that site in NPM by the port number. Let me know if you run in to problems, Kru-x

Hi Tom, Yes I ment the browser cache and if that isn't working I still think it is due to how it's installed. Can't see your site but you have to install the site from your domain, several people have had that problem as WP saves all the links and redirects in your DB. Eg. if you installed WP on your local host ( ex . 192.168.1.100) the CSS file is going to point to that address when it should point to yourdomain.com. So to fix that delete both folders, WP & DB then reinstall the containers and before you do the installation from the WP installation screen, connect your domain. Than when you can connect to the WP installation page from your domain, and not untill then start the installation. Then you can point the DB to it's local IP address. WP will recognice that you are on your domain and add all the correct redirects. If you have an existing site that you would like to use, use the "Duplicator Pro" Plugin or similar to migrate the whole site to the new domain. Works really well and I do it all the time with my sites. Hope it helps, Kru-x

Clear cache?

Hi Tom, I believe it is due to how it is installed, try to delete both folders and then you should see the installation page of WP when you go to it, if you connect to the DB from there it should work. R K-rux