After re-installing portainer all my docker containers are not there

You have to edit the ports:

you're portforwarding 3x port 80 to different ports on the same IP: (some analogy to the Immortals="""THERE CAN BE ONLY ONE""")

same goes for port 443.

Remove/delete the last 3 entries. snce that will conflict with the one's above.

For eg.: SWAG receives a call from external on port 80 (for cert approval) and the router must forward it to port 81 (port where SWAG is listening on IP 192.168.0.23)

But the router also has forwards from 80 external to internal ports (2 in your setting), It will clash.

You can only have TCP Ext:80 to Int:81 (for SWAG) and TCP Ext:443 to Int:450 (also SWAG and according to what you have --^^^)

Post your docker-compose.yml here in full (hide sensible data) and I'm sure we can edit it to use bitwarden with either subdomain or subfolder.

Nice to see at least some is sorted,

Please, edit/hide/mask your SUBDOMAIN and your email on the post above

I've found this: bitwarden website but it's only available for x64 (NOT arm as the RPi) so the only one that runs on arm7vl+ (armhf) that I'm aware of is located here on github and is referenced here on this site.

If this is what you want, then we can create a compose for it and run it along side SWAG.

Acording to this source:

docker run \
-p 8005:80 \
-v bitwarden:/config \
--name bitwarden \
--restart always \
bitwardenrs/server:latest

Would become a "docker-compose" to integrate to an existing docker-compose.yml:

bitwarden:
 image: bitwardenrs/server:latest # raspberry
  container_name: bitwarden
    volumes:
      - /srv/dev-disk-by-label-DATA/appdata/bitwarden:/config # <<<--- This has to be adjusted!!!
    ports:
      - 8005:80
    restart: unless-stopped

Or as a stand alone service, would be like this:

version: "2.1"
 services:
  bitwarden:
   image: bitwardenrs/server:latest # raspberry
    container_name: bitwarden
     volumes:
      - /srv/dev-disk-by-label-DATA/appdata/bitwarden:/config
     ports:
      - 8005:80
     restart: unless-stopped

EDIT#2 Idents corrected and everything is running as it should, Good to go,

EDIT NOTE: For some reason, my docker-compose is spitting errors after I added the bitwarden part. Not parsing (prolly ident errors)

Working on it so don't do this just yet.

But I managed to run bitwarden straight via CLI with the docker command (just copy/paste in the terminal, it will start and show on portainer but only access via LAN).

First things first, I don't run neither root nor sudo since my user as "docker" privileges.

You have to do as you did the previous round of the stack. (either on root or with sudo and an unprivileged user)

You need to create a SUBDOMAIN for bitwarden on the duckdns.org (for instance: vandoebitwarden)

Go to duckdns.org and register what you want/need and use it for the rest of the instructions.

Edit you docker-compose.yml with:

Zitat von vandoe

- DNSPLUGIN=duckdns
- URL=duckdns.org
- DUCKDNSTOKEN=my token
- SUBDOMAINS=theonesyoualreadyhave,vandoebitwarden # <<-- there's a comma and then name without any spaces

Now, let's assume that you have your docker-compose.yml in "/home/pi/" folder).

cd /home/pi/ to go to the folder and then ls and confirm that the "docker-compose.yml" is there.

VERY-IMPORTANT: DO NOT SKIP THIS

Make a copy of the "docker-compose.yml" in case something goes wrong. That way you're safe:

cp docker-compose.yml docker-compose.yml.NO.BITWARDEN

BACKUP DONE: YES. Ok continue.

nano docker-compose.yml and add the sample above --^^^^ for existing stack (adding to what you posted above:

[LAN_ACCESS]

version: "2"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud:latest
    container_name: nextcloud
    environment:
      - PUID=1000
      - PGID=100
      - TZ=America/New_York
    volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/nextcloud/:/config
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Primary/AppData/Nextcloud/:/data
    depends_on:
      - nextclouddb
    ports:
      - 450:443
    restart: unless-stopped
  nextclouddb:
    image: ghcr.io/linuxserver/mariadb:latest
    container_name: nextclouddb
    environment:
      - PUID=1000
      - PGID=100
      - MYSQL_ROOT_PASSWORD=dbpassword
    volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/nextclouddb/:/config
    restart: unless-stopped
  swag:
     image: linuxserver/swag
     container_name: swag
     cap_add:
      - NET_ADMIN
     environment:
      - PUID=1000
      - PGID=100
      - TZ=America/New_York
      - DNSPLUGIN=duckdns
      - URL=duckdns.org
      - DUCKDNSTOKEN=my token
      - SUBDOMAINS=
      - ONLY_SUBDOMAINS=true
      - VALIDATION=http
      - EMAIL=
     volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/swag/:/config
     ports:
      - 444:443
      - 81:80
     restart: unless-stopped
  bitwarden:
     image: bitwardenrs/server:latest # raspberry
     container_name: bitwarden
     volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/bitwarden/:/config
     ports:
      - 8005:80
     restart: unless-stopped

Now you can go to Portainer--> Containers and "bitwarden" should be there running.

Open it's logs and see if there's any errors (I never used it so don't really know what it should say).

At this time, your bitwarden should open on the browser with "http://RaspberryIP:8005".

[/LAN_ACCESS]

[WAN_ACCESS]

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

    server_name bitwarden.*; # <<-- replace "bitwarden.*" with "vandoebitwarden.*" <<< Remember the domain registered in duckdns?!?

And now, you should be able to go to "https://vandoebitwarden.duckdns.org" and profit,

[/WAN_ACCESS]

Zitat von vandoe

current swag is mapping 81:80

and the bitwarden you proposed is mapping 8005:80

Swag is using port 81 on the host while bitwarden will use 8005,

Ports on the right are for the containers themselfs.

Please read carefully my previous post, I'm still trying to clean the docker-compose.yml due to errors on some idents, It's not parsing properly.