How can I recover my BSN.
...
Cloud/BSN username and/or password?
Expand | ||
---|---|---|
| ||
USERNAME Your BSN.cloud Cloud and BrightSign Network username is your email address. If you are using plus-addressing to create a different email address that goes to the same inbox, be aware that each username is different to the system. Check your email for messages from BSN.cloud Cloud (the sender will be noreply-brightsign@brightsign.biz) and check the To: field for the correct username. PASSWORD (BSN.cloudCloud)
PASSWORD (BrightSign Network) As long as you have your username and network (account) name, you can use Forgot Password to get a new password. If you are a user on multiple networks, any of those network names will do - your password is the same for all BrightSign Network networks. The email will come from noreply-brightsign@brightsignnetwork.com so be sure to add it to your whitelist or contact list to ensure it does not go into spam/junk/quarantine. Do not include the trailing period from the new password, and make sure there are no leading or trailing spaces. If you cannot access the email address associated with the account and you do not have any other administrators on the account that can set up a new user login, see this article. |
Moving a player from one group to another did not work in BSN
Expand | ||
---|---|---|
| ||
If you move a player from one group to another in the BSN Web UI and either or both groups do not have a presentation scheduled, the move will fail to apply. The player will look like it moved, then shortly thereafter will pop back up in the original group. Make sure presentations are scheduled on both the source and destination groups before trying to move the player. If the player status indicator is red and the player won't stay in the group you moved it to, but the player is connecting normally, then the player may be having trouble downloading the current-sync.xml file (i.e. the BSN sync spec) for the new group. To fix this:
|
...
|
Why are the player Err and Pwr lights both
...
flashing during BSN Setup?
Expand | ||
---|---|---|
| ||
This error occurs when the player cannot reach the BrightSign Network servers during the setup process. The initial setup process instructs the player to download a setup file (also known as a "recovery" file) from the BSN servers. If the player cannot download this setup file, it will flash the Err and Pwr LEDs and reboot after a few moments. This process will repeat until the player can establish a connection to the BSN servers and download the setup file. The Err and Pwr LEDs flash in unison on Series 3, 4 (XTx44, XDx34, HDx24, LS424) and Series 3 (XTx43, XDx33, HDx23, LS423) and 5 models. On earlier models, the Err and Upd LEDs flash instead. To troubleshoot this problem, you will need to resolve the connectivity issue between the player and the BSN servers. These are common connectivity issues: No Internet accessYou can perform Network Diagnostic tests to determine if the player has general Internet connectivity. There are two ways to perform these tests:
The DNS servers cannot resolve the BSN serversThe BrightSign Network servers are located on an Amazon S3 instance. If your provider cannot resolve these addresses, try configuring your network to use the Google Public DNS by setting the DNS addresses to 8.8.8.8 and 8.8.4.4. Proxy or firewall issueA network proxy or firewall may be blocking calls to the BrightSign Network servers on Amazon S3. See this FAQ for a list of ports and IP addresses that should be allowed. SSL or HTTPS issueThe initial setup step requires a secure call to the BSN servers. This call will fail if there's a certificate issue on the network or if a proxy server on the network is rejecting secure calls. The player cannot reach the default time serverThe player uses a BSN-based time server to set its time and date. Even if you set a different Time Server during the player setup process, the player must use the default time server the first time it checks in with BSN. This issue is caused by a firewall blocking HTTP time (HTP) calls or, if the player has been configured to use NTP, calls on UDP port 123. |
Why do I get a 403 error when connecting to BSN?
Expand | ||
---|---|---|
| ||
This error is caused by one of the following:
|
Why can’t I upload files to BSN?
Expand | ||
---|---|---|
| ||
Uploads can fail for a variety of reasons (connectivity issues, file problems, permissions issues, etc.). Sometimes, just trying again will resolve the problem. Otherwise:
If you still can’t resolve this issue, find the eventlog.txt file on your computer (see this page for more information) and send the log to support@brightsign.biz. |
Why can't I log in to my BSN account with BrightAuthor?
Expand | ||
---|---|---|
| ||
If you were able to log in to BSN previously, this could be a temporary outage. Otherwise try the following:
|
Why is the BSN status red in BrightAuthor when the unit is still connecting?
Expand | ||
---|---|---|
| ||
If the BrightAuthor connection status indicator is red, but the Last Connection time (located in the Manage > Status tab in BrightAuthor or the Current Usage tab in BSN) remains current, then there could be a temporary hiccup, a problem with file downloads, or nothing scheduled to play.
*The sync spec is an .xml file that lists all files required to play presentations currently scheduled for the group. The player compares this list to the files that are currently on local storage, and then downloads any missing files from the BSN servers. |
Why can't I see player logs in the WebUI under the Current Usage tab?
Expand | ||
---|---|---|
| ||
Before you can download the logs from your BSN network, you must enable the Logging options and specify when the logs should be uploaded from the player's SD card to the cloud. Logging options are enabled during the Unit Setup process (in either BrightAuthor or the BSN WebUI). Alternatively, if a BrightSign player is connected to your network, you can enable logging by going to Manage > Status, right-clicking the player, selecting Edit, and checking the corresponding boxes for Logging. Forcing Log UploadsIn addition to the automatic log uploads, you can manually send a command to each unit on your network to upload the logs. To do this:
You can also force log uploads in the WebUI:
It takes some time for the server to parse the logs and provide them for download in the WebUI Current Usage tab. Contacting the Device HandlerBrightSign players upload the logs to the device handler at the following URL: The Device Handler returns an HTTP 405 status if opened in a browser.
|