diff --git a/.env b/.env
index 52c6cb8f..04c4e722 100644
--- a/.env
+++ b/.env
@@ -1,12 +1,15 @@
 
 # Taiga's URLs - Variables to define where Taiga should be served
 TAIGA_SCHEME=http  # serve Taiga using "http" or "https" (secured) connection
-TAIGA_DOMAIN=localhost:9000  # Taiga's base URL
+# TAIGA_DOMAIN=localhost:9000  Taiga's base URL
+
+TAIGA_DOMAIN=10.136.55.126:9000 # New URL, fix applied
+
 SUBPATH="" # it'll be appended to the TAIGA_DOMAIN (use either "" or a "/subpath")
 WEBSOCKETS_SCHEME=ws  # events connection protocol (use either "ws" or "wss")
 
 # Taiga's Secret Key - Variable to provide cryptographic signing
-SECRET_KEY="taiga-secret-key"  # Please, change it to an unpredictable value!!
+SECRET_KEY="htaatmjVq_oR<wh!"  # Please, change it to an unpredictable value!!
 
 # Taiga's Database settings - Variables to create the Taiga database and connect to it
 POSTGRES_USER=taiga  # user to connect to PostgreSQL
diff --git a/README.md b/README.md
index 31e7465b..0f4faf51 100644
--- a/README.md
+++ b/README.md
@@ -528,3 +528,38 @@ server {
 ## Change between subpath and subdomain
 
 If you're changing Taiga configuration from default subdomain (https://taiga.mycompany.com) to subpath (http://mycompany.com/subpath) or vice versa, on top of adjusting the configuration as said above, you should consider changing the TAIGA_SECRET_KEY so the refresh works properly for the end user.
+
+## Accessing Taiga from Other Devices on the Local Network
+
+By default, Taiga may use:
+
+TAIGA_DOMAIN=localhost:9000
+
+This only works when accessing the service from the same machine.
+
+To allow access from other devices on the same network, update the
+`.env` configuration to use the host machine's local IPv4 address:
+
+TAIGA_DOMAIN=<your-local-ip>:9000
+
+Example:
+
+TAIGA_DOMAIN=192.168.1.25:9000
+
+After modifying the configuration, restart the containers:
+
+docker compose down
+./launch-taiga.sh
+
+## Public Registration and Secret Key Configuration
+
+### Enabling Public Registration
+
+By default, Taiga Docker deployments disable public user registration.
+To allow users to create accounts directly from the login page, add the
+following configuration to `docker-compose.yml`.
+
+In the backend shared environment:
+
+```yaml
+PUBLIC_REGISTER_ENABLED: "True"
\ No newline at end of file
diff --git a/docker-compose.yml b/docker-compose.yml
index 2f803fc4..7864d2fd 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -28,6 +28,7 @@ x-environment:
   # Telemetry settings
   ENABLE_TELEMETRY: "${ENABLE_TELEMETRY}"
   # ...your customizations go here
+  PUBLIC_REGISTER_ENABLED: "True"
 
 x-volumes:
   &default-back-volumes
@@ -103,6 +104,7 @@ services:
       TAIGA_WEBSOCKETS_URL: "${WEBSOCKETS_SCHEME}://${TAIGA_DOMAIN}"
       TAIGA_SUBPATH: "${SUBPATH}"
       # ...your customizations go here
+      PUBLIC_REGISTER_ENABLED: "true"
     networks:
       - taiga
     # volumes: