You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keycloak is accessed via two routes: host.docker.internal (from the backend) and localhost (from the frontend). To ensure consistent access, an additional hostname is introduced that works for both.
5
+
### Resolve local naming
6
6
7
-
Add the following entry to your /etc/hosts file to resolve keycloak.internal to your local machine:
7
+
Sometimes Keycloak is accessed via multiple routes. For example `host.docker.internal` (from a backend) and `localhost` (from a frontend). To ensure consistent access, an additional hostname is introduced that works for both.
8
+
9
+
Add the following entry to your `/etc/hosts` file to resolve `keycloak.internal` to your local machine:
8
10
9
11
```sh
10
12
echo -e '127.0.0.1\tkeycloak.internal'| sudo tee -a /etc/hosts
@@ -16,4 +18,4 @@ Verify the setup by running:
16
18
ping keycloak.internal
17
19
```
18
20
19
-
This resolves keycloak.internal to 127.0.0.1 for both backend and frontend access.
21
+
This resolves `keycloak.internal` to `127.0.0.1` for both backend and frontend access.
0 commit comments