Docker Community Forums

Share and learn in the Docker community.

Some issue with a docker container and a domain in Nginx PM

Hi,
I have been struggling with this problem for quite a while.

I deployed a few containers which work well:

I also created 4 letsencrypt SSL certificates for 4 services of mine via my Nginx PM as you can see below:

Three of them work perfectly fine, and I can get access to them either via Internet or via my local LAN.
But I’m still struggling to make the first one (“blog”") work.

Docker is installed in a host of my LAN (192.168.3.93) and I set in docker compose 8005->80 as my blog host->container port. I can access it in my LAN via this IP in my browser 192.168.3.93:8005, but if I tried to access it via Internet or directly by clicking on its domain link in nginx PM I got:

**"connect failed firefox can establish a connection to the server blogxxxxxxxxxxx:8005.

I don’t know how to fix it. But I’d like also to understand what is the matter with it since the other ones work flawlessly.

For the record here is my worpress docker-compose yml file :

version: "3.3"

networks: 
  nginx_default: 
    external: 
      name: nginx_default
      
services:
   db:
     image: mysql:5.7
     container_name: wordpress_db
     volumes:
       - db_data:/var/lib/mysql
     networks:
           - nginx_default
     restart: always
     environment:
       MYSQL_ROOT_PASSWORD: xxxxxxxxx8x
       MYSQL_DATABASE: wordpress
       MYSQL_USER:xxxxe
       MYSQL_PASSWORD: xxxxxxx8
       

   wordpress:
     depends_on:
       - db
     image: wordpress:latest
     container_name: wordpress
     networks:
           - nginx_default
     ports:
       - "8005:80"
     restart: always
     environment:
       WORDPRESS_DB_HOST: wordpress_db:3306
       WORDPRESS_DB_USER: xxxxe
       WORDPRESS_DB_PASSWORD: xxxxxx8
       WORDPRESS_DB_NAME: wordpress
      
volumes:
    db_data: {}

Could you help me figure it out please?
Thanks

Could anyone give some advice on that, please?

I FIXED IT!!!
Some issue with its port.

I ran into this issue just today. I proceeded under the assumption that it was a bug.

While reviewing the docker logs I noticed it was looking for “npm-4” and “npm-5”, but it couldn’t find them. Eventually I came around to deleting the error SSL and remaking the proxy host, requesting the SSL again.