WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #34143, comment 2


Ignore:
Timestamp:
10/04/2015 10:56:42 AM (4 years ago)
Author:
idrarig
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34143, comment 2

    initial v1  
    55To better explain my configuration, let's consider another scenario.  Suppose you have a machine (be it a container, VM, VPS, whatever...) accessible from a certain public IP 1.2.3.4, and then configure the DNS so that yourdomain points to 1.2.3.4.  You install WordPress on yourdomain and this goes smoothly.  But if the machine itself does not really have the public IP 1.2.3.4 but is on a private network 10.0.0.0, and routing/firewalling is not properly taken care of, the machine may not see itself as yourdomain.  This happened to me in production with a proprietary webapp, but the setup problem applies to any website.
    66
    7 During development, I have a port mapping localhost:5555 -> container:80 set up by docker. This way I installed WordPress on http://localhost:5555, but from within the container the request  to http://localhost:5555/wp-cron.php can not work.
     7During development, I have a port mapping localhost:5555 -> container:80 set up by docker. This way I installed WordPress on http://localhost:5555, but from within the container the request  to http://localhost:5555/wp-cron.php cannot work.
     8
     9(I didn't try the plugin you mentioned but according to the description, it wouldn't help with reporting these kinds of problems.)