Title: ddit's Replies | WordPress.org

---

# ddit

  [  ](https://wordpress.org/support/users/ddit/)

 *   [Profile](https://wordpress.org/support/users/ddit/)
 *   [Topics Started](https://wordpress.org/support/users/ddit/topics/)
 *   [Replies Created](https://wordpress.org/support/users/ddit/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/ddit/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/ddit/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/ddit/engagements/)
 *   [Favorites](https://wordpress.org/support/users/ddit/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [[docker/wordpress] changing to https…site is unavailable](https://wordpress.org/support/topic/docker-wordpress-changing-to-https-site-is-unavailable/)
 *  Thread Starter [ddit](https://wordpress.org/support/users/ddit/)
 * (@ddit)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/docker-wordpress-changing-to-https-site-is-unavailable/#post-16853850)
 * 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 1 replies (of 1 total)