Kru-x

I think it is becouse you did the WP installer on your internal address, always creates a lot of havocs. Delete your folders and DB and start from the beginning, ones you have your domain up running then start the wp installer, Kru-x Ps. read some of the threads earlier in this forum, its a common issue that many run in to.

Did you install WordPress from you domain or local? Kru-x

Hi broadcastthebadger, If you have used this docker for a while it is probably that you have the old one, the old one broke and I changed it to another one, should be in said in this forum I think. Anyhow check if you have jwater7/godaddy-publicip-updater in the repository column, if not delete the image and my template and use the new one in the apps library. Hope it helps, Kru-x

Don't worry, Godaddy is a domain name provider and you are paying for it! The service as a website hosting is just a side kick. It won't matter to them if you host it or another provider douse it, same for them and it is a reason they provider an api to change it.. Kru-x

Sa du fick det att funka? Kru-x

Wish it was that easy, 🙂 But all references to pages, post, comments etc. are saved into the Database (thats how WordPress do much of it's workings), thats why it is better to start from scratch or you have to find all those faulty references in the DB manually. As I have mentioned in previous posts, there is good programs (plugins) that will do this for you if you have a site already or is working in a development environment. Kru-x

Then it is that you installed WP on your local ip address first, it's WordPress that redirects to the same ip that it was installed on. To explain what I believe is happening, during installation WP created an index.php page (the homepage) that have a an address of IP:8080 and saves that info in to the database. And even if you change the site's domain he will still redirect to domain:8080. That's why I always recommend installing from your domain first. Kru-x

Sounds like you are only using one instance of a MariaDB, whilst you could, I always make a new instance of the database eg. so two containers for each site ex wp-temp & wp-temp-MariaDB. Makes it much easier to fire one site up and delete it when needed. The "issue" with the webUI, it should auto change to the port that you add in the template, if not you can change it your self in advance view and correct the WebUI: http://[IP]:[PORT:8080]/ it works the same with all containers in unraid. Kru-x

You can create as many instances of WordPress as you like and it seems you have figured it out, create different containers with different ports and that should be it. Seems like you are confident enough to change user permission and wp-config.php, that is good if you are but in a basic setup you shouldn't need to, the MariaDB is accessed by WP as root user with full privileges and the installation takes care of the directions in the wp-config.php file, both if you just use the regular settings in the template. And just a side note, if you start the install from the internal ip address that is the address that is used, might be easy enough to change b4 you have done any changes or added any pages but if you work a bit on the site and then wants to get it on a domain address you are in for a ride, much of the internal working of WP is relying on the info in the DB. I always suggest to do a clean install from the domain name and work from there, if there is a site you have worked on or a development instance, move it to the clean instal of that domain by using a plugin, I always use "Duplicator Pro". Kru-x

Nahhh, it will only replace a file that is missing but not overwriting. So your _.php might pop up again, not that I know what that is , never seen one myself.

Hi, The root folder is the one you created when you added the container, as per below "/mnt/user/appdata/wordpress-temp/". The php.ini is not there by default but you can add one. I have had more success with .htaccess method to increase the upload limit. Kru-x

HI dancue, Personally I run all my containers in Bridged mode, but I know many is using Spaceinvaders guide and are using a "proxynet" that creates a separate "internal" network. Many swear by it and I have read that it might be better for a proxy routing traffic. Having said that, only ones I have had the need to use a specific separate network and even then later on I switched back to bridge mode again and got it working. For me it is just easier to use one network as I know exactly what the different IPaddresses are on each box (i got two servers). You don't need to add a "custom location" as per your screen shots otherwise it looks right and as for your setup, I guess you installed WordPress from your internal ip address and not on your Domain name, eg remove both the WP and MariaDB's folders and add the two containers again, then check if you can see WP's installation page on your local address but without starting the install, then try to connect to it from your domain name and do the install from there. Hope it helps, Kru-x

Thanks for that explanation Squid, didnt know that, Kru-x

Hi ingarb, I understand what you are saying but not why ;-), It works like this, first time you add a container you download a/my template (in this case my WP), then as soon as you save it, it is saved in a template directory with all your modified settings, any subsequent use should use the modified template, do you delete the templates in between? I don't get it, Also why would you try to remove the port mapping, 80 is the port inside the container to communicate with the "outside world" and the port you add is the port you communicate with from the outside. How are you doing it otherwise? Kru-x

