Related
I try to enable SSH on my raspberryPi 4. I don't have screen and it's for that I created ssh file (without extansion) in D:boot. When I try to log in I get an 'Acces denied' response from ssh terminal. I try with pi id and raspberry password. I created/default new raspberry image (x64). when I take back my sd card to check, ssh file doesn't exist.
Have you any issue.
I was running into the same problem, but in this case its not a problem about SSH itself.
The real problem is RaspberryPiOS removed the default User "pi" since the lastest version (April 4th, 2022). Means you get "access denied" because there is no User named "pi". (Release notes here: https://downloads.raspberrypi.org/raspios_arm64/release_notes.txt)
To create a user you have 3 options: (use 1 out of 3)
Plug in a display and keyboard on your RasPi and follow the steps on screen to create a User.
Use the Raspberry Pi Imager tool to create a new Image on your SD-card. Under advanced settings you can set a username.
Flash the Image again and beside creating a "ssh"-file you need to create a "userconf.txt", containing a single line of text, consisting of "username:encrypted-password".
For example: (to get standard-user "pi" and password "raspberry" again.)
"pi:$6$/4.VdYgDm7RJ0qM1$FwXCeQgDKkqrOU3RIRuDSKpauAbBvP11msq9X58c8Que2l1Dwq3vdJMgiZlQSbEXGaY5esVHGBNbCxKLVNqZW1"
More information here: https://discourse.pi-hole.net/t/warning-latest-raspberry-pi-os-image-april-4th-2022/54778
Hope i could help, have a great day!
WhisperFromDarkness
What is so maddening about this is that the latest Imager (at least the macOS version) pre-populates the user name in the advanced screen with "pi", which is no longer a valid user. After about 3 attempts, it dawned on me that I had to put in a different username and password to get SSH to work. They should definitely update the Imager with a blank username.
Did you manage to solve this yet? You can solve this using the Raspberry Pi Imager application.
To begin, when referring to the fact you have no screen, I assume you mean you are running the raspberry pi 'headless', meaning controlling it through secure shell (SSH) over your local network.
If you have not already installed the raspberry pi imager application, this can be found on the official raspberry pi website. On this application, you must select the relevant SD Card and operating system, before pressing CTRL+SHIFT+X, which will take you to the advanced settings page. Here, select 'enable SSH', before entering your WIFI SSID and password.
Once you have completed these steps and re-entered the SD card into the raspberry pi, you may open the terminal and enter 'SSH pi#ipaddress', followed by the password you created during setup, or the default password, which I believe is simply 'pi'. You will now have access to the Pi through SSH. Enter the command
sudo raspi-config
and you may alter the configuration settings as you like. Here, you may wish to change the VNC settings, so that you can view your raspberry pi GUI through remote desktop SSH.
I hope this was relevant and solved your query.
I've got virtual box installed. And when I look at the host > LAN > ip address is exp://192.168.56.1:19000.
How can I change it without disable the network? because it's my virtualbox ip and my device can't connect to it.
Thanks
You can specify the REACT_NATIVE_PACKAGER_HOSTNAME environment variable to use the correct IP address.
If you're using XDE, then make sure to launch it from your project directory with xde . after you've installed the command line tools.
In windows you can use:
set REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.59
set is only used for one session. If you always wanna use the same ip after reboot you can use:
setx /M REACT_NATIVE_PACKAGER_HOSTNAME 192.168.1.59
Even after you set the custom ip, you still cannot connect the virtual box.
You need to set a port forward for the virtual mechine at networking setting page.
Just use the real host mechine ip for the app Expo.
REACT_NATIVE_PACKAGER_HOSTNAME='real host mechine ip' npm start
check your pc whether install virtualbox , disable VirtualBox Host-Only Network
go to win pc: Control Panel\Network and Internet\Network Connections
run again command expo start is ok
Open CMD from your Project Directory and Run Command as set REACT_NATIVE_PACKAGER_HOSTNAME=192.168.0.12. Replace the ip with your own LAN ip address.
The Command set is used to set the Environment variable locally, without defining it into Environment Variables.
I have similar kind of problem (with may a slight difference), but the solution doesn't work for me. Finally I tried Expo CLI tool which worked great for me and is also recommended by Expo team.
My detailed question (may help someone to resolve similar problem):
Expo LAN configuration doesn't work for New ReactNative Project
On the Windows Subsystem for Linux (Ubuntu 18.04.1 LTS "Bionic"), I had to use the export command:
export REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.76.
If you have "ubuntu in windows" configured you can automate the process and run:
for /F "usebackq delims=" %A in (`ipconfig ^| grep -A4 'Wireless LAN adapter WiFi' ^| tail -1 ^| awk '{print $NF}'`) do set REACT_NATIVE_PACKAGER_HOSTNAME=%A
My problem solved by reinstall expo client on ios simulator.
I was used expo v37 before but got this problem on v38, the problem was expo client not have expo sdk 38.
Sharing my experience using EXPO with Cloud 9 and AWS Amplify. Similar with you, the QR code gives exp://localhost:19000
As the Security Group has been configured to provide public access, I regenerate the QR code to have it accessible from public IP address of exp://X.X.X.X:19000, this can be scanned from IOS devices to EXPO.
REACT_NATIVE_PACKAGER_HOSTNAME environment variable is ment for react DevTools.
For EXPO, you have to set EXPO_DEVTOOLS_LISTEN_ADDRESS environment variable.
Here is the weird function that determines the hostname :
function devtoolsGraphQLHost() {
if (process.env.EXPO_DEVTOOLS_LISTEN_ADDRESS && process.env.REACT_NATIVE_PACKAGER_HOSTNAME) {
return process.env.REACT_NATIVE_PACKAGER_HOSTNAME.trim();
}
else if (process.env.EXPO_DEVTOOLS_LISTEN_ADDRESS) {
return process.env.EXPO_DEVTOOLS_LISTEN_ADDRESS;
}
return 'localhost';
}
If you're still having this problem, try switching to tunnel connection. It'll install #expo/ngrok# and then you can scan the qRcode. Its what I did and the connection worked without having to change the IP address
click 'npm start', open the browser where your application is running, and on the bottom left corner, you will find the QR code.
Above the QR code, three options are displayed saying 'Connection: Tunnel | LAN | Local' which is defaulted to 'LAN'. Just change it to 'Local'.
Your application will be up and running.
For me, something completely different worked under Windows.
My pc has multiple network interfaces and the LAN URL points to a different one than that the mobile device can connect to.
This was quickly solved by deactivating all unnecessary network adapters.
(Setting the REACT_NATIVE_PACKAGER_HOSTNAME environment variable did not work for me.)
And of course I was on the private network and had disabled the firewall for it until I configured it.
Alternatively, to avoid having to deactivate a network adapter, you can also adjust the metrics or priority of the adapters like this:
goto Control Panel > Network and Internet > Network Connections
right click the desired connection (Higher Priority Connection)
click Properties > Internet Protocol Version 4
click Properties > Advanced
Uncheck 'Automatic Metric
enter 10 in 'Interface Metric
Click OK
I am trying to run create-react-native-app on expo app in android.
Firstly ,I created the project by writing command
create-react-native-app test
then I executed
npm start
then scanned the qr code from expo app.
But after scanning QR code , I am getting following error:
Uncaught Error: Java.net,sockettimeoutException: failed to connect to after 10000ms
Github Issue:
https://github.com/react-community/create-react-native-app/issues/144#issuecomment-296631692
This is due to not open port from your machine.
Linux (Ubuntu)
In Ubuntu Run In terminal
sudo ufw status verbose
To view open port if you cannot found 19000 port open then you need to open port using
sudo ufw allow 19000/tcp
and then again run
sudo ufw allow 19001/tcp
to serve http for react native i solve this problem in my ubuntu using this method. I hope this will help you.
Windows
To open a port in the Windows firewall for TCP access
On the Start menu, click Run, type WF.msc, and then click OK.
In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.
In the Rule Type dialog box, select Port, and then click Next.
In the Protocol and Ports dialog box, select TCP. Select Specific local ports, and then type the port number of the instance of the React port, such as 19000 for the default instance. Click Next.
In the Action dialog box, select Allow the connection, and then click Next.
In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.
In the Name dialog box, type a name and description for this rule, and then click Finish.
Similarly you can open port 19001 too.
Change connection from LAN to tunnel.
In my case the firewall settings alone didn't do it. My issue was that VirtualBox network devices were taking priority and the Expo host was starting on the wrong network.
On windows you can run ipconfig and look at the network adapters you have. npm/yarn start seems to take whatever shows up first in that list.
I found out about this from here: https://github.com/react-community/create-react-native-app/issues/60
If you don't need the other network adapters in the list, you can disable them in the Network Connections interface of the Control Panel.
If you need to use those connections and have Expo work then to solve the issue I followed this process:
Goto Control Panel > Network and Internet > Network Connections
Right click the desired connection (Higher Priority Connection)
Click Properties > Internet Protocol Version 4
Click Properties > Advanced
Uncheck 'Automatic Metric'
Enter 10 in 'Interface Metric'
Click OK
Repeat for the Lower Priority Connection, but this time put 20 into the 'Interface Metric'
You'll now use the higher priority connection as a default.
You can get around that by fixing your laptop's ip address to a static ip, let's say 192.168.1.69, then you need to change the react native packager ip address to the same of your laptop, using
set REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.69 (Windows)
REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.69 (Mac & Linux)
start your project again and you're good to go.
I had done everything mentioned in context.
Just Changed my connected WiFi network from public to private.
This Worked for me
First of all, disable the unused network connection. In my case it was VirtualBox. Maybe it's using the same port. I am not sure about that. after disabling the unused connections then restart the packager. if you used npm then type
npm start
Found ipv4 address
open expo app then tap to explore button from bottom
write exp://[ipv4adress]:19000 to searchbar
Then your app will open
I suggest you install expo application for react native, link to official guide here
npm install -g exp
Then you can use Genymotion software to emulate different environment setting for your app an run:
exp start
If you use in the terminal "npm start" with native react, the following is for you.
I found out that if my application runs successfully IpV addresses of my computer, that are shown in the terminal and that is on Expo app are identical, for example:
ipconfig -> IPv4 Address. . . . . . . . . . . : 10.0.0.124
exp://10.0.0.124:19000
Based on this observation I solved this issue by the following way:
Close npm prompt script which is running app
Close Expo app
Find your IP by running command in the terminal:
ipconfig
Run command in NodeJS command prompt with your IP (for example 10.0.0.124)
set REACT_NATIVE_PACKAGER_HOSTNAME=10.0.0.124
Start Expo app, scan barcode
npm start
If it does not help, then use next steps recommended by React developers in addition to other reasonable efforts:
Install Genymotion with VirtualBox
SignUp at Genymotion site
Run Genymotion software and !!!SignIn
If you are using git bash for development then this solution by Icruz4 will help
Instead of
set REACT_NATIVE_PACKAGER_HOSTNAME
Use:
export REACT_NATIVE_PACKAGER_HOSTNAME='192.168.1.123'
Note:
When you run
npm start
Expo tells you in the output the IP it's using. If that IP is not the IP you want then the
REACT_NATIVE_PACKAGER_HOSTNAME
environment variable is not set properly
in Windows
run the ipconfig in command prompt
get the ip4 address and copy it.
Than go to
This PC > properties > advanced system settings > environment variables
add the following system variable: REACT_NATIVE_PACKAGER_HOSTNAME
As the value for the variable I had to paste the ip4.
then run the npm start
It's work for me
I've had the same issue. The problem is that the command yarn start or npm start finds the first enabled network adapter it finds which just happens to be the adapter for VirtualBox on my (and many other machines). The solution is to either:
manually set REACT_NATIVE_PACKAGER_HOSTNAME environment variable, or
disable the unused network adapter in Windows' Network Connection (see image)
The problem is that Expo finds the first Network adapter, and not the active network adapter that provides the internet connection.
change LAN to Tunnel to solve this issue
In case someone is still looking for the answer. Do the basic thing first, Disable the VirtualBox Host-Only Network first by opening your network configs. This worked for me.
If you have tried everything the other answers suggest and it still does not work, please also check that your computer and your phone are connected to the same WIFI network. For me this is what wasted an hour.
This issue could possibly be resolved by:
Setting your environment variable with alternative instructions here
Or
Assigning interface matrix priority for your network adapters with detailed instructions here or here.
Or
An Ubuntu machine is unable to open a port
After you make any changes, please restart the computer before testing if it works.
Good luck!
I tried many solutions, only this way helped me to solve this problem:
In Windows:
go to "Network and Connections" in Control Panel of windows (Network and Sharing Center>Change Adapter Setting)
Disable all virtual boxes which you can see here
Restart npm or yarn or expo...
In my case, this problem occurred because Expo android app need "draw over other apps" permission and I didn't give it. So I give this permission to Expo app and the problem solved..
One of the simplest and 100% working solutions is:
Enable the Mobile Hotspot of your development machine( PC or Desktop ) and connect your Android device with this hotspot.
Goto Control Panel > Network and Internet > Network Connections
You will land in here as shown:Network Connections setting
Then set the IP address of Local Area Connection(Your DESKTOP HOTSPOT) to a desired one, say: 192.168.1.69 by right-clicking on the concerned connection and then clicking on properties -> Internet Protocol Version 4(TCP/IPv4) -> Properties. Then set the priority of this connection to be the highest and this is best described here
Then open a command terminal and run:
set REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.69 (Windows)
REACT_NATIVE_PACKAGER_HOSTNAME=192.168.1.69 (Mac & Linux)
Then restart your expo server by running npm start in your expo project folder and run the app on your Android device by scanning the generated QR code with the expo app.
This error beaus your port it is not open
just check port is open or not for ubuntu you can check using the following way
sudo ufw status verbose
check 19000 port open then you need it
then run following command if port not open
sudo ufw allow 19000/tcp
for other port runs following command
sudo ufw allow 19001/tcp
because http port not you are getting erro. above step solve your problem
similar for mac and windows check firewall setting once
Solution 1:- Connect both(your PC and mobile)with same network then scan the QR with expo application.
Solution 2:-Select / change connection type as Tunnel mention in local host development window of your browser then scan the QR with expo application.
I think this will help :)
I had the same issue I got this when I cancel the permission window of node js I solved it by going at the directory
On the Start menu, click Run, type WF.msc, and then click OK.
In the Windows Firewall and Advanced Security, in the left panel in Inbound Rules I had two options or rules disabled Node.js Serverside Javascript.
I simply double click and in new window In action, I select allow the connection and save
I had the same issue but after some research, I found that this is because your computer has previously connected to multiple adapters. Expo may pick the IP address of one of these. To avoid this
Go to the command prompt and write 'ipconfig'.
Copy the IPv4 Address under Wireless LAN adapter Wi-Fi.
Then wrte the below command.
set REACT_NATIVE_PACKAGER_HOSTNAME=(Your IP here)
i just want to remember this for those who only try to scan the QR Code
You need to connect your phone to your computer using a USB cable the first time you want to launch the app,that will install the app on your device then the expo scan will work, i think all the solution above will work maybe it's just because you didn't connect them first that everything didn't work
just read the docs
https://reactnative.dev/docs/running-on-device
I got it by using this command on my ubuntu system:
sudo ufw allow 19000/tcp
and then type this:
sudo ufw allow 19001/tcp
restart vscode and the expo server and then you are good to go!
For Linux Ubuntu 21.10
This is for users, that don't use UFW.
Make sure ufw is inactive, else, execute 'sudo ufw allow 19000'
sudo ufw status
List rules:
sudo iptables -L
This will output on clean Ubuntu like this:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Now allow port 19000 with command:
sudo iptables -A INPUT -p tcp --dport 19000 -j ACCEPT
Make sure that rule added:
sudo iptables -L
Expected output:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpt:19000
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
After restart all rules will be wiped, so we need to install package, that will add rules from a file rules.v4 on each OS boot
sudo apt install iptables-persistent
su root
iptables-save > /etc/iptables/rules.v4
Enjoy! :)
If you are on Mac OS, this fixed it for me:
System Preferences > Network > Wifi
Uncheck "Limit IP Address Tracking".
This might have to do with iCloud Private Relay blocking your Mac from being seen by other devices.
In Windows,
set REACT_NATIVE_PACKAGER_HOSTNAME=my-ip-address
worked inside my git bash terminal, but not cmd. In git bash, after I ran npm start, I got a firewall popup, which I clicked allow and it worked!
In your device: Log in to your expo app, create account if you doesn't have any.
In you system: open terminal go to you project directory via cd command and then type sudo exp start
it will ask you your expo account login details once you done with this.
It will gives you qr code to scan.
You Just need to open the port in Window Firewall and everything should work.
1.On the Start menu, click Run, type WF.msc, and then click OK.
In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.
In the Rule Type dialog box, select Port, and then click Next.
In the Protocol and Ports dialog box, select TCP. Select Specific local ports, and then type the port number of the instance of the React port, such as 19000 for the default instance. Click Next.
In the Action dialog box, select Allow the connection, and then click Next.
In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.
In the Name dialog box, type a name and description for this rule, and then click Finish.
Similarly you can open port 19001 too.
If you have tried everything, and still not working for you. Change the Connection to 'Local' instead of 'LAN', it is working perfectly for me. It is not the best solution but does the work.
I have installed the Windows 10 Insider Program. Everything works, except Apache. When I try to start it, it says that port 80 is blocked. Is there a way to unblock it or tell Apache to use another port instead?
I was using Windows 7 before. I had trouble with port 80 with skype, but i have disabled it.
I had the same problem on windows 10, IIS/10.0 was using port 80
To solve that:
find service "W3SVC"
disable it, or set it to "manual"
French name is: "Service de publication World Wide Web"
English name is: "World Wide Web Publishing Service"
german name is: "WWW-Publishingdienst" – thanks #fiffy
Polish name is: "Usługa publikowania w sieci WWW" - thanks #KrzysDan
Russian name is "Служба веб-публикаций" – thanks #Kreozot
Italian name is "Servizio Pubblicazione sul Web" – thanks #Claudio-Venturini
Español name is "Servicio de publicación World Wide Web" - thanks #Daniel-Santarriaga
Portuguese (Brazil) name is "Serviço de publicação da World Wide Web" - thanks #thiago-born
Alternatives :
Another solution is to shutodwn the service via an admin console with command sc stop W3SVC
see community wiki from Tobias Hochgürtel Apache Server (xampp) doesn't run on Windows 10 (Port 80)
Edit 07 oct 2015: For more details, see Matthew Stumphy's answer Apache Server (xampp) doesn't run on Windows 10 (Port 80)
This answer is intended as an addendum to the highest rated answer on this thread by paaacman. I just wanted to add some helpful detail for users like myself who don't know their way around Windows 10 as well.
Windows 10 runs IIS (Internet Information Services, Microsoft's web server software) automatically during Startup on Port 80. In order to use Apache Server on that port, IIS must be stopped.
paaacman's response refers to the IIS server as "W3SVC", or the "World Wide Web Publishing Service". I suppose that's because Windows 10 runs IIS as a service. In order to disable it or modify how the service runs, you need to know where to find "Services" in your system.
I found the easiest way there was to click on the search button next to the start menu button in the Windows 10 taskbar and type "Administrative Tools". You can either hit return or click on the "Administrative Tools" link that Windows finds for you.
A control panel window will open with a list of tools. The one you want is "Services." Double-click it.
Another window will open called "Services." Locate the one named "World Wide Web Publishing Service." Some other users in this thread have listed what it is called in other languages, if your list is not in English.
If you only want to turn off the IIS server for this Windows session, but want it to run automatically again the next time you start up Windows, right-click "World Wide Web Publishing Service" and choose "Stop." The server will stop, and Port 80 will be freed up for Apache (or whatever else you want to use it for).
If you want to prevent the IIS server from running automatically when you start up Windows in the future, right-click "World Wide Web Publishing Serivce" and select "Properties." In the window that appears, locate the "Startup type" dropdown, and set it "Manual." Click "Apply" or "OK" to save your changes. You should be all set.
With Windows 10 IIS runs on Port 80 by default which can be changed:
Run appwiz.cpl use Turn Windows features on or off and install the IIS Manager Console.
Run InetMgr.exe and go to "Connections -> Sites" and open with right-mouse click the context menu on the default entry "Default Website". In Context Menu select "Bindings" to open the Server address and port configuration.
https://technet.microsoft.com/library/hh831681.aspx#Site_Bingings
I had the exact same problem and solved it running the folowing command from the command line as an admin :
1) first stop the service with the following
net stop http /y
2) then disable the startup (optional)
sc config http start= disabled
Type in command line
netstat -aon | findstr :80
You'll see PID of process which uses port 80.
Then try to configure this app to use another port, or just kill it
UPDATE:
I'll write my comment here to be more clear: according to this link, in Windows 10, it is the MsDepSvc service which occupies port 80. It's for IIS or Web Matrix 2. If you will not use IIS or Web Matrix 2 for any web development, you can try shutting down the service
And for the second part of your question, you can tell Apache to use another port by editing [Apache folder]/conf/httpd.conf. It has "Listen 80" string. Change 80 to whatever free port you want and reload Apache
You may need to terminate SQL Server Reporting Services as well.
In my case I need both XAMPP for Apache development & IIS Express for .Net 2013 development; so I do the following:
In Command Prompt typed services.msc, this loads "Windows Services" where I located "World Wide Web Publishing Service" and stop it.
World Wide Web Publishing Service STOP
The I start XAMPP Control Panel click on "Config", then choose "Apache httpd.conf". Search for "80" then change that to "8080" in both "Listen 80" and "ServerName localhost:80". Save the file from "Save As" & choose "All files" to not save it as text from "Save As Type" & the "Encoding" should be "UTF-8".
Apache httpd.conf
Quit XAMPP Control Panel, then start it again and from "Action" start Apache & MySQL. Now you will see the port changed. As you know now you have to get to your Apache server by using "localhost:8080" instead of "localhost". Also you have both Apache & IIS Express running in the same Windows 10 PC.
I read a post some where were the writer suggested to use port "9080" but it did not work for me.
The problem happens whenever a process uses port 80.
You can run Netstat which is available in XAMPP Control Panel and check which process uses port 80 in your system.
For me it wasn't IIS, but Skype.
Turn off that process/application and then start the Apache services.
I know that maybe this problem was resolved but I had the same problem with different solution. For that, I am going to explain another possible solution. In my case, the port 80 was occupied by Skype (pid: 25252) and I did not know what programme was.
To see the program's pid which is using the port 80 you can use the command that other people said before:
netstat -aon | findstr 0.0:80
To kill the process using the pid (in the case that you do not know the programme) you have to open the CMD with administrator permission and use the next command:
taskkill /pid 25252
Other options with this command are here.
I think it simple to change your Apache server port
Go to C:\xampplite\apache\conf
Open httpd.conf files
Search for Listen 80
Change 80 to any other like 9080
Now XAMPP restart try to start server
NB I am using Server version: 5.1.41 with windows 10
I know this MIGHT not be the cause of your issue, but I've spent a few hours hitting my head against the wall to solve this issue and this is my solution.
(running Windows 10 x32)
So I had installed XAMPP in a deeply nested directory and all the conf files make reference to root\xampp\apache, whereas my files were some_dir\another_dir\whatthehelliswrongwithme\finally\xampp\apache
so my options were to either go through and edit all \xampp\apache references and point them at the right place, OR, the much simpler option... reinstall XAMPP at the root, so the references all point to the right place.
A little annoying, but I guess that's what we get when Mac and Windows try to be friends..
Hope it helps a few of you.
In case you need to run IIS on port 80/443 but on different IP address, you may use netsh http add iplisten xxx.xxx.xxx.xxx as described here:
https://support.microsoft.com/en-us/help/954874/iis-binds-to-all-ip-addresses-on-a-server-when-you-install-iis-7-0-on
More details about netsh http add iplisten can be found here:
https://msdn.microsoft.com/en-us/library/windows/desktop/cc307219.aspx
Shutting down "some system process" may be tricky... you should rather edit the [Apache folder]/conf/httpd.conf as mentioned by #Sergey Maksimenko and if you want to configure virtual host, use the new port in [Apache folder]/conf/extra/httpd-vhosts.conf (I used 4900 instead of 80 and 4901 instead of 443 in [Apache folder]/conf/httpd-ssl.conf). And remember to use the port when accessing page on localhost (or your virtualhost), for example: localhost:4900/index.html
This fixed node.js not running on port 80 under Windows 10 as well, I was getting a listen eacces error. Start > Services, find "World Wide Web Publish Service" and disable it, exactly as paaacman described.
I had the same issue and none of the above solutions worked for me.
Apache uses both ports 80 and 443 (for HTTPS) and both must be ready to be used for Apache to start successfully. Only port 80 might not be enough.
I found in my case that when running VMWare Workstation I had the port 443 used by the VMware sharing.
You have to disable sharing in the VMware main Preferences or change the port in this section.
After that as long as you have no other server hooked to the port 80 (see above solutions) then you should be able to start Apache or NGinx on XAMPP or any other Windows stack application.
I hope this will help other users.
While many are taking the approach to stop/disable IIS, it may be helpful to know that you can simply modify the XAMPP port, which has been answered here. This is the route I had to take as I need both running.
Beside the quite obvious reason (IIS), there is another reason that is common enough for this problem. It is worth to quote this question and its answer here:
http://stackoverflow.com/questions/22994888/why-skype-using-http-or-https-ports-80-and-443
So, if you have Skype installed in the computer, be sure to check this as well. The solution is quoted here:
To turn off and disable Skype usage of and listening on port 80 and port 443, open the Skype window, then click on Tools menu and select Options. Click on Advanced tab, and go to Connection sub-tab. Untick or uncheck the check box for Use port 80 and 443 as an alternatives for incoming connections option. Click on Save button and then restart Skype to make the change effective.
First, open regedit run as administrator
see image
open HKEY_LOCAL_MACHINE\SYSTEM\CurrentCurrentControlSet\Services\HTTP
open Start, change value from 3 to 4
see image
then restart your computer
I am looking for a tool that will allow me to monitor and control programs running inside a Windows VM from the Linux host machine. I realize that this is similar to what a rootkit would do, and I am completely happy to use some hacker software if it provides the necessary functionality (and if I can get it in source-code form).
If I can't find something, I'll have to write it using C. Probably an embedded HTTP server running on an odd port and doing some kind of XMLRPC thing.
Here is the basic functionality I need:
Get list of running processes
Kill a process.
Start a process
Read/write/create/delete files
I would like to:
- Read contents of screen
- Read all controls on screen.
- Send arbitrary click to a Windows control.
Does anything like this exist?
Build Samba with WMI support from http://dev.zenoss.org/svn/trunk/inst/externallibs/wmi-1.2.9.tar.bz2. Not in the official Samba yet.
Get list of running processes
wmic -UAdministrator //host "select * from Win32_Process"
Kill a process
You need to run wmic on the Windows host using winexe because Samba wmic only supports querying
winexe -UAdministrator //host "wmic process where name=\"process.exe\" delete" # Kill process.exe
winexe -UAdministrator //host "wmic process where ProcessId=145 delete" # Kill pid 145
Start a process
winexe -UAdministrator //host process.exe
Read/write/create/delete files
You probably want to use Samba read man mount.cifs and man smbclient