Port added to URL by wordpress – not just the usual problem

  • crousti

    (@crousti)


    10 years, 9 months ago

    Hi,
    i have searched, and found various answers related to this. Some helped, some confused me … anyway here is my problem.

    I am trying to make a self hosting system, based on dockstar hardware (armv5 128MB ram).

    I installed the latest arch linux, nginx, php-fpm, mysql (mariadb) and finally wordpress, all that today.

    My nginx server listens on port 1080. It has IP 192.168.1.77.

    WordPress is installed in /blog.

    I am behind an ISP box, which does NAT. It redirects its port 80 to this dockstar port 1080. I also installed phpmyadmin which can only be accessed locally on another port.

    If i set home and wordpress URL to http://192.168.1.77:1080/blog, i can access it from my local network only. Any attempt from the external ip adds the port number to the URL, and that does not work. My error log is empty, and that added port only happens on wordpress pages, not on some test pages i did set at the root, so i think it is not added by nginx.

    If i set the wordpress url to http://externalip/blog , it does not work either. Yet i CAN access http://externalip/blog/wp-admin , as it somehow redirects me to the local IP address, but thats it ; i then have to edit the database to reset URL site to the local server ip.

    Any hint on this ? I really dont know what to do now. I need both access. I hope you can help. Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Pothi Kalimuthu

    (@pothi)

    10 years, 9 months ago

    You may set port_in_redirect to off, to get rid of port number after the URL.

    Thread Starter crousti

    (@crousti)

    10 years, 9 months ago

    I tried that at first, when i thought it was nginx. But it is not nginx, as http://externalip/ and http://externalip/info.php work perfectly; it only happens when i try to access a wordpress page.

    I tried again to add that line to the nginx .conf file and it did nothing, i still get that “:1080” added to the url, and then the browser fails to load the page with a timeout error (the same error i would get when trying to reach a page that does not exist).

    That and the nginx log does not show any error at all. It really is a wordpress problem.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Port added to URL by wordpress – not just the usual problem’ is closed to new replies.

Tags