• Resolved fanglord

    (@fanglord)


    I have a website that I host on my main server (a Mac). I’ve got a Ubuntu server (lucid) running wordpress on a different machine on my site. My main server is NAT-routed port 80 -> port 80, as one would expect. I’ve got my wordpress server NAT-routed port 8888 -> port 80, the idea being I can point my browser from outside the firewall at https://www.example.com:8888/wordpress/ and reach my wordpress install.

    This does not happen. What happens is that the wordpress at port 8888 then redirects to the same folder, but to the server running on port 80. It took me a while to realize what was happening, because there was not wordpress/ directory on the Mac, and it was giving a 404 error. I created that directory, and stuck a simple index.html page in to redirect back to the Ubuntu server. Of course, I got a nice redirect loop going on.

    I’m guessing that the wordpress install doesn’t realize that to the outside world, it’s on port 8888, and some script tells it to return port 80, which sends the browser back to the Mac server. I don’t want to run wordpress on the Mac server. Is there any way to set it so that I can run wordpress on my Ubuntu server NAT routed on port 8888?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Wouldn’t you need to configure httpd on the ubuntu machine to listen on port 8888 instead of the defaults? It seems like you could reconfigure the default ( or add port ) to 8888, (What does /etc/apache2/ports.conf look like? ) or just configure a name based virtual host container for that site that listens on port 8888 – which probably still means adding port 8888 to the listen directives in the global Apache config. I’m just guessing, though.

    Thread Starter fanglord

    (@fanglord)

    I searched the forums more deeply, and found out that it’s because I didn’t set up wordpress originally with that port added. I followed the instructions here:

    Changing the Site URL

    and all is well!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘NAT-routed wordpress redirects to standard port’ is closed to new replies.