Differences

This shows you the differences between two versions of the page.

--- en:firewallconfiguration [2018/09/20 14:33]
admin ↷ Liens modifiés en raison d'un déplacement.
+++ en:firewallconfiguration [2023/10/18 21:54] (current)
admin [First fix attempt that should be performed]
@@ Line 1: / Line 1: @@
 ====== How to avoid "unstable connection" ======
 ===== Why this is happening? =====
-|{{public:en:unstable1.jpg?nolink|}}|{{public:en:unstable2.jpg?nolink|}}|
+|{{public_media:en:unstable1.jpg?nolink|}}|{{public_media:en:unstable2.jpg?nolink|}}|
 You may have noticed some screen with the "unstable connection" warning sign.
 This situation happens when the real-time communication channel between the screen and the server is dropped.
 The real-time communication is needed in order to get screen status or other information as well as sending orders to the display (turn on, turn off, change content, get a screenshot, reboot, etc.).
 The main root cause of this issue is the firewall configuration and can  be solved easily most of the time.
+===== First fix attempt that should be performed =====
+<WRAP center round info 60%>
+We noticed that with some firewalls / routers or ISP the problem can easily be solve by **switching the display connection to zebrix to https instead of http**.
+</WRAP>
+  * On a SAMSUNG screen, you must change URL from, for example, http://screen.zebrix.net to https://screenv2.zebrix.net. [[en:changement_url_tizen|Here is how you can change the URL on a SAMSUNG screen]]
+  * On a zebrix player, you must open the configuration tool and select https instead http in the "protocol" section. [[en:changement_url_nuc|Here is how to open the configuration tool on a zebrix player]]
+By experience, this problem has often been reported with **PROXIMUS (Belgium)** et **TELENET (Belgium)** ISPs. We were not able to understand the root cause of this issue, we don't know if the problem is related to these ISP networks or to the Modem/Router/firewall offered by these ISPs.
 ===== Firewalls known to be concerned by this problem + solutions =====
 ==== Fortinet Fortigate ====
@@ Line 26: / Line 36: @@
 ==== Stonesoft ====
 The problem on stonesoft firewall can easily be fixed by turning off the **"Deep Inspection"** and switching the **"Connection tracking mode"** to **"Loose"**
-{{ public:stonesoftexample.jpg?nolink |}}
+{{ public_media:stonesoftexample.jpg?nolink |}}
-==== With certain Proximus routers ====
-Switching the connection of screens to https instead of http fixes the problem.
 ==== Bluecoat Proxy / Firewall ====
 It has been noticed that bluecoat proxy antivirus module regularly close the channel to do its scanning job. If turning off the antivirus is not an option for you, consider to switch the connection of screens to https instead of http fixes the problem.