Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Kru-x

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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 . the CSS file is going to point to that address when it should point to 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
  7. 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
  8. You must install a database, MB or MySql. That is also done in a container, nothing must be installed on your unraid server file system except from the docker folders. The only tutorial I know about is this discussion (there is a lot of pointers in some threads) or you can find a French tut here: Even if you don’t understand French you will understand what is going on and if you translate the page it’s even better. Kru-x
  9. You must install a database, MB or MySql. That is also done in a container, nothing must be installed on your unraid server file system except from the docker folders. The only tutorial I know about is this discussion (there is a lot of pointers in some threads) or you can find a French tut here: Even if you don’t understand French you will understand what is going on and if you translate the page it’s even better. Kru-x
  10. My guess is that the plugin wants to connect to your db and ad some tables/row in there but is using a older connection method not compatible with the newer mysql syntax. Try to throw in the --default-authentication-plugin=mysql_native_password in the extra parameter and try to restart the container. If it works it douse if not just delete it and restart it again. I would look elsewhere though, Kru-x ps. I mean in the mysql container if that wasn’t clear.
  11. Hi xcsuperfly, Now you puting me on thin ice, but have skimed over it I think it has to do with "default_authentication_plugin=mysql_native_password". What I believe is that the plugin using an old legacy autentication, "mysql_native_password" instead of "caching_sha2_password" Read about the problem here, I know I have had this problem some time ago. The solution I found at that time was to add "--default-authentication-plugin=mysql_native_password" in the extra parameter in the template (advanced). It is just a guess based on the problem I have had, but I could be totaly wrong. AND it is a lot of fiddle to try to findout a problem like this and in worse case you have to change the docker image itself (make your own one and adjust for your needs, then you are in for a ride 🙂 ) Instead I tend to distrust plugin's that is not updated to the latest and always using and untouched official docker containers ( in this case mysql ). Extremly smart guys that look after them and update them for the mass. If you haven't got a specific reason to use this plugin, maybe look at some others, I use "newsletter", its brilliant. Hope it helps, Kru-x
  12. ?????? You have internet, don't you? Should make no different at all. Kru-x
  13. You can't access it from your local IP, the page addresses is saved in the data base and WP will redirect to whatever address a user is asking for. WP doesn't know your local address, hence the importance to install WP from the domain.
  14. You are far more advance than me Don't think it is WP, you should be able to reach the install even without the DB has nothing to do with it until you install WP. I know people have had problem with cache, try to connect in "private mode". Reinstall and when you can reach the install with your IP, don't do anything just try to connect to it online from your domain, then install. Sorry don't understand the internal DNS thing so I don't know if that could be in the way, Kru-x
  15. Looks right, first try to empty your cache in your browser. Still not sure how you can reach your domain on your local network eg "" should not work , but should work. Try to delete both folders again especially the DB, then see if you can reach the WordPress install by your local IP (don't install anything from your local IP), then try to reach the WP installer from your domain and install from there if it works. Holing my thumbs. 🙂 Kru-x
  16. How did you redirect in NPM, should be to your internal address eg. Looks like you it asks for the domain:port, shouldn't do that. You shouldn't need to have any special settings for nginx, NPM takes care of it. I don't understand your "wordpress works with in local (not via internet)"? Kru-x
  17. Hi Nexius2, Shouldn't be any bigger problem to get you online, but I cant really help with Swag as I have never used it myself nor am I good at setting up Nginx (proxy). Instead I use NPM (NginxProxyManager), makes life much easier and you should also be able to use it for anything else you would like to reach from online like guacamole. There is posts in this thread mentioning setting up WP with NPM, but the most important is to get it to work with your domain first and then install Wordpress. Kru-x
  18. Hang on, why do you say "https://IPADDRESS:PORT"? That is not right, should be your domain, you can't have https on the local IP address.
  19. Check the settings in NPM, have you got "http" selected in Scheme, It must be a setting, it should make no different installing WP. Kru-x
  20. Hi IKWEB, Im not sure if I follow exactly what you are doing, or trying to do, but try this. First delete both the Wordpress folder and the database folder in unraid (to remove eventual old values, from previous installs). Then reinstall both, then make sure you can reach the Wordpress installation on your Domain, going through NPM, and start the install from there and set up your db etc. then it should work. After install you can not reach the WP install from your local ip address, hope it helps, kru-x
  21. Sorry I don't know updraft and can't really tell, you should be able to write in too the folder. Try to sett a different permission on the folder itself. Else as I said try Duplicator, it works great and takes care of any permission issues, at least for me. Kru-x
  22. Hi Bonistir, How was the back-up made and what have you backed up? Only the folders? Most of the settings and data is stored in the DB itself. Do you have a site that you can take a new backup from? If, I suggest using "Duplicator PRO" (a WP plugin), it will clone the whole site + DB and handle all the permissions. Also I use on my unraid "duplicati" docker container to back up the folders both for WP and DB. Though, If it is a heavy site with a lot of traffic you should take a DB snapshot and back up that instead of the DB folder. Only copy and past the folder is going to get you in a heap of problems. Kru-x