diff --git a/homelab/docker-compose.yml b/homelab/docker-compose.yml
index aeced73..d5c4729 100644
--- a/homelab/docker-compose.yml
+++ b/homelab/docker-compose.yml
@@ -13,11 +13,15 @@ services:
       - MARIADB_DISABLE_UPGRADE_BACKUP=1
     env_file:
       - ./env/nextcloud-db.env
+    networks:
+      - proxy-tier
 
   nextcloud-redis:
     image: redis:alpine
     container_name: nextcloud-redis
     restart: unless-stopped
+    networks:
+      - proxy-tier
 
   nextcloud-app:
     build: ./builds/nextcloud-app/
@@ -38,7 +42,6 @@ services:
       - nextcloud-redis
     networks:
       - proxy-tier
-      - default
 
   nextcloud-cron:
     image: nextcloud:apache
diff --git a/homelab/setup.org b/homelab/setup.org
index 0c7c452..f596bf9 100644
--- a/homelab/setup.org
+++ b/homelab/setup.org
@@ -3,6 +3,12 @@
 
 This walks you through setup of this homelab docker-compose template into a working production environment.
 
+** Docker Networking
+By default, only docker-compose containers within the same file are able to talk to each other. This can be bypassed by creating an "external" network. In this sample, the external network is called "proxy-tier" and must be created manually with the command:
+#+BEGIN_SRC sh :noexec
+sudo docker network create proxy-tier
+#+END_SRC
+
 ** Domain Name
 In order for this to work, you're going to need a domain name. Do a search for the best domain name registrars and pick one. Then search up domain names you would like until you find something available. Then, as long as you aren't trying to get something fancy like .gg or .ai, the yearly payments shouldn't be too bad.
 
diff --git a/network/pi-hole-setup.org b/network/pi-hole-setup.org
index db2fa6a..b7e8191 100644
--- a/network/pi-hole-setup.org
+++ b/network/pi-hole-setup.org
@@ -3,6 +3,12 @@
 
 This walks you through setup of Pi-hole on your home network, which can block ads (or any domain for that matter) /and/ act as a local DNS server you can control.
 
+** Docker Networking
+By default, only docker-compose containers within the same file are able to talk to each other. This can be bypassed by creating an "external" network. In this sample, the external network is called "proxy-tier" and must be created manually with the command:
+#+BEGIN_SRC sh :noexec
+sudo docker network create proxy-tier
+#+END_SRC
+
 ** Firewall Rules
 In order to make sure everything works, the both the server's firewall and your router's firewall must be configured to allow access to the ports we need. Port 8093 will be the Web GUI for administration, and port 53 since that is the standard port for DNS servers.
 
diff --git a/network/wireguard-setup.org b/network/wireguard-setup.org
index 22a567b..7dd0b47 100644
--- a/network/wireguard-setup.org
+++ b/network/wireguard-setup.org
@@ -1,6 +1,12 @@
 #+title: Wireguard Setup
 #+author: Emmet
 
+** Docker Networking
+By default, only docker-compose containers within the same file are able to talk to each other. This can be bypassed by creating an "external" network. In this sample, the external network is called "proxy-tier" and must be created manually with the command:
+#+BEGIN_SRC sh :noexec
+sudo docker network create proxy-tier
+#+END_SRC
+
 ** Firewall Rules
 In order to make sure everything works, the both the server's firewall and your router's firewall must be configured to allow access to the ports we need. Port 52180 is the only port needed for Wireguard.