Hoping this is the right place to ask this. I'm trying to learn React Native and I'm using Expo as my medium for deployment, but I'm finding that I'm literally getting 20 minutes at a time before my browser fails to connect with the error code ERR_CONNECTION_FAILED. I've tried the following:
netsh winsock reset, then the related ipconfig commands for flushing DNS settings
Clearing browser caches
Updating drivers
I'm at my wits end as the only thing that completely solves it is restarting my laptop, which for obvious reasons isn't feasible every 20 minutes, so I'm hoping somebody can help.
I'm experiencing the same issue with Expo in this environment:
Windows 10, version 1909 (OS build 18363.476)
using WSL (Windows Subsystem for Linux) with Ubuntu 18.04 LTS
These links were useful to learn why this is happening:
https://github.com/expo/expo-cli/issues/99
https://github.com/microsoft/WSL/issues/2913
https://github.com/microsoft/WSL/issues/3951
In essence, this issue seems to be due to a problem with WSL. Per a post in the first link, I tried the alternative to restarting the computer and it worked - it made the ERR_CONNECTION_FAILED problems disappear...for 20 minutes. That alternative is as follows:
WIN+R -> services.msc
Find LxssManager
Right-click -> Restart
This restarts the WSL service which also means that the WSL instance that was running gets terminated. This is less than ideal, but at least a computer restart is avoided. The third link says this WSL problem is fixed in Windows Insider Build 18890.
I am now considering spinning up a VM to run Ubuntu instead of trying to use WSL for Expo projects.
I uninstalled the latest Windows updates, and the problem has not surfaced since.
Related
I'm on windows 10 and I'm encountering Docker on Windows crashing on startup.
I just installed docker on windows and have a couple of containers spinning up (last night). I've been able to use it but after reboot, or shutdown, this was the behaviour ever since. Pretty unstable.
It looks like this and terminates after a while without any prompt of an error.
More info that I have Hyper-V installed on my machine and "Use the WSL 2 based engine" option enabled on docker.
On my end, I was able to solve this by:
Going to Apps & Features
Search for Ubuntu (or any linux distro you've installed)
Click on it and navigate to Advance options
Click on Reset button.
Also, try to trial and error which docker on windows version is stable with your system.
Hope that helps.
tried looking online for the last 2 hours and I can't find an answer, tried enabling every single thing possible (Hyper-V, Virtual Machine Platform and wsl in turn windows features or off) but the problem presists.
when trying to install wsl2 from scratch I get error code 0x80070032, and when trying to upgrade wsl1 I get this:
"Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The request is not supported."
My Windows Version: 21H2 OS Build 19044
Installation from scratch
Windows 10 N Pro, version 2004
I had a few different OS VM's setup before I decided to try Docker out.
After installing it and realizing I better stick to VM's I went on my Virtualbox, tried starting my old VM's and couldn't get past the boot screen - the issue is it goes to a black screen.
I created a few new VM's all resulting in the same issue. I tried restarting the machine, Windows Restore, trying different BIOS settings, uninstalling docker, reinstalling Virtualbox, increasing VRAM to 128MB, uninstalling subsystem for Linux, disabling the Hypervisor and sandboxing. The only thing that let me interact with the VM was enabling EFI - although after choosing "boot" option I had the same black screen.
After trying all possible solutions on SO and Google I stumbled upon a comment (which unfortunately I can't find) which pinpointed that Docker installer explicitly overwrites VM/Hypoer registries or processes. I don't know if that's the issue however it is the case.
How can I get my VM's running again without reinstalling Windows?
It sounds like the problem is: 1) You were successfully running VMs with VirtualBox on Windows 10 Pro, 2) You installed Docker, 3) Docker broke VBox. Correct?
Look here:
https://superuser.com/questions/1290051/virtualbox-no-longer-works-after-uninstalling-docker-on-windows-10.
Control Panel -> Programs and Features
On the left side choose "Turn Windows features on or off
Uncheck Hyper-V
reboot
After reboot you have to reinstall/repair your installation of VirtualBox with the original installer!
Reboot again and it should work 🙂
In general, please try posting these kinds of questions on https://serverfault.com or https://superuser.com. StackOverflow is for "programming" questions.
Centos 8 ships with Wayland as its compositor and I was forced to install centos8 due to some GLIBCXX compatability issue. Everything SEEMS to work ok but there is a curious absence of all xapps and I cant get a remote X11 session going. It seems I am in Wayland hell.
Centos 8 ships with the shiny new Wayland with rumored X11 compatibility, but all I find is articles on rumors of xwayland and a host of badly named products whose names all begin with 'W' for cute.
I cant seem to install any x11, xapps or anything that would force xwayland to install as a dependency. Its amazing how easily a decision is taken to burn thousands of hours on tens of thousands of users globally.
My best google-fu has yielded nothing.
Please help. How can I get x11 (xwayland) up and running so that I can run apps from my Windows desktop as I used to with Centos 7...?
I've already encountered this "problem" and the solution I usually apply is to disable WayLand.
To do this, just edit this file with any editor (I use VI)
/etc/gdm/custom.conf
and change the line
#WaylandEnable=false
into
WaylandEnable=false
Save and close the file and restart gdm service with
systemctl restart gdm.service
I have been using Windows 7 applications within Mac iOS software for a few months (using Parallels), but recently it has stopped working. Every time I try to open a windows 7 application the application shows a broken, corrupted page that looks like static.
I have tried uninstalling and reinstalling Parallels but this has been unsuccessful.
Thank you in advance.
Also, just before this happened my computer prompted that I was running out of memory.
Restart your computer and reset PRAM by holding down
'cmd+option+p+r'
After that try opening up the application again. If the issue persists, close the windows session and allow it to use some more memory and try again.