Kru-x

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

No worries, Just remember to start the installation of WP after you got the NPM to work and can connect to the site by your domain. Else WP is going to try to redirect to your internal IP, you gona get the same problem when you are moving your sites if you are not careful. Best is to use a plugin to migrate your whole site, ill use "Duplicator Pro" for moving my sites around when needed. Kru-x

The 0 in the MariaDB setting is telling the container to not use a password (blank) for the root user, WP is trying to login to the DB with the password 0 that you used as password in hence it didn't work. You can set a password, if other then 0, then you have to add the same password in the WP template. Kru-x

So that was not the problem? I think you might get the "Error establishing a database connection" on a wrong password as it is trying to use the root user for the DB. If not mayby try other ports, 8080 is often used by other containers, but then you should get a fault when starting the container. Is your settings looking like this? (see attached screen shots)

WP WORDPRESS_DB_PASSWORD: left blank? 0 in the MB database means no password. Or?

Hi thany, You are right, I should probably do a "getting started" guide as it all change a few years ago making the --link option redundant and that the unraid team rightfully deleted my MongoDB that was setup for wekan in lieu of the official newer MongoDB container that has different credentials, but its all there in the latest post's how to set it up today. The reason I have not bother too much with it is that wekan is more for companies and organizations that probably would have an IT guy to figure out the setup. For me as a nob, I have moved away from wekan even if it is a nice system. I have gone for simpler systems and more all around like nextcloud (not that NC is a simple system, very powerful) that has the similar functions and more other goodies to choose from. As for integrating the MongoDB, not sure if it is a docker out there to do that, but the main reason not to, is that it is better to separate the program from the DB and have two separate instances for easier and safer retention of the data. Most and many containers are doing this and it is just to get the head around it, then most containers are working in the same way with similar setup. Kru-x

Hi tr0910, I have no doubt that they would run smooth and you most likely have a quicker/better setup than many of the providers out there, not knowing yours thought. You'll be surprised of how easy it is, the storage is your's so no problems with file sizes. The only caution I have is with the credit card processing, not that I think it would be much problem to run it but you might want to be able to track the IP-addresses of your clients or purchasers. I know there is a workaround but never had the need to bother about it, but WP is inside a containers and will only see the IP-address from inside the container. Believe it is a setup in Nginx that can forward the right addresses to inside the container. Hope it helps and keep us updated, Kru-x

Smart move, So you already have development site that you want to move, and non of the above working? The "problem" with WP is that all info is stored in the DB and it wont help to just copy the files over, if the site is something you have work on for a while that you don't want to loose the easiest way that I use all the time is to install the brilliant plugin "Duplicator pro" on your development site and compact your whole site and transfer to the root folder and install it again, that will take care of all redirections. You could possibly change the site's url with one of the suggestions in https://www.wpbeginner.com/wp-tutorials/how-to-change-your-wordpress-site-urls-step-by-step/ Hope it helps, Kru-x

It's how you installed it and wordpress is directing the home page to :80 port, I assume you are playing with it locally. Try this, login to wp-admin, go to settings and see if you can change the home site address to 192.168.1.9:4441, if you can't change it try to update permalinks, and if still not working delete both MB & WP folders and reinstall again. Let me know what worked, quite common question and I usually just recommend to reinstall. But well give it a go, Kru-x

Hi Djoss, Sorry to have bothered you, turns out that it is not NPM after all. The problem is strange, I have two servers with the exact same setup and if I have the onlyoffice on one server the other won't talk to it but the same will. And even more odd the one with NPM on it wont talk to to an instance of only office on the same server nor the other one. Don't know what happening! Kru-x

Hi Alex.b, By default there is no php.ini file in WP, but you can add one manually in the root folder. See https://stackoverflow.com/questions/6165558/how-can-i-find-my-php-ini-on-wordpress/42347382 If it t is to increase the download size, I'll use the .htaccess method to do so. Kru-x

