with: SSLTUNNEL_LOG_LEVEL=0 MOZ_LOG=proxy:5 https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&revision=5090712e68322e9ca7201786e68a97680c6ced8f It looks like the android-em emulators actually contact the ssltunnel since SSLTUNNEL messages appear in the log. It is not clear to me that usermedia is actually enabled though since there are : TypeError: navigator.mediaDevices is undefined errors. The android-hw devices do not contain SSLTUNNEL messages. The android-hw devices also contain 06:22:46 INFO - 04-09 23:15:47.531 I/Gecko ( 6447): [(null) 6447: Main Thread]: D/proxy pac thread callback PROXY 10.7.205.216:4454 Bitbar says that all ports are open and not blocked by a firewall. I disabled my local firewall and still reproduced the issue. Locally, Fennec can reach <myip>:8888 but not <myip>:4443. the ssltunnel config file used locally is $ cat /tmp/ssltunnelUXY_Cu.cfg httpproxy:1 certdbdir:/home/bclary/mozilla/builds/inbound/mozilla/build/pgo/certs forward:127.0.0.1:8888 websocketserver:192.168.1.7:9988 listen:*:4443:pgoserver listen:self-signed.example.com:443:4443:selfsigned listen:untrusted.example.com:443:4443:untrusted listen:expired.example.com:443:4443:expired clientauth:requestclientcert.example.com:443:4443:request clientauth:requireclientcert.example.com:443:4443:require listen:mismatch.expired.example.com:443:4443:expired listen:mismatch.untrusted.example.com:443:4443:untrusted listen:untrusted-expired.example.com:443:4443:untrustedandexpired listen:mismatch.untrusted-expired.example.com:443:4443:untrustedandexpired listen:no-subject-alt-name.example.com:443:4443:noSubjectAltName listen:bug413909.xn--hxajbheg2az3al.xn--jxalpdlp:443:4443:bug413909cert listen:www.bank1.com:443:4443:escapeattack1 redirhost:redirproxy.example.com:443:4443:test1.example.com listen:include-subdomains.pinning-dynamic.example.com:443:4443:dynamicPinningGood listen:bad.include-subdomains.pinning-dynamic.example.com:443:4443:dynamicPinningBad listen:badchain.include-subdomains.pinning.example.com:443:4443:staticPinningBad failHandshake:fail-handshake.example.com:443:4443 listen:sha1ee.example.com:443:4443:sha1_end_entity listen:sha256ee.example.com:443:4443:sha256_end_entity listen:imminently-distrusted.example.com:443:4443:imminently_distrusted ssl3:ssl3.example.com:443:4443 rc4:rc4.example.com:443:4443 ssl3:ssl3rc4.example.com:443:4443 rc4:ssl3rc4.example.com:443:4443 tls1:tls1.example.com:443:4443 Locally, ssltunnel is running on my host as a linux x86_64 executable from host utils. My local fennec build does have a ssltunnel arm binary. Should we be running it on the device instead of the host?
Bug 1335740 Comment 49 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
with: SSLTUNNEL_LOG_LEVEL=0 MOZ_LOG=proxy:5 https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&revision=5090712e68322e9ca7201786e68a97680c6ced8f It looks like the android-em emulators actually contact the ssltunnel since SSLTUNNEL messages appear in the log. It is not clear to me that usermedia is actually enabled though since there are : TypeError: navigator.mediaDevices is undefined errors. The android-hw devices do not contain SSLTUNNEL messages. The android-hw devices also contain EDITED TO ADD CORRECT MESSAGE I/Gecko ( 6749): [(null) 6749: Main Thread]: D/proxy DisableProxy http 10.7.205.214:4454 1800 Bitbar says that all ports are open and not blocked by a firewall. I disabled my local firewall and still reproduced the issue. Locally, Fennec can reach <myip>:8888 but not <myip>:4443. the ssltunnel config file used locally is $ cat /tmp/ssltunnelUXY_Cu.cfg httpproxy:1 certdbdir:/home/bclary/mozilla/builds/inbound/mozilla/build/pgo/certs forward:127.0.0.1:8888 websocketserver:192.168.1.7:9988 listen:*:4443:pgoserver listen:self-signed.example.com:443:4443:selfsigned listen:untrusted.example.com:443:4443:untrusted listen:expired.example.com:443:4443:expired clientauth:requestclientcert.example.com:443:4443:request clientauth:requireclientcert.example.com:443:4443:require listen:mismatch.expired.example.com:443:4443:expired listen:mismatch.untrusted.example.com:443:4443:untrusted listen:untrusted-expired.example.com:443:4443:untrustedandexpired listen:mismatch.untrusted-expired.example.com:443:4443:untrustedandexpired listen:no-subject-alt-name.example.com:443:4443:noSubjectAltName listen:bug413909.xn--hxajbheg2az3al.xn--jxalpdlp:443:4443:bug413909cert listen:www.bank1.com:443:4443:escapeattack1 redirhost:redirproxy.example.com:443:4443:test1.example.com listen:include-subdomains.pinning-dynamic.example.com:443:4443:dynamicPinningGood listen:bad.include-subdomains.pinning-dynamic.example.com:443:4443:dynamicPinningBad listen:badchain.include-subdomains.pinning.example.com:443:4443:staticPinningBad failHandshake:fail-handshake.example.com:443:4443 listen:sha1ee.example.com:443:4443:sha1_end_entity listen:sha256ee.example.com:443:4443:sha256_end_entity listen:imminently-distrusted.example.com:443:4443:imminently_distrusted ssl3:ssl3.example.com:443:4443 rc4:rc4.example.com:443:4443 ssl3:ssl3rc4.example.com:443:4443 rc4:ssl3rc4.example.com:443:4443 tls1:tls1.example.com:443:4443 Locally, ssltunnel is running on my host as a linux x86_64 executable from host utils. My local fennec build does have a ssltunnel arm binary. Should we be running it on the device instead of the host?