diff --git a/docs/DEBUG_GRAPHQL.md b/docs/DEBUG_GRAPHQL.md
new file mode 100755
index 00000000..c6d90c38
--- /dev/null
+++ b/docs/DEBUG_GRAPHQL.md
@@ -0,0 +1,64 @@
+# Debugging GraphQL server issues
+
+The GraphQL server is an API middle layer, running on it's own port specified by `GRAPHQL_PORT`, to retrieve and show the data in the UI. It can also be used to retrieve data for custom third party integarions. Check the [API documentation](./API.md) for details. 
+
+The most common issue is that the GraphQL server doesn't start properly, usually due to a **port conflict**. If you are running multiple NetAlertX instances, make sure to use **unique ports** by changing the `GRAPHQL_PORT` setting. The default is `20212`.
+
+## How to update the `GRAPHQL_PORT` in case of issues
+
+As a first troubleshooting step try changing the default `GRAPHQL_PORT` setting. Please remember NetAlertX is running on the host so any application uising the same port will cause issues.  
+
+### Updating the setting via the Settings UI
+
+Ideally use the Settings UI to update the setting under General -> Core -> GraphQL port:
+
+![GrapQL settings](./img/DEBUG_GRAPHQL/graphql_settings_port_token.png)
+
+You might need to temporarily stop other applications or NetAlertX instances causing conflicts to update the setting. The `API_TOKEN` is used to authenticate any API calls, including GraphQL requests. 
+
+### Updating the `app.conf` file
+
+If the UI is not accessible, you can directly edit the `app.conf` file in your `/config` folder:
+
+![Editing app.conf](./img/DEBUG_GRAPHQL/app_conf_graphql_port.png)
+
+### Using a docker variable
+
+All application settings can also be initialized via the `APP_CONF_OVERRIDE` docker env variable. 
+
+```yaml
+...
+ environment:
+      - TZ=Europe/Berlin      
+      - PORT=20213
+      - APP_CONF_OVERRIDE={"GRAPHQL_PORT":"20214"}
+...
+```
+
+## How to check the GraphQL server is running?
+
+There are several ways to check if the GraphQL server is running.
+
+### Init Check
+
+You can navigate to Maintenance -> Init Check to see if `isGraphQLServerRunning` is ticked:
+
+![Init Check](./img/DEBUG_GRAPHQL/Init_check.png)
+
+### Checking the Logs
+
+You can navigate to Maintenance -> Logs and search for `graphql` to see if it started correctly and serving requests:
+
+![GraphQL Logs](./img/DEBUG_GRAPHQL/graphql_running_logs.png)
+
+### Inspecting the Browser console
+
+In your browser open the dev console (usually F12) and navigate to the Network tab where you can filter GraphQL requests (e.g., reload the Devices page).
+
+![Browser Network Tab](./img/DEBUG_GRAPHQL/network_graphql.png)
+
+You can then inspect any of the POST requests by opening them in a new tab.
+
+![Browser GraphQL Json](./img/DEBUG_GRAPHQL/dev_console_graphql_json.png)
+
+
diff --git a/docs/PERFORMANCE.md b/docs/PERFORMANCE.md
index 00a1d5f0..13dac538 100755
--- a/docs/PERFORMANCE.md
+++ b/docs/PERFORMANCE.md
@@ -85,8 +85,8 @@ services:
       # (Optional) Useful for debugging setup issues
       - local/path/logs:/app/log
       # (API: OPTION 1) Store temporary files in memory (recommended for performance)
-      - type: tmpfs              # ◀ 
-        target: /app/api         # ◀ 
+      - type: tmpfs              # ◀ 🔺
+        target: /app/api         # ◀ 🔺
       # (API: OPTION 2) Store API data on disk (useful for debugging)
       # - local/path/api:/app/api
     environment:
diff --git a/docs/img/DEBUG_GRAPHQL/Init_check.png b/docs/img/DEBUG_GRAPHQL/Init_check.png
new file mode 100755
index 00000000..92d9d562
Binary files /dev/null and b/docs/img/DEBUG_GRAPHQL/Init_check.png differ
diff --git a/docs/img/DEBUG_GRAPHQL/app_conf_graphql_port.png b/docs/img/DEBUG_GRAPHQL/app_conf_graphql_port.png
new file mode 100755
index 00000000..8dff5e2e
Binary files /dev/null and b/docs/img/DEBUG_GRAPHQL/app_conf_graphql_port.png differ
diff --git a/docs/img/DEBUG_GRAPHQL/dev_console_graphql_json.png b/docs/img/DEBUG_GRAPHQL/dev_console_graphql_json.png
new file mode 100755
index 00000000..c26b5be6
Binary files /dev/null and b/docs/img/DEBUG_GRAPHQL/dev_console_graphql_json.png differ
diff --git a/docs/img/DEBUG_GRAPHQL/graphql_running_logs.png b/docs/img/DEBUG_GRAPHQL/graphql_running_logs.png
new file mode 100755
index 00000000..45a6125a
Binary files /dev/null and b/docs/img/DEBUG_GRAPHQL/graphql_running_logs.png differ
diff --git a/docs/img/DEBUG_GRAPHQL/graphql_settings_port_token.png b/docs/img/DEBUG_GRAPHQL/graphql_settings_port_token.png
new file mode 100755
index 00000000..e9253304
Binary files /dev/null and b/docs/img/DEBUG_GRAPHQL/graphql_settings_port_token.png differ
diff --git a/docs/img/DEBUG_GRAPHQL/network_graphql.png b/docs/img/DEBUG_GRAPHQL/network_graphql.png
new file mode 100755
index 00000000..71a96538
Binary files /dev/null and b/docs/img/DEBUG_GRAPHQL/network_graphql.png differ
diff --git a/front/php/templates/language/it_it.json b/front/php/templates/language/it_it.json
old mode 100644
new mode 100755
diff --git a/mkdocs.yml b/mkdocs.yml
index 6efe6ed3..d1b4bc02 100755
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -61,6 +61,7 @@ nav:
   - Troubleshooting:
       - Inspecting Logs: LOGGING.md
       - Debugging Tips: DEBUG_TIPS.md
+      - Debugging GraphQL: DEBUG_GRAPHQL.md
       - Debugging Invalid JSON: DEBUG_INVALID_JSON.md
       - Debugging Plugins: DEBUG_PLUGINS.md
       - Debugging Web UI Port: WEB_UI_PORT_DEBUG.md