I have tried to enable that but still wont work. I am not confident in Nginx and the configs but one setup is talking about that you have to add your .key file to the Document server, NPM uses .pem files. Config for just Nginx is looking like this, meybe you can make sense of it: # only office doc server server { listen 443 ssl; server_name documentserver.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_docs OnlyOfficeDocumentServer; proxy_pass https://$upstream_docs:443; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-Proto $scheme; } }

Hi, For Varible MONGO_URL use: mongodb://192.168.1.121:27017/admin, witch is the admin login for MongoDB. Also if you are behind a revers proxy the varible ROOT_URL should be https://yourdomain.com, else if you are only using it internally it should be http://192.168.0.37:5555 I know you can export from Wekan to another instance, but if you can live without the old todo's and depending on how many, I would start again. Another factor I would personally consider is the requirements and future setup. I moved away from Wekan myself, not that I don't like it it's brilliant, but it is for professional use "like big organizations" and for my to remember to water my garden or feed the Cat 🙂 is for sure an overkill. I use Nextcloud for my file system and it has a good task manager as a plugin, much of my needs consolidated in to one. Kru-x

HI Djoss, I love that you have added this to unraid and I use it for all my proxied containers and the all works mint, EXCEPT one "onlyofficedockument server". Pulling my hair on this one, the manual talks about X-Forwarded-Proto and X-Forwarded-Host and I suspect it is the call back to 443 that buggers it up, either my settings on the different containers (owncloud, onlyoffice, or NPM). Have you got any clue who to set it up and connect to it? All containers works perfect, I can connect to them all proxied but the ony thin is that I cant connect from nextcloud to the Onyloffice servera and get it to call back. Any pointers would be appriciated. Kru-x

Did you do a fresh install from your home local address or from you domain address? it’s your permalink that is wrong I guess. If you can, login to wp-admin.php go to settings and permalinks and update them. Edited: if you have not done anything before you read this, it’s your cookies in your browser. I can see your page properly, kru-x

Nahh I was thinking NPM but shouldn't be needed, can you reach it from your internal address b4 installing, and as I understand it you still get the wrong redirects even after installing fro your domain? One guy had problem with a setting in NPM using 8080 maybe it is some clash there with another container, but sorry I am a little bit lost on this one and it shouldn't be. If you follow the templates and install from your domain it should be really a easy setup, I have done it on several sites and even now I am playing with a test one to try to replicate your problem but it just work.

Hmmm, Have you deleted the Maria DB folder and WP folder in between trying, It looks like it is still trying to redirect you to the internal address. And weird with NPM, it was when I switched to it, mine started to work perfectly. I have all my containers (exposed to internet) trough NPM and I have no problems. The database folder HAS to be deleted in between else the old values is still in the DB. There is a few previous problems like yours that has been solved by starting from scratch and it should be fairly strait forward especially if you can reach the installation from your domain. So in short delete all 3 folders, install the MariaDB and WP, as per templates, if you can reach the installation of WP with your ip address, just leave it to that (without starting the installation of WP) and try again from NPM and do the installation and ask for a new cert from within. Hope it helps, Kru-x

How did you install WP and are u using a local network or a domain? Guess domain, using NPM. The port is Nginx's (NPM's) internal port that is 8080 and I believe that's why it shows that port if the site can't be found. Can you login to wp-admin? If check in "settings" of the website address, else delete both container and wait to install until you can reach the WP installation from your domain. Kru-x

As dom1 said, you can fire up as many instances you would like, just do exactly the same as with the first ones, just with different names, ports and storage folders. Kru-x

Sorry I read your email to quick and didn't realize it was only at the themes that didn't work. Its strange, just tried a test site and I have not got that problem. Have you change any settings in "general settings" in WP. Don't think it is a container/unraid problem anyway, it's quite a common problem with WP and is mentioned in several forums. I would start all over again, delete both folders and reinstall both WP & the DB, when installed go strait to theme and try again. Guess most problems with this is a redirection issue from apache (http server installed in the docker). Happens easily if the settings are wrong in WP. Hope you solve it and let us know, Kru-x