VertrigoServ Apache HTTP Server Port 80 Already In Use - apache

I have recently installed VertrigoServ, with the Apache HTTP Server, expecting to work perfectly like other installations. Unfortunately, this time it has not. Apache says the port 80 is already in use; I have tried all the methods suggested in other forums, but there seems to be no service, program or process using port 80.
Any ideas?

yes skype do clash with vertrigo just exit skype in tray icon and restart vertrigo you will be good to go.

Vertrigo / Settings / Program Settings / Unckeck "Run servers as services", then restart your PC and start vertrigo again

In my case case icon was yellow in Vertrigo because of running
Web Deployment Agent Service
which came probably with Microsoft WebMatrix, it is also run and probably installed by Microsoft Visual Community for example.
Changing Start type of this Service from Automatic to Manual is good solution ? Here:
http://www.sitepoint.com/unblock-port-80-on-windows-run-apache/
is such advice. Today it was turned off using simply Task Manager, but maybe this too brutal way.
The Run servers as services in Vertrigo is unchecked, but Web Deployment Agent Service was blocking Vertrigo.
Microsoft Matrix can run php too.

Try to change the port that Vertrigo uses to run php pages. It worked for me, I did like this (changed to 8080):
https://sourceforge.net/p/vertrigo/discussion/2083479/thread/e8546bc9/

Related

IIS can only support three instances of a Blazor server client?

