Introduction

This guide will help you access the STB browser debug page.

Please note that all browser logs are, by default, being redirected to STB logs.

Prerequisites

This article assumes that you have an Amino Enable device.

Summary

For WebKit releases,

1. SSH/Ensight to the STB
2. Run the command: ~# touch /mnt/persist/webkit/enable_web_inspector
3. Run the command: ~# killall browser
4. Run the command: ~# /etc/init.d/S38iptables stop
5. On your PC, open remote inspector (http://<STB_IP>:9222)

For Chromium releases,

For releases that are deployed with the chromium browser, you will first need to change your Boot Argument.

1. Add the following parameters to the Boot Argument:

--remote-debugging-port=9222 --devtools-frontend-url=http://resources.core.cloud.vewd.com/devtools/4.20/inspector.html

2. SSH to the STB

3. Run: ~# /etc/init.d/S38iptables stop

4. Open remote inspector on your PC (http://<STB_IP>:9222)

Note: Latest Remote Inspector testing was done on Chrome 53. Please use this version if you find any problem with your current browser version.

If you find issues running console commands on the latest chrome version (i.e. enter key changes line instead of running commands) follow these steps:

1. Open the Remote Inspector console tab.
2. Press F12 on chrome to open debug page.
3. Run the piece of code below.
4. Close the debug page and confirm you are able to run JS commands when pressing Enter.

isEnterKey = function(event){
    return event.key == 'Enter' && event.keyCode == 13;
}

Reference

None.