Tag: DNS

Finally? My blog site is starting to behave itself again!

Loading

I have been wondering whether my blog site issue posts should have had different subject lines:

  • “The Day after Tomorrow”
  • “Pride and Prejudice”
  • “The Abyss”
  • “The Temple of Doom”
  • and the final one: “The Great Escape”

I have fixed numerous problem along the way, all with no prior experience with Docker, but the main ones have been:

  • Obtaining a static IP address from my ISP.
  • Conversion of my server functions into separate Docker containers.
  • Building a user-specific Docker image with Apache2 and Perl for the “other” folders outside of WordPress.
  • Adding DNS server addresses to Docker.
  • Removing access restrictions to the /tmp areas of the databases.

I think I can say with more confidence that my blog site is becoming robust enough to be able to support my retirement next week! Yes, by the start of April 2025 I will have officially retired, but this site will still be up-and-running!

My blog is back, but all of your saved links will need to be updated…

Loading

On 13Feb2025 my broadband was upgraded, which set in motion a chain of events that I have only this weekend managed to control. As a result, where before you used https://hollandnumerics.org.uk/wordpress to access this site, you should now use just https://hollandnumerics.org.uk. Which means that the link to my last “hopeful” post is now here: Have you missed me? I think my blog site is back. Let me explain…

While in February I thought my blog site was back online, it was unbelievably slow, so I started searching for a reason:

  • I checked the firewalls in the new docker containers, Linux server and router, but nothing I changed had any positive impact.
  • I asked for help from the WordPress and Jetpack community, but nothing improved my situation.
  • Finally, after scouring through the various logs on my Linux server, I found a reference to incorrect DNS (Domain Name Server) addresses. Correcting them in /etc/network/interfaces to match my router resolved all of the problems connecting to WordPress and Jetpack servers, and, suddenly, my blog site sprang into life again.

My problems are still not completely over, as I have a collection of non-WordPress web pages that will not happily co-exist with my blog site, so I am asking the StackOverFlow community for assistance (I have 2 docker containers: WordPress exposing port 443, and ownCloud exposing port 8080. Can I add a Perl/httpd container to run exposing port 80?). If you can help, then please post a suggestion there.

Thanks in advance………….Phil

PS. You can also comment on my Docker query at https://forums.docker.com/t/unable-to-start-httpd-latest-image-httpd-foreground-cannot-find-httpd/147124/2.