Kru-x

Hi Fipship, The image pulled is the "wordpress:latest" that is maintained by the WordPress community, the most stable one is usually the "latest". But the beauty with docker is that you can pull any image that you like. Go to wordpress - Official Image | Docker Hub and chose the tag to the image you would like and then add it to the "repository" option in the template ex. wordpress:6.8.2-php8.3-apache Hope that explains, Kru-x

Hi Casperse, Not sure if I understand you right. But you cant "downgrade" when WordPress is already installed if you do not start all over again from scratch. WP updates internally (the DB) thus it will never be able to be "going back" in time (at least not with docker container), guess it might be a solution for WP itself. Me myself, is always when I develop my sites using "Duplicator PRO" for taking backups and if something goes sideways I just Migrate back again. And for your previous question, not sure but when you install internally the database stores the pages with a URL, so if you go to the homepage and it is installed on ex. http://192.168.1.100:8080 its always going to take you there as this is how WP works internally. I used a proxy and use subdomains to handle different test/dev sites eg https://mysite.com/testsite1but nowadays I use docker on my laptop to develop and only have live sites on my unraid server, ones again using Duplicator to move the sites back and forth. Hope that helps, Kru-x

IF you have built it already, you could use "Duplicator". just make a copy of your site on the local host. Then migrate it to your new domain, works like charm. Kru-x

Hi Aarex, The problem you have is a common problem many people runs into, it is most likely that you installed WP before you added the domain. So internally WP directs to pages xxx.domain.com/my_page so if you installed it on the local ex. 192.168.1.100/my_page the change of domain won't change that, WP trying to find that page that is not there anymore. The easiest in unraid is to stop the container, remove the folder with WP and restart the container again, then connect from your domain and start the WordPress installer from there. Hope it helps, Kru-x

Hi SadRobot11, It is most likely that you have installed WP locally and then try to change to your domain. Look through the previous posts, it is one of the most comment problems. If my assumption is wrong let me know. Kru-x

Hi Thymon, Not sure what the problem is and the ftp_xxx is not related to WordPress and and I don't think the PHP version has changed lately. You could always revert to a previous version that worked, but is not going to solve the real problem. Sorry I am lost on this one, Kru-x

I'm looking in to it now, ill let you know!

Hi Ritzer, See my answer to @N-Lekim, and my template was based on the “official Wordpress docker container” and you can add all the parameters yourself, just a little bit of a fiddle, but you should be able to use your previous template as explained to @N-Lekim, I assume you have already used my template b4. Kru-x

Hi N-Lekim, Not sure I understand what you mean, you have (if you have used my repo b4) the template in “previous” templets. Eg. Just hit the “create new container” then you have all your previous used templets, choose the WordPress (or whatever you called your other ones) and just change the folder where you saved it b4. Kru-x

Hi, See my reply in the next post. Kru-x

Not sure what happened there, can you use your previous template to create a new instance? Remember to change the location of the folder. If, its not my repo that is not working, only CA. Have to look in to it when I get home next week. Kru-x

Hi Jeff, They would not be related, the first one “webUI” is unraids message saying that if you klick on the icon in unraid it might not connect if the port is wrong, you can set that yourself. And it seems like it works if you clicked on the icon for wordpress due to that the next message is WordPress saying that it can’t connect to the database, you possibly made a mistake in your setup when adding the ip/port to your db/wordPress containers. Hope it helps, kru-x

Hi Bartist, You update it as usual through WP, the container wont overwrite the wp core files or your files in the folder u choosen. It's only adding new files if missing or adding all on new install, any subsequent update only the container files themselves if updated. Kru-x

Hi Jurak, Im not familiar with cloudflare but it seems to me that you have a redirect problem. Have you emtied the cache or tried in a incognito tab? What proxy are u using? Kru-x

Hi RichardU, FTP in to your unraid server is possible but I would not recommend it. Not sure about your requirement and systems, but I use windows and connect via a SSH client (Mobaxterm) and there is plenty of other clients for both win and mac (FileZilla is an SSH client as well, have tried it a few times, but find it bloated). When I want to edit files directly I have setup an SHH client in VS Code and can edit the files directly. You should have SSH enabled by default, if not, it is easy to enable it reading the manual. That's all you have to do if you are working on your local network, if you need remote access just setup WireGuard and use a VPN to connect to your network and work the same as above. A VPN is way more secure than FTP and both involves opening up ports to the world! Hope it helps, Kru-x

Hi Dirtyrobot, No any extra configurations should not be needed, I assume you have setup a mail system in WP? Kru-x

Hi Tolete, Yes it is usually a read and write permission issue, check "Health Check" In WordPress, it will tell you what access it is missing. Cant remember exactly what permission WP requires but a quick google search on the subject will tell you. Regards, Kru-x

Hi Drago Prime, Did you install WordPress locally and then tried to add it to Nginx Proxy manager? One of the biggest problem people have with this docker, the easiest is to delete WordPress & DB folders, then make sure you can reach the WP installation screen on your domain b4 you install WP. Hope it helps, Kru-x

Hi ptsiampas, As you said I have not updated this template for years and I am not using wekan for the moment, other tasks got in the way. It is a shame as it is a useful program for people needing it and it should be kept better than I do it. If you care to look after it and improve and keep the support thread up, please be my guest and I will remove my template in favours for yours and point this thread to you. Let me know if you do, R Kru-x

Hi Aehryn, You most likely installed it locally and has a reference in the DB to port 80 (Tower's Main page default port). Its fine to install it locally (port dependent) when you only using it locally but not so when wanting to use it behind a revers proxy. Remove containers and make it work with the proxy b4 you install it from the WP installation screen. Browse through previous posts in this thread, its problem people run in to often. R Kru-x

Hi Jurak, Odd, have you tried to log in from another system (InPrivate window) sounds like a cache problem to me. Or if not it is most likely a DB problem, is it pointing to an empty DB the first time you install? R Kru-x

I am about to build a woo-commerce site and believe I need it for that, thought bitnami/wordpress-nginx would help me but to no avail. Ill keep looking, Kru-x

I stand corrected! Just playing with the container bitnami/wordpress-nginx and they do exactly what you are suggesting and they know what they are talking about, so I am for sure wrong in my assumptions. Haven't given it much thought before and has not seen the need for it but might have to reconsider. Kru-x

Have you given the user "wordpress" full read and write access to the "wordpress" db in mariadb? Sounds like you haven't, Kru-x

And after reading your post thoroughly :~(): the container only copies the files the first time to the folder, any subsequent restart docker leaves the existing files and only adds files missing, thus if something changes in the file docker will not override it. But then as you said you should leave all file AS IS except for the wp_content, so you have a point. The read and write access will be different in the container and WordPress wouldn't be able to update the files internally so the internal update would not work, you would have to wait until the container is updated I believe, so you would most likely get in to heaps of problems and I wouldn't recommend it, but then I am not an expert so I could be wrong. Kru-x