WP persists on using wrong port

  • After moving WP from local installation (which used port 8081) to live domain (which obviously uses port 80) it still redirects to example.com:8081 instead of simply opening example.com.
    WTH? Can somebody tell how to get this running. I already applied the necessary changes to wp_options table (Base and Home), also tried to hardcode it into the wp-config file. Both did not change anything. Is there a cache file or something which still uses the old port number?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter tobik999

    (@tobik999)

    backend works properly, but wth does the frontend stil redirect to the wrong port?

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    After moving WP from local installation

    How did you perform the move? You may need to do a search and replace in your database and modify all example.com:8081 references to just example.com (less the 8081).

    See this Codex article for what I mean.

    https://codex.www.ads-software.com/Moving_WordPress#Moving_to_a_New_Server

    Thread Starter tobik999

    (@tobik999)

    UI what a pain, I have to change all the guid manually. I really do not understand why WP needs the whole path as unique identfier.

    Thread Starter tobik999

    (@tobik999)

    I changed also all the db entries from example.com:8081 to example.com using the search and replace script, but it is still redirecting to the old port# :S

    Is your base URL inside your settings setup to use the port as well?

    Under Settings->General, make sure your WordPress Address and site address do not use the custom port.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WP persists on using wrong port’ is closed to new replies.