figured it out, long day

I'm using Cloudflare tunnels on my Unraid server. I've successfully got a couple Minecraft servers and Overseerr working. I got Worpress and MariaDB set up and working fine locally. Because port 8080 was already in use, I set the Wordpress container to port 8089. I can open the Wordpress demo site up locally at 192.168.1.1:8089, but when I try to access it from the outside, page.mydomain.xyz:8089, I get an error message that the page is taking too long to respond. It somehow also seemed to kill my Overseerr interface. Now, when I try to go to overseerr.mydomain.xyz (port 5055), it times out and gives the same error for page taking too long to respond, and then shows the url as overseerr.mydomain.xyz:8089. I don't even have Overseerr set to that port. Alternatively, if I go to a previous url for Overseerr users page, overseerr.mydomain.xyz/users, the page loads fine. Any guidance is very appreciated.

 

EDIT: I'll add this from the Wordpress log screen:

 

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.XX.XX.19. Set the 'ServerName' directive globally to suppress this message

 

Does this help?

Edited November 16, 20241 yr by vdprice77
adding more info

Hi, how would I go about setting the upload limit bigger the 2 MB? 

On 11/14/2024 at 6:20 PM, vdprice77 said:

I'm using Cloudflare tunnels on my Unraid server. I've successfully got a couple Minecraft servers and Overseerr working. I got Worpress and MariaDB set up and working fine locally. Because port 8080 was already in use, I set the Wordpress container to port 8089. I can open the Wordpress demo site up locally at 192.168.1.1:8089, but when I try to access it from the outside, page.mydomain.xyz:8089, I get an error message that the page is taking too long to respond. It somehow also seemed to kill my Overseerr interface. Now, when I try to go to overseerr.mydomain.xyz (port 5055), it times out and gives the same error for page taking too long to respond, and then shows the url as overseerr.mydomain.xyz:8089. I don't even have Overseerr set to that port. Alternatively, if I go to a previous url for Overseerr users page, overseerr.mydomain.xyz/users, the page loads fine. Any guidance is very appreciated.

 

EDIT: I'll add this from the Wordpress log screen:

 

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.XX.XX.19. Set the 'ServerName' directive globally to suppress this message

 

Does this help?

I am facing a similar problem, did you find a solution?

On 3/17/2025 at 10:33 PM, SadRobot11 said:

I am facing a similar problem, did you find a solution?

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

On 5/9/2023 at 9:14 AM, Tolete said:

THE FIX:

Adding the following lines to the "wp-config.php" file in the WordPress installation directory:

 

define('FS_METHOD', 'direct');
define('FS_CHMOD_DIR', 0777);
define('FS_CHMOD_FILE', 0777);

This will force WordPress to use the "direct" method for updating plugins and themes, and set the directory and file permissions to 0777, which allows all users to read, write, and execute the files and directories.

 

After adding code to my wp-config.php and re-testing solved my issue.

This worked for me, however I also had to manually chmod -r 777 wp-content. i changed the other folder permissions back to 755, 644 and 640 per WP recommendations.

Having a pretty basic problem, i think its actually a word press problem but i can't figure out whats doing it.

I have port forwarding setup on my router for 443 -> NPM

NPM i have a proxy host setup to take traffic in from a wildcard DNS entry and forward it onto my wordpress BridgedIP:8083

Whenever i try to access via my DNS entry its forwarding to XXX.Domain.com:8083 which obviously is not going to work because i dont have 8083 exposed on my router.

I have 2 other external services running in the same manner and they do not exhibit this behaviour.

I tried updating wordpress site url to use my XXX.Domain.com url but when i did that my entire application became unreachable and i had to revert by manually editing the config files.

Anyone know what might be doing this?

2 hours ago, Aarex said:

Having a pretty basic problem, i think its actually a word press problem but i can't figure out whats doing it.

I have port forwarding setup on my router for 443 -> NPM

NPM i have a proxy host setup to take traffic in from a wildcard DNS entry and forward it onto my wordpress BridgedIP:8083

Whenever i try to access via my DNS entry its forwarding to XXX.Domain.com:8083 which obviously is not going to work because i dont have 8083 exposed on my router.

I have 2 other external services running in the same manner and they do not exhibit this behaviour.

I tried updating wordpress site url to use my XXX.Domain.com url but when i did that my entire application became unreachable and i had to revert by manually editing the config files.

Anyone know what might be doing this?

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

8 minutes ago, Kru-x said:

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

