Trying to configure Live Server to properly launch and connect to web pages on my local machine in VSCode .However, I seem unable to set the port I want to run live server on. When I accept the default port (chosen by the extension itself) I get ERR_UNSAFE_PORT from both Chrom and Firefox.
I have tried changing the settings, but its seems to be ignoring anything I put in there. Can someone please advise ?
Here is a screenshot of where I am trying to set the port..
Thanks..
P.S It does not matter what value I use for the port (2000 here just as an example.) Whatever you put in is ignored. tried various,, 8080 etc..
https://github.com/ritwickdey/vscode-live-server/issues/2611
May local config overrides the global config？
Related
I have installed the jfrog-artifactory-oss-7.3.2 in windows 10. Default port has been changed to the 8285 in below files. (8285 port is available)
C:\jfrog-artifactory-oss-7.3.2-windows\artifactory-oss-7.3.2\app\artifactory\tomcat\conf/server.xml
C:\jfrog-artifactory-oss-7.3.2-windows\artifactory-oss-7.3.2\app\misc\tomcat/server.xml.template
C:\jfrog-artifactory-oss-7.3.2-windows\artifactory-oss-7.3.2\app\misc\tomcat/server.xml
once execute artifactory.bat server is getting up without any issue. I don't see any log errors in catalina log either access, access_service etc log files.
but browser gives below error.
***** HTTP Status 404 – Not Found
Type Status Report
Message /ui/
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/8.5.51 *****
If i change back to the default port(8081) it works perfectly.
If someone came across issue like this please share your thoughts and solutions.
To change server port of artifactory, you need change in system.yaml. Please review system.yaml.template.
The path in system.yaml is
artifactory:
port: 8081
This change will make changes needed in server.xml as well.
Also if you want to change the router port which serves the UI. Please change system.yaml as below
router:
entrypoints:
externalPort: <new port>
Let me know if this does not work for you.
I am trying to change the ports of my jboss server to run on port 80.
I've tried what feels like everything: editing the server.xml file, editing the C:\jboss-5.1.0.GA\server\default\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml file to no avail.
Is there another way that I'm missing because I can only access my server via port 8082.
Yes, to change ${JBOSS_HOME}/server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml is the answer, as pointed out in another question
But also change:
1. server.xml file at $jboss/server/jboss-ports-01/deploy/jbossweb.sar to the port you need
Verify also ${jboss.service.binding.set:ports-default} setting the correct binding as in ${jboss.service.binding.set:ports-PORT}
This reference brings more information about it as well.
I have several Play applications running parallel. One of them is running in Eclipse. I want to connect the Eclipse debugger (launcher "Connect JPDA to myapplication.launch"), but the port changes every time (probably due to one of the other applications blocking the default port). I would edit the launcher and enter the current port manually*, but: How would I know which port to use?
PS: As my app runs for quite a while I do not see the port initially displayed in the console anymore.
*PPS: Is there a more elegant way to handle this?
The more elegant way of handling this is to just define the jpda port it should use yourself, so you always know behind which jpda port an application is running and you don't have to look it up all the time. Its documented in the configuration manual and it comes down to adding jpda.port=???? in your application.conf (changing the question marks into a port number, ofcourse).
The reason they change is indeed because they are running in parallel. Java automatically switches to the next available port if the default is in use.
There should be a line in the output log that looks like the following:
Listening for transport dt_socket at address: <some port number>
That's the debug port number you need to configure in Eclipse for JPDA.
OK, in OS X you'll find the port in the activity monitor: Double click each "java" process until you find the one belonging to Eclipse. The requested port is the one mapped to "*".
Click here for details (in German) and screenshots (I need 10 reputation to post images or more than two links)
I am trying to run JBoss(5.1) on remote system connecting it using RDC. Which ever port I try, it's says already in use and throwing java.net.BindException Cannot assign requested address: JVM_Bind
I have tried to change the port using jboss service binding configuration located at below path:
jboss\server\Server_Instance\conf\bindingservice.beans\META-INF\bindings-jboss-beans.xml
I have tried various options like ports-01, ports-02 ,ports-03 and then customizing the default port configurations as well with No luck.
I am just wondering how it is possible that it's not allowing any port whichever I try. One thing I would like to let you know here is that the remote system has 3 different logins and all of the users are using the system.
Appreciated if you can provide me any assistance please.
You can pass the -b ${IPofMachine} to bind to an IP. This will also make it externally accessible. You can do 0.0.0.0 which will bind to all available IP's
Already, I've checked at least 20 resources and am out of ideas:
I have a clean, remote Ubuntu EC2 instance, fresh from the AMI, having stopped only to install LAMP, phpmyadmin, and xdebug on it. Yes, I have configured my remote EC2 instance's php.ini file as follows:
Meanwhile, back on my laptop I have Netbeans & Eclipse installed. While I can get either to seamlessly upload and Run my php web app on my EC2 site (via SSH/SFTP) as soon as I hit "Debug" from either, index.php gets uploaded, a browser window opens, and then NOTHING HAPPENS. The page doesn't load, the Debug perspective doesn't open, breakpoints don't get triggered, nothing. Netbeans just hangs out saying "waiting for connection" whereas Eclipse just sits at the notorious 57% level (& yes, I toggled the xdebug.idekey before testing with Eclipse)).
So I tested xdebug's functionality on my server according to the instructions found here and here (both passed). I tried changing to port 9001 (in remote php.ini as well as in local Netbeans/Eclipse), I even tried launching this brand spanking-new EC2 instance with pretty much open Security group settings (SSH=0.0.0.0/0), but nothing seems to be working. I am out & out flummoxed, a self-confessed noob, and appreciative of any insight seasoned professionals in the community may have to offer.
Thanks,
Debbie
This feels like a networking issue to me. Port 9000 may not be accessible. The quickest way to test is to telnet to port 9000 on the remote system (if you have a telnet client installed that allows you to specify which port to telnet to). If the telnet attempt times out or is closed by the remote system you will see the error and this verifies that there is a networking issue.
I would check /etc/services to make sure that port 9000 is not reserved for use of something else. If port 9000 exists and is uncommented then something else is using the port and that services does not know how to respond to your request so it hangs.
I would do a netstat (lookup params to see "all" listening ports) and make sure the remote system is listening on port 9000. If you don't see port 9000 then the remote system is not configured to establish the connection.
If you are on a WIFI network then port 9000 may need to be port forwarded to the remote system using the internal cable modem configuration menu/utility. This is the scenerio I favor because I've wasted so much time solving this kind of problem with different software.
Good luck, you have more troubleshooting ahead of you and different questions to ask to resolve your problem.