Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Kru-x last won the day on May 18 2020

Kru-x had the most liked content!

1 Follower

About Kru-x

  • Birthday 09/28/1966


  • Gender
  • Location

Recent Profile Visitors

1871 profile views

Kru-x's Achievements


Explorer (4/14)



  1. 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 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
  2. 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
  3. 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 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
  4. Sorry, I am the worst person to ask about premission's, still after all these years I am still just 777 everything! Kru-x
  5. 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
  6. Reinstall from the beginning on the new port and/or change the site adress to ip:port-number Kru-x
  7. 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 Hope it helps, Kru-x
  8. Clear the browser cache? Try your site in a private window in your browser.
  9. 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
  10. Glad that you figured it out and thank you for sharing you findings, Kru-x
  11. 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
  12. Have u tried to use a migration tool, such as wp-migration? Seems to be a permission problem. Kru-x
  13. 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
  14. 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
  15. 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