Deployment to Cloud VM: Frontend and Backend access issue

[fanpeng-kong]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched in the documentation/README.
• I already searched in Google "How to do X" and didn't find any information.
• I already read and followed all the tutorial in the docs/README and didn't find an answer.

Commit to Help

• I commit to help with one of those options 👆

Example Code

NA

Description

Following the Deployment instructions, I have successfully deployed the stack (staging and production) into two of my Azure Virutal Machines running Ubuntu 22.04 server. I can see all the containers running normally all both VMs as below:

IMAGE             COMMAND                  CREATED        STATUS        PORTS                                                                      
backend:latest    "/start.sh"              10 hours ago   Up 10 hours   80/tcp                                                                     
adminer           "entrypoint.sh php -…"   10 hours ago   Up 10 hours   8080/tcp                                                                   
postgres:12       "docker-entrypoint.s…"   10 hours ago   Up 10 hours   5432/tcp                                                                   
frontend:latest   "/docker-entrypoint.…"   10 hours ago   Up 10 hours   80/tcp                                                                     
traefik:v2.3      "/entrypoint.sh --pr…"   10 hours ago   Up 10 hours   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp   

I can also access the Traefik Dashboard and Adminer interface, log in with the credentials that I set and examine the data there, e.g.: all the Routers, Services etc. seem to work properly:

However, when I was trying to access the Frontend and Backend (API Docs) through their subdomains urls.

For the staging environment, I run into below issues:

1. Potential security risk warning due to invalid security certificate
2. If I accept the risk and choose to continue, I reached at a 404 page not found error

For the production environment, I run into below error:

This site can’t be reachedCheck if there is a typo in my-domain-name.
DNS_PROBE_FINISHED_NXDOMAIN

My DNS records configuration look like below:

*.my-domain-name -> Staging VM IP
*.staging.my-domain-name -> Production VM IP

I understand that my issues may not be related to the code base itself but rather my configurations (DNS, VM or Deployment configuration). However, I appreciate if anyone who has gone through similar hurdles, or can spot any of my silly mistakes, could give me some hints on these issues.

Appreciate your help!

Operating System

Linux

Operating System Details

Ubuntu 22.04 Server on Azure

Python Version

3.10.12

Additional Context

No response

[fanpeng-kong]

The comment in under this issue gave me some hints. The complete DNS records (type A) should look like below:

my-domain-name -> Staging VM IP
*.my-domain-name -> Staging VM IP
staging.my-domain-name -> Production VM IP
*.staging.my-domain-name -> Production VM IP

Now I can access both backend and frontend services. However, I am still facing the Certificate is not valid for the Traefik default cert.

[fanpeng-kong]

okay, the certificate for backend/frontend services also became valid no so I guess it just takes some time for the certificates to become valid...