Letencrypt or docker issues

I was able to set up Nextcloud with spaceinvador video. but it seems like Nextcloud is hijacking all other docker Https. 

what i mean is when I set up my Bitwarden and use my https://bitwarden.mydomain.com it will direct me to nextcloud UI.

I can't set up anything else that work with reverse proxy other then Nextcloud. I tried also to follow Spaceinvador for "onlyofficedocumentserver" video and it doen't work. I am trying to figure out where the problem is.

this is from a different thread where i have my set up for Bitwarden. I don't where is the issue;

I used first dock DNS as my domain, it didn't work so i decided to have my own domain to try and see if bitwarden would work. i will write all the steps and please let me know if i am missing something.

first, I know that Letenrypt is set up right with my domain name and subdomains, the log connected to all my  subdomains: Nextcloud, bitwarden. see image. made sure the Cnam is set right spelled right...

Second, my duckdns is set up right since my Nextcloud is working following Spaceenvador's Video

for Bitwarden, yes i set up the network to custom,  just like Nextcloud.

I tried 2 different config files in letencryp for bitwarden, one with spaceinvador file and i left the  container name as original with bitwardenrs

of course i alway restart my dockers.

#BITWARDEN
# make sure that your domain has dns has a cname or a record set for the subdomain bitwarden 
# This config file will work as is when using a custom docker network the same as letesencrypt (proxynet).
# However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve.  
# If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7

resolver 127.0.0.11 valid=30s;
upstream bitwarden {
    server bitwardenrs:80;
}

server {
    listen 443 ssl;
    server_name bitwarden.*;
    include /config/nginx/ssl.conf;
  client_max_body_size 128M;

  location / {
   proxy_pass http://bitwarden;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
  }
  
  location /notifications/hub {
   proxy_pass http://bitwarden;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
  }
  
  location /notifications/hub/negotiate {
    proxy_pass http://bitwarden;
  }
}

second i tried the original config in Letinrypt and chnage .sample to .conf and i change the container name to bitwarden. 

# make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url
# make sure your bitwarden container is named "bitwarden"

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name bitwarden.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 128M;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app bitwarden;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }

    location /notifications/hub {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app bitwarden;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
    }

    location /notifications/hub/negotiate {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app bitwarden;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }

}

now the weird part. when i use http://bitwarden.mydomain.com it will direct me to nextcloud i don't understand why?, when i stop nextcloud and try again i have error 502 Bad Gateway nginx/1.16.1

i am able only to connect locally with bitwarden i dont know what am i missing. this was the same using duckdns as domain