I recently followed many guides about how to get the chromebook into dev mode, allow modifications by making the linux OS writable and how the forwarding works. Also opened the firewall to allow any traffic. I've entered the --remote-debugging-port=2253 and --remote-debugging-address=0.0.0.0 to the /etc/chrome-dev.conf file. The reason I entered 0.0.0.0 is because to my understanding, chrome does not by default allow remote hosts to connect and is by default only listening to localhost. (This method worked on Ubuntu, macOS and windows devices.)
Now when I start chrome and browse to localhost:2253 I indeed get to see inspectable pages. However, I cannot access these from another machine. (Even with forwarding enabled)
Is there something I am missing or doing wrong? The reason I want to access these pages is because I'm trying to run an automated remote test (with puppeteer) that takes screenshots while 'using' our application.
I've also tried to take another path and get node running on the chromebook without success. I tried doing this with NVM but When installing NVM it fails because of permissions errors. Even when running as sudo.
I hope someone can help me so I can remotely connect to the device with the chrome devtools.
Related
I am used to using VS Code to work on projects locally on my (Windows) laptop. However, for a new project I'm working on, I need an Ubuntu VM, which I installed with VM Box. The issue is that developing directly in the VM is not as seamless as I would like it to be, which is why I want to connect to the VM remotely from my laptop.
I was able to connect to the VM, but all my VS Code User settings were seemingly reset or absent for the remote session. All my configurations in the settings but also the extensions were gone. If I open a local window, the settings are still there, but not in the remote session.
I get that it might be useful for virtual environments and things like that, but I don't want to have to copy all my user settings and reinstall manually all my extensions that I will use regardless of the project.
Is there any way to use my user settings for remote sessions as well?
I'm attempting to do some development on iOS for a model-viewer web component through browserstack (using iOS 13 Chrome) and it seems unable to connect to localhost, whether I use bs-local (as suggested via browserstack), my IP, or anything else.
I went through their troubleshooting guides with no success, and their own "Debug Connectivity" test in localhost:45454 seems to return a 200 OK response for my page, but live.browserstack.com still seems unable to connect (it returns "Unable to display the page").
I'm attempting to run it using iOS 13 on Chrome.
I've set up the proxy details, enabled 'Force Local', and installed the Browserstack Local app and have verified that it is connected correctly. The URL formats I have tried are:
http://localhost:8000/dev/index.html
http://bs-local.com:8000/dev/index.html
http://bs-local:8000/dev/index.html
http://<my-ip>:8000/dev/index.html
I am writing my code in VS Code and am using node.js/npm and npm run serve using Ubuntu (WSL) in the terminal to start the web dev server, which starts on its own correctly. Opening the page on my own machine seems to work fine, it is solely unable to connect through browserstack live.
Is there a step that I'm missing? What should I troubleshoot next? I'm a junior developer, so please explain in detail.
here's my problem, I have a Webservice that I run in tomcat using eclipse, and I have an android app connected to that Webservice. I access to that localhost using the local ip of my computer. Yes my phone is using same network. Sometimes when I launch the server, it's like I didnt, my app cant find a route and when I restart my computer everything works again. So my question is: What could be the problem because its kinda annoying to always have to restart my computer. I need a definitive solution. Thanks
On GitHub Desktop (I use it on Windows), I have had this error over the last few days:
My Internet connection seems to work fine though. What could cause the issue?
Is your internet connection goes through firewall/proxy server. I found that GitHub Windows client is only reliably works when no proxy enabled. Being windows (.NET to be precise) application it takes proxy settings as they defined in Internet Explorer connection settings. Meanwhile, Git itself, which GitHub Windows client desktop application simply uses via command prompt, is governed by http and https proxy settings in .gitconfig file or environment variables. This discrepancy makes it quite sophisticated to setup.
What's interesting, is that desktop app was working the first time I installed it fresh (never had it on this Windows), but it wasn't able to connect to GitHub. Then I started to fiddle with --global http/https settings and I broke the app. Now, even uninstalling and installing it back again, I still have connectivity issues, as it seems to remember settings somewhere, as it doesn't prompt me with welcome screen and does remember my name.
Worth to mention, that even if the app complains about connection, I can clone the repo with it.
This worked for me:
In Internet Explorer: Tools/Internet Options/Connections/LAN Settings
Uncheck "Use a Proxy server..."
Restart GitHub.
You might also be able to disable the Proxy Server via Edge. In my case, I found that after turning it off in IE, it was off in Edge also.
Edit: I also had to update the GitHub application in order to be able to clone to my local repository.
I have deployed my GWT application to its target environment (i.e. compiled and copied the war directory contents to the target device's /var/www) and some parts of it are not working. I understand that I can debug my local instance of the GWT app as if it were running in the target environment, by opening the deployed GWT App URL and adding gwt.codesvr URL parameter to it, like this:
http://deployment_host/gwtapp.html?gwt.codesvr=localhost:9997
I get
Plugin failed to connect to Development Mode server at localhost:9997
Follow the underlying troubleshooting instructions
My Chrome browser is running on the same machine as Eclipse, so localhost above should be ok. Just to make sure, I've added -bindAddress 0.0.0.0 in the Run/Debug configuration in Eclipse and tried with my external IP/hostname, with no change, except that the error message is updated accordingly. What am I doing wrong?
If I replace deployment_host with localhost above everything works fine, but it's of no use to me to debug locally. (There is some Proxy and ReverseProxy-ing going on in the local Apache, so I do not need the 8888 port when running locally, but this should be unrelated)
Questions Debugging GWT applications outside of dev mode? and Debug GWT application in a remote browser are related but do not help.
If you are using chrome, look in the address bar at the right for a grey GWT icon. In any other browser, you would see a popup message confirming that you want to debug, but in Chrome this apparently isn't possible.
Click the icon, and it will ask you to whitelist this site as allowed to run Java locally on your computer. After you whitelist it, it should run correctly.
Along the same lines as the answer above Ive just had some success restarting the extension helped (but restarting browser hadnt)
Just enable and disable it in :
chrome://chrome/extensions/
Good luck! It's the only thing wrong with GWT imho...