I used Andronix/Termux to install Ubuntu 20.04 on an Android device. The Chromium Web Browser connects to the internet. Does it connect by default through a proxy and, if so, how can I determine the proxy? I've tried commands shown on the internet using lxterminal without success.
Related
I do development on my laptop, currently running Mac OSX Ventura. At the moment, I find myself sitting on a network that uses pi-hole, and is blocking many of the destinations that my NextJS backend needs to reach.
I've spun up an EC2 instance and used SSH to tunnel through it, and have confirmed that I can set the SOCKS proxy in Safari and it works fine. However, SOCKS is application specific. How do I tell my NextJS dev environment to use the local proxy?
I am trying to understand how to work with apple passes whilst using localhost. I am using Android Usb debugging so I can visit my website served on localhost from my phone. I have also setup the signing, compressing and installation of the passes.
What I don't understand, is how to debug communications between the installed pass and my server. I don't seem to be receiving requests from the pass once it is installed. Is this because I am using localhost? I inserted localhost as the web service in the pass.json file used to generate the file. My problem is understanding how to debug the problem as I am getting no feedback to work on.
Localhost won't work as the device will view localhost as itself, not as your computer.
To work locally:
connect your phone and computer to the same wireless network
allow http in the developer menu of your iPhone (otherwise the pass will be rejected for not having a https webServiceURL)
use http://computerIp:8080/ as the webServiceURL
serve your web service on your computer on port 8080
For feedback you can view your device logs in Xcode or in the OSX Console application.
I'm having trouble running a selenium test run, using google chrome headless, accessing a site which is only available through a proxy server.
TLDR: Chrome headless can't access sites through a proxy server unless fiddler is running
Trying to diagnose the problem, I've found a strange set of circumstances that cause it to work:
Internet explorer is configured to use the proxy and the site can be accessed only when the proxy is turned on. Without the Internet Explorer proxy set, there is no connectivity to the site whatsoever.
Chrome uses the Internet explorer proxy settings, so access to the
site using chrome depends on the Internet explorer proxy being set.
As long as the Internet Explorer proxy is set:
When the Selenium tests are run with chrome (not headless), the site is accessed successfully.
When the Selenium tests are run with chrome (headless), the site is not accessed successfully (it times out).
If the proxy server configuration is passed through to chrome* (headless),
the site is not accessed successfully.
If the proxy server configuration is not passed through to chrome (headless), the site is not accessed successfully.
If we install fiddler on the server, the proxy settings are replaced with the Fiddler proxy, and suddenly selenium tests running through chrome (headless) work successfully. And:
If the proxy server configuration is passed through to chrome*
(headless), the site is accessed successfully.
If the proxy server configuration is not passed through to chrome (headless), the site is accessed successfully.
Proxy server configuration passed through to chrome using
chrome_options.add_argument.
Notes:
- There are no chrome extensions enabled.
The website is using HTTP, so there is no issue caused by certificates
Accessing the website via a route that doesn't need a proxy server, such as from our desktops, chrome headless works.
I've tried this on two different servers, with identical behaviour.
The proxy server doesn't require authentication.
So chrome headless can't access the sites through the proxy unless fiddler is running. Does anyone have an idea why this could be, and how I get it working without having Fiddler running?
I used network monitor to see that the headless chrome calls were resolving to a website IP address, rather than that of the proxy, so it looked like headless chrome wasn't using the default proxy, as suspected.
In the end, configuring the nunit tests to pass the proxy server in to headless chrome using the --proxy-server argument did the trick.
I started web server on mac using following command.
# apachectl start
But other devices in same private network can not be able to access the http service of my mac pc. Browser was showingsite unreachable.
How i can solve this problem?
I am successfully connecting to the internet using an application called tether for a jailbroken iphone. (I know there's better options now).
My iphone is connected to my laptop's wifi "device network".
I have in my OS X network settings a location called iphone and the proxy is configured to use the correct IP and port for the phone.
I can browse the internet using Chrome over http and https perfectly.
iTerm cannot ping google. Git cannot pull. I've googled for days and don't see anything "easy" or that I understand. Any advice is appreciated.
Command-line tools usually only support HTTP proxy. For providing a HTTP proxy out of a SOCKS one you have Privoxy. After you've set up Privoxy you have an HTTP proxy. In terminal usually saying export http_proxy=ip:port is enough for most applications. For Git specifically consult here.
But if that's too much for you, you can use sshuttle. It transparently transfers all your connections through a SOCKS proxy. That is, all the connections in your computer, and after that you don't have to change proxy settings for your GUI apps.
I use Homebrew as my package manager in Mac, and both Privoxy and sshuttle are available in it.