Hi, Try to empty your browsers cache. But having said that (and read your message properly :-()) wonder. I never got the hang of letsencrypt/nginx settings , and it seems to be ask in that forum or to make life easy for you use the nginx manager as per previous posts. Then you don't have to worry about settings. Kru-x

Hi Martin, No worries we are all at a stage where we wondering how to do things. I recommend reading up on docker itself, that taught me a lot in my understanding of how containers works. As for your question, you just add a new template with a different name and port, then a new instance (container) of a MariaDB is created. Make sure the folder path is different as well. Hope it helps, Kru-x

No worries, Personally I can't see any benefit using the same DB to different sites more then in a multi-site setup. It is no disadvantage to run different DB's and it benefit separating each instance witch makes it easier should something go wrong. That's the main reason I have not added more variables to the template, I tried to make it as simple as possible. But having said that, each person have it's own preferences and a more confident user can add any variables himself, you can add a WORDPRESS_DB_NAME environment variable to your template. But if I can give an advice I wouldn't bother as per above, still if you insist i would use a software to connect to my database and manually manage the DB's/users/ and passwords. You can leave the WORDPRESS_DB_HOST blank for a new instance then you get presented with the WP installation on startup where you can do it all manually, but with this the user needs to understand what the container and DB is about (thus use a software), in regards to username password and db names etc. The MariDB container is setting the user to root with full privileges and the WP container is using the same to use the DB, in a production environment this should be done manually and should not be using root. Kru-x

Hi hkinks, What are you trying to achieve? You say "if I have a database with different name". On a new install you can name the database to whatever you want by adding the the parameters to the DB template see https://hub.docker.com/r/linuxserver/mariadb (heading "parameters"). If the WP container can't login to the mariaDB container you are presented with the WordPress install where you can add your DB name user and PW. You could also login as root to the mariaDB with a separate DB software and create whatever DB name you like then install WP the same as a above. Remember user and privileges thought. Hope this answered your question Kru-x

Please give more info, the post u r referring to I guess he had the domain name wrong.

Ohh that sucks, You need the ports to divert the traffic thru, if you can't change provider I doubt that you can do anything else then pay up. You might be able to use a VPN but then you are on thin ice and are going to run in to problems all the time. Wouldn't do that in production. Why can't you change, sound strange to me? Shared cable in to units or? Any how good luck and keep us posted, Kru-x

Looks ok, but I believe the protocol should be UDP, don't know if that would make any difference. Hope it works out and for sure ask your provider, if they are good they should take care of their costumers need.

It is for sure NPM, only worry about your IP address first of all, when you add that to any browser and when it is working you should be greeted with a welcome to NPM greeting. Not until then you can start to invoke your containers and certificates. You say that you have forward the ports correctly, but I would double check the settings again. Did you forward too the right IP of your server? Is this the first time you connect to your server from internet? Donno, but I suppose your ISP could potentially block those ports but I cant see why, ask them or find out googling, IF they do, tell them to bugger off and get another provider, you don't have to have a fixed IP, waste of money if you pay extra or the ISP provider charge extra for it. Kru-x

Hi tr0910, I'm not sure what you mean and I doubt that your ISP is blocking your ports, what happens if you go to your ip address in a browser? You said that you had a fixed one, didn't you? The same if you have forward your domain(s) to that ip address, what are you seeing? the same as when you are using your domain as with the ip?

Hi Alex.b I think you are misunderstanding and I am not sure what you are trying to do. Change DB name? Why. The log you see is the log of WP not docker. During the first install WP is loging in to the MariaDB with the root privilege and creating a database inside with the name "wordpress" and user "alex" and setting up privileges for that user, then subsequent login WP is using "alex" as user and "alex" has no privileges to create a database only read and write into that DB, it is only "root" that has that privilege of "CREATE DATABASE". The best way to understand it is to login to MariaDB with a database software and look at the database within, privileges & users, with that you could create a database logged in as root and then set privileges to alex, but still I don't know what you are trying to do and there is not any real reasons to change the database name I can think of. Kru-x

Hi Alex, Its most likely wordpress doing it or you have problems with your share folder. Docker compares the share folder To the one inside the container, if the file is missing he adds it else he wont. Docker wont overwrite any existing files. I would ask in a WP forum, Kru-x