• Hi,

    I have an internal website, which I want to migrating to another host, running docker, but struggling to setup basic SSL.

    In order to strip back things to the basics, I have deployed a brand new WordPress instance running on docker. My docker compose has the following port mappings

    8080:80
    8443:443

    With the docker container running, I browse to https://192.168.100.100:8080, then go through the initial WordPress setup (language, create user/pass). I then go to the Settings > General, but if I try to change the URLS from the above to https://192.168.100.100:8443, and save the changes, then I cannot access the site at this address. I get Chrome error “ERR_CONNECTION_REFUSED”. I have tried incognito, clearing cache etc.

    My only way to recover is to stop the container and wipe the DB and files volumes, then setup again from scratch.

    When in this state, my wp-config.php does not contain definitions for WP_HOME or WP_SITEURL. I feel something is not working properly when I save my changes to these URL’s in the GUI.

    Any help is greatly appreciated.

Viewing 2 replies - 1 through 2 (of 2 total)
  • but if I try to change the URLS from the above to https://192.168.100.100:8443, and save the changes, then I cannot access the site at this address. I get Chrome error “ERR_CONNECTION_REFUSED”.

    Are you able to get a STATIC file (text, HTML or image) placed at the root of your WordPress installation to load with this address?

    Eg if you place a static HTML file test.html file in the root of the WordPress installation, can you view it from https://192.168.100.100:8443/test.html

    When in this state, my wp-config.php does not contain definitions for WP_HOME or WP_SITEURL. I feel something is not working properly when I save my changes to these URL’s in the GUI.

    When you change these constants in the WordPress dashboard, they’re only saved to the database: they’re not written to the wp-config.php file.

    In fact, if you manually stick the constants in wp-config.php, this locks up these fields ins the dashboard, making them unchangeable (from the dashboard).

    Thread Starter ddit

    (@ddit)

    Hi George. Thanks for the reply. When I create a test.html page at put at the root level of the site, this does not load either. I also noticed WordPress has it’s own readme.html file at the root level, which doesn’t load either.

    I used a portscanner to check both ports above. 8080 is open and the port scanner identifies this as Apache. Oddly, 8443, is closed/unresponsive, so I need to go back to my docker container and troubleshoot that next, but this seems the likely issue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[docker/wordpress] changing to https…site is unavailable’ is closed to new replies.