What did you do? ================ Attempting to do this. https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugging/Debugging_Firefox_for_Android_over_Wifi What happened? ============== Would not work on a corporate network. It appears that connections to remote website(s) are done to register both ends of the debugging session and these could be blocked on a corporate network (where everything is blocked by default). If the registration is not done the debugging PC can not "see" the device you are attempting to debug. What should have happened? ========================== The ports, ips (DNS), and protocols required so that this will work should be clearly documented so that developers behind a corporate firewall can use these tools. It appears that this will not work if either device can not reach servers which are not on the local network. Is there anything else we should know? ====================================== This is posted on StackOverflow as well with a detailed description of the problem. http://stackoverflow.com/questions/41644027/firefox-webide-port-requirements-on-a-corporate-network
Ryan, can you help with this? I'm not sure what the best thing to say here is.
I have updated the WebIDE troubleshooting page with details on the networking requirements. I also copied them as an answer to the StackOverflow question. I also added more links to the troubleshooting page from the various other "setup" pages about remote connections. For the reporter, if you have more questions about this, I recommend the DevTools Discourse forum for questions like this. It is actively watched by engineers on the DevTools team. : https://developer.mozilla.org/en-US/docs/Tools/WebIDE/Troubleshooting#Connecting_to_Firefox_for_Android_over_Wi-Fi : https://discourse.mozilla-community.org/c/devtools
Thank you Ryan!
Thanks! This makes perfect sense now. This will be a big help. Also thanks for the top about devtools.