starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #588] How-to access WordPress Docker with Custom Port #493

New issue

Closed

opened 2026-02-26 06:33:06 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 06:33:06 +03:00

Owner

Originally created by @redtripleAAA on GitHub (Aug 30, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/588

Checklist

Please read the setup instructions
Please read the FAQ

What is troubling you?
How-to access WordPress Docker with Custom Port

I have other basic project that can be accessed with their custom ports, except for Wordpress docker image

I have this setup

FYI,
As you can see, I can access the website locally

And admin dashboard

Please advise.

I can share the domain for testing as well.

Thank you.

Originally created by @redtripleAAA on GitHub (Aug 30, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/588 **Checklist** - Please read the [setup instructions](https://nginxproxymanager.com/setup/) - Please read the [FAQ](https://nginxproxymanager.com/faq/) **What is troubling you?** How-to access WordPress Docker with Custom Port I have other basic project that can be accessed with their custom ports, except for Wordpress docker image I have this setup ![image](https://user-images.githubusercontent.com/5244872/91653829-ff152000-ea71-11ea-9354-65a58451b5aa.png) FYI, As you can see, I can access the website locally ![image](https://user-images.githubusercontent.com/5244872/91653844-15bb7700-ea72-11ea-9aed-073fd8afe665.png) And admin dashboard ![image](https://user-images.githubusercontent.com/5244872/91653799-cd9c5480-ea71-11ea-8823-64e7b0152748.png) Please advise. I can share the domain for testing as well. Thank you.

kerem

2026-02-26 06:33:06 +03:00

closed this issue
added the
product-support
label

kerem commented

2026-02-26 06:33:07 +03:00

Author

Owner

@LivingWithHippos commented on GitHub (Aug 30, 2020):

Is that the ip address you use? It's a special address so maybe that's the problem.

If that is not the problem,

did you put the correct domain name (first screen)? If your domain is yourdomain.com you must put either that or a subdomain such as sub.anydomain.com
does your domain resolve to the correct IP? Try it from a command line with ping yourdomain.com

If you join the docker networks between the wordpress and the nginx containers you can follow the instruction in my other post

@LivingWithHippos commented on GitHub (Aug 30, 2020): Is that the ip address you use? It's a [special](https://www.speedguide.net/ip/10.0.12.16) address so maybe that's the problem. If that is not the problem, 1. did you put the correct domain name (first screen)? If your domain is yourdomain.com you must put either that or a subdomain such as sub.anydomain.com 2. does your domain resolve to the correct IP? Try it from a command line with ping yourdomain.com If you join the docker networks between the wordpress and the nginx containers you can follow the instruction in my other [post](https://github.com/jc21/nginx-proxy-manager/issues/555#issuecomment-677893307)

kerem commented

2026-02-26 06:33:07 +03:00

Author

Owner

@redtripleAAA commented on GitHub (Aug 30, 2020):

@LivingWithHippos I can confirm that the domain and its DNS is not the problem.

I have other sub-domains are working fine.

I can confirm that the subdomain in question can be resolved without issues ot the public IP address where I have my services hosted.

Checked with:
https://www.whatsmydns.net/

@redtripleAAA commented on GitHub (Aug 30, 2020): @LivingWithHippos I can confirm that the domain and its DNS is not the problem. I have other sub-domains are working fine. I can confirm that the subdomain in question can be resolved without issues ot the public IP address where I have my services hosted. Checked with: https://www.whatsmydns.net/

kerem commented

2026-02-26 06:33:07 +03:00

Author

Owner

@dash74 commented on GitHub (Sep 1, 2020):

I think I have figured out your issue. Did you setup wordpress using your internal ip? After you launch your wordpress docker image. You can go to your internal ip and make sure it works, but stop at the screen below. You should be able to access your site through the domain name and complete the setup process.

@dash74 commented on GitHub (Sep 1, 2020): I think I have figured out your issue. Did you setup wordpress using your internal ip? After you launch your wordpress docker image. You can go to your internal ip and make sure it works, but stop at the screen below. You should be able to access your site through the domain name and complete the setup process. ![image](https://user-images.githubusercontent.com/28696570/91876989-620ddf00-ec4b-11ea-80a1-8828bb5d372c.png)

kerem commented

2026-02-26 06:33:07 +03:00

Author

Owner

@redtripleAAA commented on GitHub (Sep 2, 2020):

@dash74

Thanks for testing on your end.

I can confirm that I had no issues in accessing the WordPress docker instance with the local IP address and I can access with NAT the external IP address + the port.

However, I noticed something, which I think it's related maybe to a bug in the system.

So, I managed to get it working by changing the sub-domain ... creating a new Wordpress Instance + Different Port + Creating New Sub-domain and then Proxy Manager, worked!

@redtripleAAA commented on GitHub (Sep 2, 2020): @dash74 Thanks for testing on your end. I can confirm that I had no issues in accessing the WordPress docker instance with the local IP address and I can access with NAT the external IP address + the port. However, I noticed something, which I think it's related maybe to a bug in the system. So, I managed to get it working by changing the sub-domain ... creating a new Wordpress Instance + Different Port + Creating New Sub-domain and then Proxy Manager, worked!

kerem commented

2026-02-26 06:33:07 +03:00

Author

Owner

@alejandrobalderas commented on GitHub (Feb 7, 2021):

I think I have figured out your issue. Did you setup wordpress using your internal ip? After you launch your wordpress docker image. You can go to your internal ip and make sure it works, but stop at the screen below. You should be able to access your site through the domain name and complete the setup process.

I had the exact same problem and this actually did the trick for me as well. It is important to configure wordpress from the url from which you are going to be accessing the website

@alejandrobalderas commented on GitHub (Feb 7, 2021): > I think I have figured out your issue. Did you setup wordpress using your internal ip? After you launch your wordpress docker image. You can go to your internal ip and make sure it works, but stop at the screen below. You should be able to access your site through the domain name and complete the setup process. > > ![image](https://user-images.githubusercontent.com/28696570/91876989-620ddf00-ec4b-11ea-80a1-8828bb5d372c.png) I had the exact same problem and this actually did the trick for me as well. It is important to configure wordpress from the url from which you are going to be accessing the website

kerem commented

2026-02-26 06:33:07 +03:00

Author

Owner

@redtripleAAA commented on GitHub (Feb 7, 2021):

I think I have figured out your issue. Did you setup wordpress using your internal ip? After you launch your wordpress docker image. You can go to your internal ip and make sure it works, but stop at the screen below. You should be able to access your site through the domain name and complete the setup process.

I had the exact same problem and this actually did the trick for me as well. It is important to configure wordpress from the url from which you are going to be accessing the website

I found the issue and managed to fix it.

Always run the initial setup for your wordpress instance using the public domain and not the internal domain/IP.

After that, everything should work fine.

Thanks for reminding me to share my fix here with everyone!

@redtripleAAA commented on GitHub (Feb 7, 2021): > > I think I have figured out your issue. Did you setup wordpress using your internal ip? After you launch your wordpress docker image. You can go to your internal ip and make sure it works, but stop at the screen below. You should be able to access your site through the domain name and complete the setup process. > > ![image](https://user-images.githubusercontent.com/28696570/91876989-620ddf00-ec4b-11ea-80a1-8828bb5d372c.png) > > I had the exact same problem and this actually did the trick for me as well. It is important to configure wordpress from the url from which you are going to be accessing the website I found the issue and managed to fix it. Always run the initial setup for your wordpress instance using the public domain and not the internal domain/IP. After that, everything should work fine. Thanks for reminding me to share my fix here with everyone!

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#493

No description provided.

Rows
Columns