| Question: |
Hello! Today it was discovered that the site http://machineplus.ru also the control panel on the hosting site http://46.29.2.55:2082 NOT AVAILABLE... |
| Answer: |
Hello
please Do a trace to Your domain: start - run - enter cmd - in the black window enter tracert YOUR DOMAIN - after click to highlight - making enter - skopirovat here in the ticket If You are experiencing zatrudina, view instructional videos http://ded07.net/helphost/tracert.htm |
| Question: |
Tracing route to machineplus.ru [46.29.2.77]with the maximum number of jumps 30: 1 <1 MS <1 MS <1 MS 192.168.1.1 2 26 ms * * 100.87.0.1 3 26 ms 28 ms 26 ms core1-nat.mf.belpak.by [93.85.81.193] 4 34 ms 26 ms 27 ms 10.0.51.45 5 39 ms 28 ms 28 ms core.net.belpak.by [93.85.253.129] 6 26 ms 26 ms 27 ms ie2.net.belpak.by [93.85.80.42] 7 26 ms 25 ms 24 ms asbr1.net.belpak.by [93.85.80.98] 8 35 ms 33 ms 33 ms ae7.RT1.NTL.KIV.UA.retn.net [87.245.237.21] 9 55 ms 67 ms 55 ms ae2-7.RT.IRX.VIE.AT.retn.net [87.245.233.138] 10 80 ms 54 ms 54 ms vix.invitel.net [193.203.0.160] 11 95 ms 67 ms 60 ms 31.210.11.37 12 * * * timed out for the request. 13 * * * timed out for the request. 14 * * * timed out for the request. 15 * * * timed out for the request. 16 * * * timed out for the request. 17 * * * timed out for the request. 18 * * * timed out for the request. 19 * * * timed out for the request. 20 * * * timed out for the request. 21 * * * timed out for the request. 22 * * * timed out for the request. 23 |
| Question: |
Tracing route to machineplus.ru [46.29.2.77]with the maximum number of jumps 30: 1 <1 MS <1 MS <1 MS 192.168.1.1 2 26 ms * * 100.87.0.1 3 26 ms 28 ms 26 ms core1-nat.mf.belpak.by [93.85.81.193] 4 34 ms 26 ms 27 ms 10.0.51.45 5 39 ms 28 ms 28 ms core.net.belpak.by [93.85.253.129] 6 26 ms 26 ms 27 ms ie2.net.belpak.by [93.85.80.42] 7 26 ms 25 ms 24 ms asbr1.net.belpak.by [93.85.80.98] 8 35 ms 33 ms 33 ms ae7.RT1.NTL.KIV.UA.retn.net [87.245.237.21] 9 55 ms 67 ms 55 ms ae2-7.RT.IRX.VIE.AT.retn.net [87.245.233.138] 10 80 ms 54 ms 54 ms vix.invitel.net [193.203.0.160] 11 95 ms 67 ms 60 ms 31.210.11.37 12 * * * timed out for the request. 13 * * * timed out for the request. 14 * * * timed out for the request. 15 * * * timed out for the request. 16 * * * timed out for the request. 17 * * * timed out for the request. 18 * * * timed out for the request. 19 * * * timed out for the request. 20 * * * timed out for the request. 21 * * * timed out for the request. 22 * * * timed out for the request. 23 * * * timed out for the request. 24 * * * timed out for the request. 25 * * * timed out for the request. 26 * * * timed out for the request. 27 * * * timed out for the request. 28 * * * timed out for the request. 29 * * * timed out for the request. 30 * * * timed out for the request.Trace complete. |
| Answer: |
You can go to the control panel.? |
| Question: |
no, the same thing - timed out waiting for a response |
| Question: |
Paste in the address bar of the browser http://46.29.2.55:2082/ Answer: the Problem is when the page loads (it`s in the title), and the message is \"connection timeout expired\" |
| Answer: |
Try to restart your router |
| Question: |
Rebooted the router. The site is already available, and the control panel yet. Browser says the same thing - waiting time has expired, and one error: \"XML parsing Error: undefined parser state Address: jar:file:///C:/Program%20Files%20(x86)/Mozilla%20Firefox/browser/omni.ja!/chrome/browser/content/browser/aboutNetError.xhtml Line 395, character 58: &netInterrupt.longDesc; \" |
| Answer: |
Chistie the browser cache |
| Question: |
OK! Thanks, using FileZilla Client went without problems. |
| Answer: |
OK |
| Question: |
only when I went to the control panel via the billing panel, I saw that it has changed the IP address! Was http://46.29.2.55:2082 and became http://46.29.2.56:2082 |
| Answer: |
it`s the same server. |
