diff --git a/FAQ.md b/FAQ.md
index f2c4ba1..4ed6c7c 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -735,6 +735,15 @@ The final reason is related to the user's cloud provider.
 
 If you run container (Docker etc), there might be DNS problem with container.
 
+# Docke ssl problem
+> User: We are using docker compose and after a reboot of Rustdesk the console is displaying “License is not verified yet”. License key hasn’t changed since installation and editing it gives us error below :
+![image](https://github.com/user-attachments/assets/ecaf5bd7-35a3-44ac-afac-0d584f707ce1)
+
+> RustDesk: It seems your docker container has ssl certificate problem, I would suggest you run with native package on the host with out container, or build a new container. about license migrate please: https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/license/#invoices-license-retrieval-and-migration
+
+> User: Thanks, we’ve been able to resolve the issue and the server seems to be working without problem now.
+ 
+
 # Windows 10 opens the software with a white screen and no content (monitor/display turned off)
 https://github.com/rustdesk/rustdesk/discussions/10344
 
@@ -833,13 +842,5 @@ Then on the controlling side, you can use [default-connect-password option](http
 
 > User: Yes, I stopped the service via the tray icon in Windows. My mistake! The problem is solved. Sorry for taking up your time.
 
-# Docke ssl / dns problem
-> User: We are using docker compose and after a reboot of Rustdesk the console is displaying “License is not verified yet”. License key hasn’t changed since installation and editing it gives us error below :
-![image](https://github.com/user-attachments/assets/ecaf5bd7-35a3-44ac-afac-0d584f707ce1)
-
-> RustDesk: It seems your docker container has ssl certificate problem, I would suggest you run with native package on the host with out container, or build a new container. about license migrate please: https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/license/#invoices-license-retrieval-and-migration
-
-> User: Thanks, we’ve been able to resolve the issue and the server seems to be working without problem now.
-