Problems Remote Debugging with SourceMaps in SuperDevMode

[b***@gmail.com]

Using Chrome, I've got SDM working locally - reloading the page trips the
CodeServer I have running in Eclipse, and the sourcemaps are accessible in
Chrome via 127.0.0.1:9876 in the sources tab.

However, I wanted to try access from another machine. So I made the
changes to my setup that are mentioned on the web:

- I added "-bindAddress 0.0.0.0" to the SuperDevMode launch program
arguments.
- I added <set-configuration-property name="devModeUrlWhitelistRegexp"
value="http://.*" /> to the GWT Project and rebuilt it
- I tried opening http://application-server:port/?superdevmode=ip:port
rather than simply http://application-server:port (though this one didn't
seem to make a difference)

With the above approach, I am able to run the CodeServer remotely. I see
CodeServer run in Eclipse on the host machine, and the page loads on the
client machine and appears to work fine. *However, there are no sourcemaps
available in Chrome on the remote machine (or any other browser). *I tried
disabling the firewall with no change.


Host machine: OpenSUSE 13.1, Chrome 43.0.2357.65
Client machine Windows 7 SP1 x64, 43.0.2357.130

Can anyone else confirm this is broken? If so I will file an issue on
GitHub.

(Note: I am planning to post a separate thread regarding SDM not working
locally in Firefox, so please limit discussion here to remote access
issues.)

[b***@gmail.com]

Looking over on GitHub for existing issues, I saw that someone else
reported an issue with DNS resolution. With that in mind, I modified by
client machine's host file to include a binding for the fully qualified
name of my host machine, and when I reloaded hte page, source maps were
there!

This is even though (or because?) I was accessing the server page via IP
address rather than name. it never crossed my mind that anything on the
client would resolve that address to a name, but then fail when trying to
reverse it back to an IP address.

[Jens]

Post by b***@gmail.com
Looking over on GitHub for existing issues, I saw that someone else
reported an issue with DNS resolution. With that in mind, I modified by
client machine's host file to include a binding for the fully qualified
name of my host machine, and when I reloaded hte page, source maps were
there!
This is even though (or because?) I was accessing the server page via IP
address rather than name. it never crossed my mind that anything on the
client would resolve that address to a name, but then fail when trying to
reverse it back to an IP address.

Just had the same issue. Sometimes my host fails to update the DNS reverse
entry when it gets a new IP address. So when I do nslookup <hostname> I get
an old IP as answer. As chrome might do a DNS lookup (depending on how the
source maps url is stored in the JS output of GWT), it gets the wrong IP
and can not access the CodeServer under that wrong IP => no source maps.

Setting an entry in the hosts file or updating the DNS reverse entry for
your host name solves the problem.

-- J.

[Carlo]

Hello,

sorry for resuming this old thread.
I have as well a code server running on remote and I would like to use SDM
via my local browser. SDM works fine but it seems that the browser never
asks for the source maps.
I see in the sdm logs "source maps enabled", but then I cannot see any
request from the browsers. I can see that SM are generated on my remote
server.

I have tried to add an entry in my host file but no luck.
The remote server is running on Linux and the browser on Windows 7.
Any other possible workaround?

Thanks,
Carlo

Post by b***@gmail.com
Looking over on GitHub for existing issues, I saw that someone else

Post by b***@gmail.com
reported an issue with DNS resolution. With that in mind, I modified by
client machine's host file to include a binding for the fully qualified
name of my host machine, and when I reloaded hte page, source maps were
there!
This is even though (or because?) I was accessing the server page via IP
address rather than name. it never crossed my mind that anything on the
client would resolve that address to a name, but then fail when trying to
reverse it back to an IP address.

Just had the same issue. Sometimes my host fails to update the DNS reverse
entry when it gets a new IP address. So when I do nslookup <hostname> I
get an old IP as answer. As chrome might do a DNS lookup (depending on how
the source maps url is stored in the JS output of GWT), it gets the wrong
IP and can not access the CodeServer under that wrong IP => no source maps.
Setting an entry in the hosts file or updating the DNS reverse entry for
your host name solves the problem.
-- J.

[Thomas Broyer]

You could try https://github.com/tbroyer/gwt-devserver

Post by Carlo
Hello,
sorry for resuming this old thread.
I have as well a code server running on remote and I would like to use SDM
via my local browser. SDM works fine but it seems that the browser never
asks for the source maps.
I see in the sdm logs "source maps enabled", but then I cannot see any
request from the browsers. I can see that SM are generated on my remote
server.
I have tried to add an entry in my host file but no luck.
The remote server is running on Linux and the browser on Windows 7.
Any other possible workaround?
Thanks,
Carlo

Post by b***@gmail.com
Looking over on GitHub for existing issues, I saw that someone else

Post by b***@gmail.com
reported an issue with DNS resolution. With that in mind, I modified by
client machine's host file to include a binding for the fully qualified
name of my host machine, and when I reloaded hte page, source maps were
there!
This is even though (or because?) I was accessing the server page via IP
address rather than name. it never crossed my mind that anything on the
client would resolve that address to a name, but then fail when trying to
reverse it back to an IP address.

Just had the same issue. Sometimes my host fails to update the DNS
reverse entry when it gets a new IP address. So when I do nslookup
<hostname> I get an old IP as answer. As chrome might do a DNS lookup
(depending on how the source maps url is stored in the JS output of GWT),
it gets the wrong IP and can not access the CodeServer under that wrong IP
=> no source maps.
Setting an entry in the hosts file or updating the DNS reverse entry for
your host name solves the problem.
-- J.