The two most common reasons for that are network issues and overload. If customers report stable connection then the flapping is most likely caused by devices having issues connecting to the UISP console correctly.
If they are getting outages of internet service, then UISP is reporting the actual status just as it should. NOTE: A flapping connection occurs when the device is repeatedly switching status from "Active" to "Disconnected", often within a narrow time frame.Īs a first step, it is necessary to find out if the flapping is being experienced by the customers as well. In order to send those files please follow the guide above. If the device can ping the UISP hostname but it cannot connect anyway, please send us the output of these tests as well as support info of the device and your UISP. Replace the with the actual hostname of your UISP console and remove the :Ģ, Traceroute from the device to the UISP console: traceroute -n ģ, Check if the connection is upgraded to WebSocket: curl -insecure -include -no-buffer -header "Connection: Upgrade" -header "Upgrade: websocket" -header "Host: :80" -header "Origin: " -header "Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ=" -header "Sec-WebSocket-Version: 13" The output should look like this: HTTP/1.1 101 Switching Protocols Here are the other two commands that can be used to get more information about the network issue. The connection can be also impossible if there is any packet loss or high latency (over 400ms). If the ping cannot go through, there is a network issue either in the device's configuration or on the route from the device. Please note that some of those commands may be inaccessible on some devicesġ, Use SSH to get into the device and try to ping the hostname of the UISP console.
There are three basic tools that can be used to check if the route from the device to UISP is free. and attach it to a support request as described in the Overview above (or send it as a reply if you already have an open ticket).Įach device needs to have a clear route to the UISP console in order to connect.
#How to find docker ip addresssnot found download#
tmp/2 /home/unms/data/logs, download the 2 file from the /tmp folder. In case, any container is failing, please run this command sudo tar -cvjSf For that reason, the first step should always be to check on those containers by running the sudo docker ps command. Suspension/Traffic shaping is not working.NOTE: If you already have an open ticket about your issue, you can just reply to the last email you received from our support team and send the support info or any other additional information and requested files.
0 kommentar(er)
