From 707a5a11cafe8438c00ba777196f544e2ac278a8 Mon Sep 17 00:00:00 2001
From: kurokobo <2920259+kurokobo@users.noreply.github.com>
Date: Sat, 12 Mar 2022 00:15:41 +0900
Subject: [PATCH] fix: add notes for password and accessible url

---
 README.md               | 6 ++++--
 tips/troubleshooting.md | 9 +++++----
 2 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index cb9a0e9..df5144b 100644
--- a/README.md
+++ b/README.md
@@ -139,7 +139,7 @@ spec:
 ...
 ```
 
-Modify two `password`s in `base/kustomization.yaml`.
+Modify two `password`s in `base/kustomization.yaml`. Note that some special charactors like `&`, `$`, etc. in `password` under `awx-postgres-configuration` might cause the deployment issue. Not tested all charactors, but `!` is safe to use at least.
 
 ```yaml
 ...
@@ -239,7 +239,9 @@ secret/awx-broadcast-websocket                       Opaque
 
 Now your AWX is available at `https://awx.example.com/` or the hostname you specified.
 
-At this point, however, AWX can be accessed via HTTP as well as HTTPS. If you want to redirect HTTP to HTTPS, see [📝Tips: Redirect HTTP to HTTPS](tips/https-redirection.md).
+Note that you have to access via hostname that you specified in `base/awx.yaml`, instead of IP address, since this guide uses Ingress. So you should configure your DNS or `hosts` file on your client where the brower is running.
+
+At this point, AWX can be accessed via HTTP as well as HTTPS. If you want to redirect HTTP to HTTPS, see [📝Tips: Redirect HTTP to HTTPS](tips/https-redirection.md).
 
 ## Back up and Restore AWX using AWX Operator
 
diff --git a/tips/troubleshooting.md b/tips/troubleshooting.md
index 0e5a27a..f92f900 100644
--- a/tips/troubleshooting.md
+++ b/tips/troubleshooting.md
@@ -228,10 +228,11 @@ This problem occurs when the AWX pod and the PostgreSQL pod cannot communicate p
 
 To solve this, check or try the following:
 
-- **Ensure your PostgreSQL (typically the Pod named `awx-postgres-0`)is in `Running` state.**
-- **Ensure your `firewalld`, `ufw` or any kind of firewall has been disabled on your K3s host.**
-- **Ensure your `awx-postgres-configuration` has correct values, especially if you're using external PostgreSQL.**
-- **Uninstall K3s and install it again.**
+- Ensure your PostgreSQL (typically the Pod named `awx-postgres-0`)is in `Running` state.
+- Ensure your `firewalld`, `ufw` or any kind of firewall has been disabled on your K3s host.
+- Ensure your `awx-postgres-configuration` has correct values, especially if you're using external PostgreSQL.
+- Ensure your `password` in `awx-postgres-configuration` does not contain any special charactors like '&', '$', etc..
+- Uninstall K3s and install it again.
 
 ### The Pod for PostgreSQL is in `CrashLoopBackOff` state and shows "Permission denied" log