December 02, 2021, 09:21:47 AM
Welcome, Guest. Please login or register
News: Stay up to date with everything that's happening at

MediaSignage support forum

Author Topic: Information on Port 80 and Desktop Player communication  (Read 5339 times)


  • Administrator
  • Hero Member
  • *****
  • Posts: 5137
  • Karma: +35/-8
    • View Profile
Information on Port 80 and Desktop Player communication
« on: February 26, 2010, 02:44:26 PM »
2.5 Firewall

The SignagePlayer communicates with the hosted servers over TCP/IP. The protocol uses http (as well as RSA public / private keys over standard http) and raw sockets. In order to insure proper operation the SignagePlayer must be allowed to communicate with the hosted servers within the Digital Signage network. The mediaBOX does not include an internal firewall and so no special configuration is required. However if your local area or corporate network does have a firewall, you will need to insure proper rules exist within your firewall to allow traffic originating from the mediaBOX to pass through.

The following are conditions which must exist on your network’s firewall:

Source: mediaBOX
IP address Destinations:
master . signage . me
business . signage . me
Manage1 . signage . me
Manage2 . signage . me

Protocol: TCP/IP: Socket connection

Port: 80

Note that if you have a firewall with an existing port 80 rule, this may NOT be enough. The reason is that many firewalls will only allow HTTP traffic. However, the mediaBOX communicates using a persistent TCP/IP socket connection. You may need to add a rule in your gateway / router to specifically allow connection oriented traffic over port 80 (not just HTTP). You should know that opening port 80 on your firewall does not compromise in any way the security of your local area network. Allowing trusted traffic originating from within the LAN onto a specific destination is common practice. It does not induce any potential


Carbonate design by Bloc
variant: carbon
SMF 2.0.12 | SMF © 2016, Simple Machines