My environment is Debian Stretch x86-64 (running inside VirtualBox on a macOS host) attempting to run tests using the Android Emulator with a cross-compiled ARM Android build. Specifically when I run |./mach test gfx/layers/apz/test/mochitest/test_group_zoom.html| the Android Emulator's attempt to browse to |mochi.test:8888/tests?...| ends with a very sad "The proxy server is refusing connections" error message. When I run a server with |./mach robocop --serve| I can confirm that I'm able to access it in the emulator at |10.0.2.15:8888| (the value of |_SERVER_ADDR|) as well as |10.0.2.2:8888| (which is apparently a magic value for the host). I'm not sure how to debug beyond this. This was all performed at m-c rev a007dd56b994.

Don't know how useful this is, but here's what this whole thing looks like.

Note that Alex is running in VirtualBox because he can't run Android mochitests on a macOS host because the mac host-utils are out of date (and we are a little stuck on getting that sorted out because of the signing requirements).

His linux host-utils, as shown in comment 1, appear to be up to date (that's what I run).

I worked with Alex on this yesterday and I'm stumped. I would expect mochi.test:8888 to forward to 10.0.2.2:8888. If he has confirmed manually that an emulator browser can see the server at 10.0.2.2:8888, why would the mochi.test:8888 query indicate a refused connection? :jmaher - ideas?

is there a chance the proxy auto config didn't get setup properly in the browser? it is a long string and I remember last month that :bc: hit a scenario where the browser rejected the profile due to a pref being too long (which was the proxy auto config)

Definitely sounds like a possibility; how would one verify that?

Yes, that's a good idea. See bug 1437585. I don't know much about it.

adb logcat doesn't show any messages with "autoconfig" in them, so I guess it's probably not that, assuming the error message hasn't changed.

I've also confirmed in about:config that |network.proxy.autoconfig_url| has a data URI with a pile of javascript.

if that is the case, then I don't see why it would fail. so manually from the UI: http://10.0.2.2:8888 -> works http://mochi.test:8888 -> fails could you make sure both of those above assertions are accurate from a browser launched via the automation harness. Possibly we turned off external network access or did something goofy with our preferencees.

Yes, 10.0.2.2:8888 loads fine in a browser launched via ./mach test; though if I browser to the same path/querystring as the mochitest was trying to load, with just s/mochi.test/10.0.2.2/ the page just loads the text "bad request".

odd, I am out of ideas- this has been used for many years both on desktop and mobile. I assume bad request has to do with the server being contacted and it not returning. with PAC, I believe it is all on the desktop vs other networking getting involved.

Do you know if other folks have had success with the emulator-host being a VM? That's the only thing I can think of that's remotely novel here.

(In reply to Geoff Brown [:gbrown] from comment #2) > Note that Alex is running in VirtualBox because he can't run Android > mochitests on a macOS host because the mac host-utils are out of date (and > we are a little stuck on getting that sorted out because of the signing > requirements). mac host-utils have been updated now. 'mach robocop' or 'mach mochitest', etc should offer to update your host-utils to 60.0a2.

Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.