VS code Live Server Web Extension server port 8080 problem - visual-studio-code

I am using vs code as a code editor for PHP. To view live time update I use vs code live server extension for chrome. Using Xampp(apache) for the PHP server. But suddenly I notice that some apps blocked my port 80 of windows 10 so I change the port for apache as 8080. Then my live server stopped working.
Can anyone tell me why this happened?
I want to add that if I change other ports like 8000 it works perfectly, what's wrong with 8080? is there any other limited ports for the liver server?

It's highly possible that vscode live server use port 8080 internally
When Xampp is set to another port than 8080 and live server is started, use the following command in cmd to display a list of process using that port:
netstat -an | find /i "8080"
The PID of the process using that port is at the end of the line , then do the next command by replacing with that number to find out which process opened it, you can also look in your task manager for that.
C:\ tasklist /svc /FI "PID eq <PID>"

Related

Could not start GlassFish Server4.1 HTTP or HTTPS Listener port is occupied while server is not running ON A MAC

Could anyone shed some light on this? I have watched a few YouTube videos with the same problem but all solutions are based on Windows. How could I fix this on a Mac? I'm pretty sure I have no other servers running.
Thanks
see error image from netbeans
This means that there is another application using the ports the Glassfish requires. Use the command
lsof -nP -iTCP:$PORT | grep LISTEN
to list the what ports are in use along with the process ID of the process using the port. Glassfish requires ports 4848, 8080 and 8081 to be free. One app that sometimes causes port issues is vnc, so check if you have screen sharing turned on and try disable it if that is the case.

React can't talk to node ERR_CONNECTION_REFUSED

I am trying to create a React / Node app.
Inside a React component I am trying to populate a component using:
await axios.get('//localhost:8081/')).data;
Node is running and netstat shows it is listening on 8081, additionally when I test using curl, the data is returned:
curl http://localhost:8081/
[{"id":1,"data":"test"}]
However in the browser console I see:
GET http://localhost:8081/ net::ERR_CONNECTION_REFUSED
Check if cors is enabled on server side. Additionally check if any other process is using the port, and node process/server is actually running.
"npm start" was running on port 3000, the server's firewall had this port open. node was running on 8081, this port was not open.
I thought the 3000 process (npm start) would talk to the 8081 process (node) directly, or something like that. But it looks like the 3000 server gives the page, then your browser talks directly to the 8081 process. Once I opened port 8081 on the firewall and changed the axios line with the server's IP it all worked.
I don't really understand why there are two processes for this.

Websphere Server Error Launching Server Failed

Error received while starting the server
Reason:
Launching the server failed:
Location service deamon port 9000 is in use
Change each used port number to another unused port on the Ports page of
the server configuration editor.
I already tried to restart the computer and the result still the same.
What else i try to resolve this issue??
You have 2 options:
Stop the service/process which is using 9000 port or change its value
Change that 9000 port in WebSphere configuration. Since you cannot start your server you have to do it manually, editing xml config files:
I'm assuming you have standalone single server, in case deployment mananger and multiple servers you need to find the correct one.
Go to the PROFILE_ROOT\config\cells\YOUR_CELL_NAME\nodes\YOUR_NODE_NAME\serverindex.xml and look for 9000 it should be ORB_LISTENER_ADDRESS. Change that port to free one. You can check ports that are already taken in system using for example netstat -an

Openshift binding a TCP port with port forward?

according to this doc
Does this mean we could port forward 8000 and 8443?
If I deploy a spring integration project with TCP port binding to 8000 or 8443, will I able to telnet to openshift?
I have tried, but not sure what happened. When I use putty RAW mode connect to 8443, and send some text, nothing happened on the server console, my program should print out what it received. so I suppose I failed, right?
P.S. that project was tested using localhost tomcat, it works locally.
this related question seems to successfully forwarding many port.

Change Listen Address Web Logic

I have a server running on weblogic 12c. But it is running on localhost:7001/myapp/.. I can run it by http://localhost:7001/myapp/... or http://127.0.01/myapp/... But only on the computer that weblogic is installed. I need to access from other computers. I have changed the Listen Address from localhost to my public IP, but when i did it, my server did not run anymore, it shows an error "Could not find lock file. Maybe the server is already running" something like that. I have already tried to delete the .lok file, but that did not work either. Tried to change the config.xml file, but that did not work either. Have this happenned to someone? How do I fix this?
I faced the same issue and below the answer, for stand alone Weblogic and even for embedded one, You want to change Listen Address, Just do the following steps:
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the left pane of the Console, expand Environment and select Servers.
On the Servers page, click the name of the server.
Select Configuration > General.
On the Severs: Configuration: General page, enter a value in Listen Address.
Click Save.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).
For (integrated weblogic only) on JDeveloper, open Application servers from windows menu, select Integrated weblogic, right-click on it, select Properties, select Configuration tab, Change hostname with the same IP address you put in Console
if your Weblogic server isn't production server, just ignore steps (1 & 7)
reference : https://docs.oracle.com/cd/E50629_01/wls/WLACH/taskhelp/channels/ConfigureListenAddresses.html
First you need to check what is running on 7001 port:
On windows use: netstat -ano|find /i "7001" it will give you something like :
TCP 0.0.0.0:7001 0.0.0.0 TIME_WAIT 1028
then you can kill that process using
taskkill /F /PID 1028 (java process started on 7001)
Now try to delete *.lok file from Domain/servers/AdminServer Path
and start admin server .
If you have nothing specified in listen address field it will listen on all the available network interfaces which can be check by ipconfig command on window
On linux use netstat -tulp|grep 7001 to find process
Did you see check if there is another application running on your public ip and the same port ?
Your Question is not at all clear. You say your server is running on a server and you can access it using the url http://localhost:7001/myapp/...
So that bit is clear.
Then you try to access your application from another machine. This where it gets confusing.
You say - "I have changed the Listen Address from localhost to my public IP, but when i did it, my server did not run anymore, it shows an error "Could not find lock file. Maybe the server is already running" something like that."
Why would your server stop running if all you did was try to access from a different machine ?
" The error could not find lock file " is usually seen when you try to start a server on a machine where there might be another server already running. But since your aim is only to access your already running server from a different machine you would do that using a browser, why start another instance ?
Could you throw some more light on what exactly you are doing and the result.
Few tips -
Check the listen address of your weblogic server from admin console.
Check if the server you are running weblogic has more than 1 ip. Run ifconfig or ipconfig to get the IP's