images wasnt updated

Author: mrc4tt

docs/CNAME

@@ -10,15 +10,15 @@ sidebar_label: Network troubleshooting
 WinMTR is a network diagnostics program that combines the features of ping and traceroute. The program was developed by Matt Kimball based on the well-known MTR program for Linux. It offers the possibility to get detailed information about possible network problems. The program also allows to track the time between sending a signal and receiving the corresponding response packet. In the following screenshot the outgoing route to fshost.me is shown as an example:
 
 
-![image](https://docs.fshost.me/img/winmtr-3.png)
+![image](https://help.fshost.me/img/winmtr-3.png)
 
 ## Installation
 
 
 
 ### Windows
 
-WinMTR for Windows can be downloaded from the [FSHOST](https://docs.fshost.me/WinMTR.zip) page. Once installed, the program must be started and the host name or IP address of the affected case needs to be filled in:
+WinMTR for Windows can be downloaded from the [FSHOST](https://help.fshost.me/WinMTR.zip) page. Once installed, the program must be started and the host name or IP address of the affected case needs to be filled in:
 
 ![image](https://user-images.githubusercontent.com/13604413/159171614-5ffff921-5d69-4786-8c8f-1a1f63413a97.png)
 
@@ -34,12 +34,12 @@ Now the package can be installed with the following command:
 apt install -y mtr-tiny
 ```
 
-![image](https://docs.fshost.me/img/aptlinux.png)
+![image](https://help.fshost.me/img/aptlinux.png)
 
 
 The evaluation can then be started with the command **mtr IPaddress/hostname**. By pressing CTRL+C you can stop the test at any time as desired.
 
-![image](https://docs.fshost.me/img/mtr.png)
+![image](https://help.fshost.me/img/mtr.png)
 
 
 ## Create report
@@ -53,7 +53,7 @@ The network diagnostic test should be performed when the problem actively occurs
 The program provides several kinds of information. You have to check this information carefully in order to identify the problem correctly.
 
 
-![image](https://docs.fshost.me/img/winmtr-2.png)
+![image](https://help.fshost.me/img/winmtr-2.png)
 
 While evaluating a route, the example message **No response from host** may appear from time to time, reporting 100% packet loss. However, this is often not the direct cause. In such a case it is possible that only the packets are filtered by the firewall and therefore no response comes or is generally unreachable. The next possible option for the route is then selected. Only if the packet loss starts at one point and continues through others is there active packet loss.