I've download Visual Studio 2022 and tested the default Blazor Server template (Home/Counter/FetchData). In Visual Studio, IIS Express I can open as many tabs / instances of the application as I want.
When I host the default Blazor Server template in local IIS (Windows 10 Home 21H2, IIS 10) I can only open three instance of the application. The fourth will hang until the first is closed. I see someone has ran into nearly the exact same issue but there is no solution provided.
Anyone know whats going on? I don't understand why IIS Express can handle multiple instnaces but IIS 10 can not. Even Conveyor by Keyoti can support many many tabs compared to IIS 10.
Note: I notice SignalR has limitations on Windows / IIS of 10 concurrent connections, but I'm not even getting two.
Updates
Out of curiosity I tested it on Windows Server 2016 Standard and I can open hundreds of tabs.
I re-installed IIS on Windows 10 to make sure something wasn't wacky.
I've ensured WebSocket Protocol is enabled.
Windows 10 Home supports 3 concurrent connections at the same time, according to Microsoft.
Normal HTTP requests to IIS get process and response returned. So even if you manage to achieve 4 or more at the same time, IIS will work through the request queue and you may not have noticed that your request was slightly delayed unless your individual requests take a while to process.
However with SignalR, a persistent connection is maintained to the server. So if you open one connection per browser tab, and you have 4 tabs open, that 4th tab is going to hang indefinitely until one of the other page has its connection ended (by closing the tab, manually disconnecting via code, or refreshing the page).
I can't reproduce the issue, and I have tried to search some way to solve it.I will summarize a few ways below that you can try.
Try to install Websocket Protocol in your Win10. You can find it in Windows features.
Workaround: install IIS Express in Web Platform Installer.
Workaround: Try to deploy it in windows server, and check whether have same issue. I found some posts also mentioned it may related with OS version.
The solution was incredibly simple (maybe too simple?). Don't use IIS at all.
In Program.cs just before building the app I override Kestrel ports to listen on any ip (for now).
(Optional) I provide a custom SSL certificate in the UseHttps constructor so that it can be emailed and installed on iOS and Android devices.
(Required) Then I publish the applications to a folder and just run the .exe on the hosting machines.
Program.cs
builder.WebHost.ConfigureKestrel(opt =>
{
opt.ListenAnyIP(8000);
opt.ListenAnyIP(8001, listOpt =>
{
listOpt.UseHttps(#"Path to.pfx file", "password for pfx file");
});
});
Now Windows 10 Home can support as many connections as the hardware can handle at https://192.168.0.XXX:8001. Is this how Blazor Server is expected to be deployed within a local network? I don't understand how this overcomes the connection limit pointed out in masons answer. Please let me know in the comments if I'm missing something.

Wamp is not working after Windows 10 upgrade

WampServer worked fine on my computer running Windows 8.1. I've upgraded to Windows 10, and now Wamp is not working. The WAMP icon is red. I've looked into the Internet Information Services and found that World Wide Web Services folder was unchecked. I went to services.msc and the World Wide Web Publishing Service is missing from the list. Took off skype from port80. I've tried changing the port address in httpd.conf to 8090 and 9080. I tested port80 through WAMP - Apache interface and found out that "Your port 80 is not actually used". I'm not very good at using the command prompt. I don't know how to ensure that Apache uses port 80. I'm asking if this the problem and how to fix it. Or at least how to get WAMP working again. Thanks!
If you had WAMPServer installed before you upgraded to Windows 10 then the solution is simple. The problem is that the W10 upgrade does not know about the Apache and MYSQL (wampmysqld and wampapache) services, and therefore does not re-register them.
All you have to do is this using the wampmanager menus
wampmanager -> MYSQL -> Service -> Install Service
wampmanager -> Apache -> Service -> Install Service
Its probably a good idea to the exit WAMPServer and then restart it, but not usually necessary.
I tried several ways to make it run but it didn't. Suddenly, I selected a different version of PHP from WAMP tray and it did the trick. May be it will help many out there facing this issue.

Wamp Server Working But Still Orange

No, this is not a duplicate question!
Wamp Server doesn't start on system boot up.
When I turn it on, it is in Orange but it works just fine and Test Port 80 says that it is used by Server: Apache and PHP.
I have to Ctrl+Alt+Del < Task Manager < (2) Apache Httpd Servers
Then end both tasks.
Then Restart All Services and Wamp will be green!
My questions are
1. if it works then why is it in orange?
2. can I make it start on system start?
Note: MySQL Server is working properly at all time.
I don't have Skype installed and I don't think the problem is with the ports...
I have already tried uninstalling then re-installing but that didn't fix the problem.
EDIT:
According to the solution #RiggsFolly suggested, I can see that Apache is not starting properly; however, weirdly the web app can be run normally...
you can also change the port as well. yes you can start wamp service on system start by setting in start up program MSConfig can be used to configure several things other than just startup programs.

Can't access to wamp/xampp apache localhost:80 WINDOWS 10

I recently upgrade my Windows 7 to Windows 10 (9). I need to use Apache server for web development. But for some reason I can't access it via web browser.
First I tried to look in the firewall and antivirus settings. It looks fine. I've tried reinstall xampp then I tried Wamp. Nothing working. I'tried 3 web browsers Edge, Opera, Chrome. Then I tried to find if some application is blocking port 80. So I disabled Skype, IIS. Then I tried different ports 8080,9080,123. Still can't access it via browser, but ping works.
Then I disable preference of Ipv6 and I prefer IPV4 now. I've changed HOSTS file so only 127.0.0.1 localhost is uncommented.
Only problem occurs when I try run wamp my internet access became unavailible and a have to restart computer to access internet again.
Has anyone here have same problem, because according to everything I ve done it seems apache server and network settings is correct.
Maybe problem is somewhere else?
Thank you for your help.
Solved with clean Windows 10 installation.

Server port 9081 is in use, starting Websphere Application Server in RAD

very quick question regarding an issue I never seen before. I've being using RAD 6 for java development, with Websphere portal server 5.0 installed. When I trying to start the server, I get the following error in a popup:
Which none of what's described is the true in my case...and still the case even though I rebooted the PC, as well as checking for any redundant javaw.exe processes.
Thanks for you help
I asked a colleague, they suggested that you have a server set up which is defined to run as a service. Since the service will start automatically with Windows, rebooting won't help.
Check your services.msc and see if there's a service for WebSphere, then try stopping it and starting your server from within RAD.
Do one thing, if it's possible. Just go to running programs and check for any java.exe and stop/delete all of them. And try restarting your server. And check if it makes any sense.
Hope it helps.
//HP
Start command prompt (if you're on Windows Vista and up, ensure you start it in admin mode).
Type:
netstat -a -b
This will show you all ports being listened. Look for 9081, and then you'll be able to see the process that is capturing that port.
Which process was it?
An easiest way to do so is kill the jawa/javaw process from the taskmanager.
And then start the server.