Setting up weinre remote debugging

what is remote debugging
chrome remote debugging
weinre alternative
enable usb debugging remotely
debug js remotely
weinre github
remote debug ios-webkit
chrome remote debugging no devices detected

Instructions for running weinre state that I need to insert following script:

<script src="http://a.b.c:8081/target/target-script-min.js"></script>

where http://a.b.c is my server IP or host name.

Couple of questions:

Does this mean that I must open port 8081 on my remote server?

Also what is the target-script-min.js? It looks like I need to upload it to a target folder?

The way you start the weinre sever is by running the command


in your command line. And then you leaving it running for as long as you're still using weinre. You have options for this command that you can find by type weinre --help, but the important ones are --boundHost, and --httpPort. --boundHost defaults to localhost and --httpPort defaults to 8080. So run

weinre --boundHost

where is your ip address, which you can find by running ipconfig. Put the following in your code:

<script src=""></script>

Then, in your browser, go to

I wrote a blog post about it here:

To answer your second question, the target-script-min.js is just a javascript file that's a part of weinre whenever you install it. When you have weinre running, you can visit

to see the file if you want.

Setting up weinre remote debugging, npm -g install weinre. You can find more instructions installing weinre HERE. Now run the command weinre --help to see all available options. The debugger that performs the debugging is called the debugging server. The second debugger, called the debugging client, controls the debugging session from a remote location. To establish a remote session, you must set up the debugging server first and then activate the debugging client.

The weinre server is "started" by executing this command weinre --boundHost a.b.c.d where a.b.c.d stands for the local IP of the desktop used for debugging. The port 8080 will be opened (default port, but you may configure an other one).

At this point, the script http://a.b.c.d:8080/target/target-script-min.js becomes available on your local network, and may be called by your application located on an other device in the same local network.

If your application or tested web page call this script, it will be seen by your desktop.

Therefore, you don't have anything to upload on your target...

Remote debugging localhost with weinre ( and HTTPS too ), Debug Server: This is the HTTP server that you run from the weinre-node distribution. Can probably be set larger, but then your browser may time out. If you've use the --boundHost -all- option, then bring up the debug client using the mobile device, and see the two connect in the Remote panel of the debug client. If we need to debug default browsers, we have to use any other debugging tool. Here, in this post, we'll discuss about another wonderful remote debugging tool known as Weinre. Install Weinre # Weinre is available as an npm package. If you have configured npm in your system, let's install weinre globally with the below command: npm -g install weinre

Weinri debug resume

After successfully installed weinri,

1 - Run this command with your ip address:

  weinre --boundHost

2 - Attach in your code header:

<script src=""></script>

3 - Access your website in your tablet or whatever device

3 - Get the wenri debug screen on:


Obs: 'anonymous' word can be replaced by another of your choice.

weinre, Home - User Interface - Installing - Running - Multi-User - Security - Building weinre is a debugger for web pages, like FireBug (for FireFox) and Web Since then, some platforms are starting to provide remote debugger capabilities, as part of their platform tool set. Android: Remote Debugging on Android with Chrome. Remote debugging with weinre Installation and setup. The first step is to install weinre. In the past this ran on a horrible Java server, but recent Begin debugging. The next step is to make the pages you want to test visible to all devices. To achieve this you’ll need Next steps. Once you’ve

if you can't debug your html page even after completing all of the steps mentioned in the Nokia Developer Article, then check your windows firewall settings.Please be sure that the firewall setting for private network is TURNED OFF ..

weinre, Installation and setup. The first step is to install weinre. In the past this ran on a horrible Java server, but recent development work means it now  Remote debugging tool like weinre, replacing web inspector with the latest chrome devtools frontend. Speed up your development with this new VS Code extension.

Remote debugging with weinre, This tool saved me when I was trying to debug a web app that was misbehaving only on the Duration: 12:40 Posted: Jun 5, 2015 Set up the remote debugger On the remote computer, find and start the Remote Debugger from the Start menu. If you don't have administrative The first time you start the remote debugger (or before you have configured it), the Remote Debugging Configuration If the Windows Web Services API is not

weinre - How to set it up Remotely and locally, Using Weinre Remote Debugger. The Weinre debugging feature allows you to debug your app while testing it in the browser or on a device. To enable the  weinre is WEb INspector REmote. Pronounced like the word "winery". Or maybe like the word "weiner". Who knows, really. weinre is a debugger for web pages, like FireBug (for FireFox) and Web Inspector (for WebKit-based browsers), except it's designed to work remotely, and in particular, to allow you debug web pages on a mobile device such as a phone.

Weinre Debugger, It's a fantastic tool allowing you to remotely inspect and debug web apps - including those running on a mobile device. In order to get set up to  The weinre server will inject some JavaScript in your app through a script to allow the debugging to happen. Technically, using weinre is enough to start the server but here are 2 useful options that you might as well pick up straight away: $ weinre --boundHost --httpPort 8888