I am connecting to my VM using the ssh-in-browse
After few minutes of work it becomes VERY slow, waiting few seconds for each keyboard press to return
working with latest version of Chrome
disabled all extension
using the default connection
Related
I currently have 5 EC2 Virtual Machines, each of which has a chrome browser installed and 40 browser profiles.
Chrome updates itself every few hours, even though I have tried several different options to get it to stop.
I have tried disabling the auto update feature using a group policy edit, then restarting the virtual machine. It seems to go without update for a short period of time (a few hours), then updates.
I have disabled Google Update Services as well as Gogle Chrome Elevation Service. None of this has worked.
I would like to prevent Google Chrome from updating indefinitely.
I have an RPi2 iot-core app which has run fine for months on the previous iot-core os release. I access it regularly via the iot-hub and it writes to Azure blobs ... until the automatic update last week to version 10.0.14393.67 at which time my UWP-headless-app, although still running (I see this in my reference version via the local device portal app), no longer communicates with iot-hub or azure.
Any ideas what going on and what can I do without having to start from scratch?
PHPStorm 9 is being hit by non-stop Xdebug requests when I do not have the listener enabled in PHPStorm and I don't have it enabled in the browser Chrome extension.
These windows constantly pop-up disrupting my ability to use the IDE:
This started after I had to disable xdebug.remote_autostart setting due to conflicts causing PHP scripts run at the CLI level to hang.
Now every background queue that executes is triggering this incoming connection message.
Every time I delete the server *.dev from PHPStorm it shows back up again.
How do I stop this?
Below is the full value list from the Debugger console when these undesired requests come in:
I am facing an issue with windows 8 phone emulator.
Windows Phone emulator wasnt able to connect to Windows Phone
operating system. Phone didnt respond to connect request
This is the error that I get. When the emulator starts with internet but my application doesnot deploy. The ip that gets assigned is 192.168.137.1. Previously it worked fine,
but then suddenly it started giving this issue.
Below is the list of troubleshooting that I have performed:
169.254.xxx.xxx address set to internal emulator via dhcp, Application deployed successfully with NO internet connection
Have tried MAC address spoofing but nothing works when I use these settings.
Have changed External Virtual Switch in Sharing mode this starts the internet with ip 192.168.137.1 but application doesnot deploy
In debugger errors shown are:
Invalid pointer error
App deployment failed
Have tried Network bridging but still it doesnt work.
Created all settings manually including the internal switch and external swithch. But same issue faced when it gets 192.168.137.1 ip then internet works but application doesnt deploy.
And when it gets 169.254.xxx.xxx ip series application deploys but no internet connection.
No firewall are turned on or no antivirus is blocking any connections.
Wireless router used for network connectivity, still not successfully
Have also tried clean installation of everything but still no go.
Need help with this issue as I have been trying to get it resolved since a week.
This issue is not faced if installation is done on the same pc through a virtual machine.
What I did was :
Have allotted 4gb ram, 60gb hdd & 4 cores to the VM.
1)I installed a virtual machine with default settings.
2)Then I stopped your virtual machine (shut Windows 8 down, DO NOT suspend it).
3)At the VMWare Virtual Machine list, right click Windows 8 machine then click "Show in Finder".
4)Right click the file then click "Show package contents", then find and open with a text editor a file with the extension .vmx
5)Go till the end of the file and add this two lines (first check whether they were previously added):
hypervisor.cpuid.v0 = "FALSE"
vhv.enable = "TRUE"
6)At the VMWare Virtual Machine list, right click Windows 8, click "Preferences" then "Advanced". Choose "Intel VT-X with EPT" as "Preferred virtualization engine".
And then when I started the windows in the virtual machine it seems to be working fine without any additional setting change. However it is still not running on a physical machine
I recommend if someone is facing a similar issue then to use a Virtual Machine till this kind of issue is resolved.
Struggling with the same problem for 3 days I finally solved my issue by disabling windows firewall for "Guest or public network". I have yet to figure out what application/service to allow through so I can re-enable it.
I've installed lemmingzshadow / php-websocket on my Win7 machine, which was pretty simple to do:
unzipped the content into my htdocs folder.
executed server.php from command line.
requested the file /client/status.html from a browser that supports Websockets.
Now here's what I get on the local machine running Google Chrome 19 / Windows 7
click to enlarge
It says "connected" for 30 seconds (displaying no info from the server) then says "disconnected", and here's the related command line output:
Exact same issue when accessing the script through LAN from another computer with Firefox 12 / WinXP
click to enlarge
It only seems to work when accessing it from my VirtualBox Ubuntu, using either Firefox 7.0.1 or Chromium
click to enlarge
It's been days since I've trying to figure out why this is happening, tried other Websocket scripts and they only work when I access them from Ubuntu. I even installed this same script on Ubuntu / XAMPP and was still stuck with the same issue (script running fine on Ubuntu but not on the other operating systems).
I'm going crazy over this, any idea why it's happening??
In that code (lemmingzshadow), the default behavior is for the server to mask the data it sends to the client:
Connection.php:
public function send($payload, $type = 'text', $masked = true)
For some reason this will work in Chrome 18, but it is against the latest websocket spec and does not work in Chrome 19.
RFC 6455 Sec 5.1:
A server MUST NOT mask any frames that it sends to
the client. A client MUST close a connection if it detects a masked
frame.