From 556e823927274cc579637da1a20f076835c75992 Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Tue, 17 Feb 2026 14:39:25 +0800
Subject: [PATCH] Updated FAQ (markdown)
---
FAQ.md | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/FAQ.md b/FAQ.md
index 8568960..34871d7 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -637,6 +637,55 @@ Here is a good example, https://github.com/rustdesk/rustdesk/discussions/8999
If you set `21114` as the `https` port, please check https://github.com/rustdesk/rustdesk/discussions/10922#discussioncomment-12336832
+# An issue with custom logos
+
+User: Under Customer Clients, even clients created before mid-January the logos are no longer displayed.
+
+
+
+RustDesk: Check Network response in Chrome DevTools
+
+Because even previously created custom clients no longer display their icon/logo, we need to verify whether the data is still returned by the backend.
+
+Please do the following:
+
+- Open the Web Console in Google Chrome
+- Press F12 to open Developer Tools
+- Go to the Network tab
+- Then open one of the affected Custom Clients
+- Click the corresponding request in the Network list
+- Check the Response tab
+
+User: I got this.
+
+
+
+RustDesk: In the developer tools console, the error logs indicate that the Content Security Policy (CSP) is blocking the loading of Base64 images. We can also see in the Network panel that the Base64 images fail to load. Could you please confirm if there have been any recent changes to the site's Content-Security-Policy settings?
+
+
+Also, could you clarify what proxy software is being used—is it Nginx? If possible, could we take a look at the RustDesk website’s Nginx configuration?
+
+User: we found the rule that blocked the images in Nginx.
+
+
+The following rule blocked the Images:
+
+add_header Content-Security-Policy "img-src 'self';connect-src 'self'; frame-ancestors 'self'; block-all-mixed-content; upgrade-insecure-requests;" always;
+
+
+
+We have added some new rules in January, to improve the security of our hosted websites.
+
+This rule was one of them.
+
+
+
+Your reference to Nginx brought it to our attention.
+
+We weren't aware that the changes had an impact on rustdesk, as everything else was running normally.
+
+
+
# Connection Log or device name on devices page of web console is empty
Actually it is the same problem as above, [set correct `API` (the same as web console address)](https://github.com/rustdesk/rustdesk/wiki/FAQ#failed-to-log-in-with-custom-client-build-or-public-release-with-wrong-api-settings), you have wrong API settings.