Sounds like exactly what i did........Unfortunately i had already built the entire site

I deleted wordpress and dropped my database started from scratch does seem to work...ooph

10 minutes ago, Aarex said:

Sounds like exactly what i did........Unfortunately i had already built the entire site

I deleted wordpress and dropped my database started from scratch does seem to work...ooph

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

This might be a stupid Q :-)

But when I do open WebUI from the docker it always opens the Unraid UI.
I have changed toe default port from 8080 to 8180

And I also tride to change the WebUI in the docker to http://[IP]:8180
But it always go to the Unraid UI any way around this?
I have multiple Wordpress dockers and I would like not to remember all the different ports LOL

Also no matter what I try I cant downgrade this image to a older version?
wordpress:5.9.1 does not work

14 minutes ago, casperse said:

Also no matter what I try I cant downgrade this image to a older version?
wordpress:5.9.1 does not work

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

8 hours ago, Kru-x said:

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

No I am trying to do a new fresh install, I need to move my hosted sites back to my Unraid server (Migration is tuff).
But I need to start up with a older version and then maybe build a new one later.
For that I wanted to pull down a older version.

But no matter what I write after wordpress in the docker repository it always fetches the newest version.
wordpress:5.9.1

No effect?
I get that maybee its so old that for security reasons they just drop it?

Open webUI internally problem:
Yes maybee its a DB issue with the open web UI (Its after a restore, so it might overwrite it

I have successfully restored my dockers to unraid BUT
I wanted to copy them to my Unraid backup server.

Same ports and username and DB names.

But I keep getting the wordpress:

Error establishing a database connection

What have I forgot to do?

15 hours ago, casperse said:

I have successfully restored my dockers to unraid BUT
I wanted to copy them to my Unraid backup server.

Same ports and username and DB names.

But I keep getting the wordpress:

Error establishing a database connection

What have I forgot to do?

Seemed I wasnt really missing anything.
I did have to go and manually point to the appdata folder (Sma eone) and save the conf again.
Also the same for each of the MariaDB's and after a reboot it worked!

Hi Kru-x,

Thanks for the docker! I was wondering if it could be updated with a newer php version? Having at least 8.3 would be nice.

I am quite new to all this, so not sure whether I should know of a way to do that myself?

Thanks in advance!

4 hours ago, fipships said:

Hi Kru-x,

Thanks for the docker! I was wondering if it could be updated with a newer php version? Having at least 8.3 would be nice.

I am quite new to all this, so not sure whether I should know of a way to do that myself?

Thanks in advance!

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

On 8/24/2025 at 10:23 PM, Kru-x said:

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

Many thanks for this! This worked.

On 11/15/2024 at 3:20 AM, vdprice77 said:

I'm using Cloudflare tunnels on my Unraid server. I've successfully got a couple Minecraft servers and Overseerr working. I got Worpress and MariaDB set up and working fine locally. Because port 8080 was already in use, I set the Wordpress container to port 8089. I can open the Wordpress demo site up locally at 192.168.1.1:8089, but when I try to access it from the outside, page.mydomain.xyz:8089, I get an error message that the page is taking too long to respond. It somehow also seemed to kill my Overseerr interface. Now, when I try to go to overseerr.mydomain.xyz (port 5055), it times out and gives the same error for page taking too long to respond, and then shows the url as overseerr.mydomain.xyz:8089. I don't even have Overseerr set to that port. Alternatively, if I go to a previous url for Overseerr users page, overseerr.mydomain.xyz/users, the page loads fine. Any guidance is very appreciated.

 

EDIT: I'll add this from the Wordpress log screen:

 

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.XX.XX.19. Set the 'ServerName' directive globally to suppress this message

 

Does this help?

I got the same issue. I haven't changed anything. It had been working fine for years.

I'm assuming an update has caused this.

How did you end up fixing this?

EDIT: I have checked wp_options in the linked MariaDB database and it has the correct URL.

Edited May 15May 15 by bobalot

I have cloudflare forward to Nginx Proxy Manager which then points to Wordpress.

I have had no issues for years and then it stopped connecting and times out.

I checked the logs and keep getting errors about the ServerName which I'm assuming is the problem.

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.14. Set the 'ServerName' directive globally to suppress this message

I have checked the domain name in wp_options in the MariaDB database. It is the correct domain.

I cannot work out how to fix this.

Does anybody have any ideas?

Edited May 17May 17 by bobalot