I have a windows server running Plesk. I was having some issue with port usage so I ran the command netsh http delete iplisten ipaddress=:: and I had multiple apps running on that server that I don't even remember the configuration of and they all stopped working. I restarted the server hoping that it would restart the services but to no luck. I ran netsh http add command to again listen :: but its not helping. Anyone knows what I did wrong here?
Related
My server's hosted at DigitalOcean (it's a droplet) and basically, I cannot access my NodeJS app via Internet, only server-side. It's running on port 9000, I've allowed traffic to the port via ufw and iptables, no luck. When I run curl || wget while SSH-ed to the server, I get a normal response as if everything's in order. But when I try to access the server from an another machine, I just get timed out because the server returns nothing. I've heard DigitalOcean sometimes disable connections to all ports except ssh,www and ssl, but I think I've successfully 'opened' them. Any suggestions?
This is what I get when I run netstat -tulp | grep LISTEN
Turns out my dashboard was all messed up when it comes to ports, which I forgot to check, of course, so opening them directly on the server gave no results whatsoever.
I installed TeamCity on a windows server 2016 machine and I assigned the ci.mydomain.com to the serverUrl. I have IIS also on that machine that hosts my nuget server.
When I type in ci.mydomain.com it returns a 404. nuget.mydomain.com works fine
Does anyone knows why?
Thanks in advance
"Server URL" in TeamCity administration settings does not affect how TeamCity server can be accessed.
You can start by opening 127.0.0.1:PORT on the server machine to check that the TeamCity is running OK, where PORT is where TeamCity is configured to run on (e.g. check \logs\teamcity-server.log file, line with "Web server ports")
If that works, make sure SERVER:PORT works from other machines, where SERVER is the machine IP and the same PORT. If you'd rather use IIS as a reverse proxy, check related TeamCity instructions.
Finally, you will need to make sure ci.mydomain.com resolves to the IP and use due port in the URL.
I am running node server running react application.server is run by webpack. Server is running on 10.121.45.23:3005. I tried opening the application on other machine but page displays connection timed out. I have tried following things to resolve the issue, but nothing helped.
ping 10.121.45.23 from another machine. It is successful.
On server, netstat -ano. I am able to see 10.121.45.23:3005 listening. No loopback address was there as mentioned in many answers on Stack Overflow.
On another machine,telnet 10.121.45.23 3005. It fails and say cannot connect on port 3005. Telnet to some other port on which java is running, is successful. It fails only for node.js server.
So my problems are:
telnet is not working to that port.
Not able to open application on other machine's browser.
Am I missing any checks?
Sounds like you've tested quiet a bit. Have you tried another port, just in case there's a firewall or something?
Also, try explicitly telling webpack to listen on the all-hosts address 0.0.0.0
webpack-dev-server --port 9000 --host 0.0.0.0
I recently setup an Ubuntu 12.04 LTS server running nginx, and I could connect to it via its IP address. However, after restarting my computer I can no longer connect to the server in any browser but I can connect via SSH through puTTy. No clue what's going on and ifconfig shows that the IP address has not changed and I changed no settings on the server. How can I fix this?
This picture shows the chrome window response when I try to access the server, the ifconfig from the server (top right), the network settings on the VM (bottom left), and the location settings for /etc/nginx/sites-available/www.
server settings
I have tried restarting, doing an nginx reload, and a full computer restart. Nothing has worked so far. All help is greatly appreciated!
First make sure that the service is working using sudo service nginx status
If it's not running try starting it manually sudo service nginx start
If it fails to start, you can check the error log in /var/log/nginx/error.log or any other error log defined in the server config.
I am new to linux and just deployed a java program to run on a linux server. I tried to connect from my windows machine to the linux box with jconsole and got an error.
Connection Failed: non-JRMP server at remote endpoint
I searched online and found the following suggestion was to run the following:
java -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=
[YOUR PORT] -Dcom.sun.management.jmxremote.ssl=
false -Dcom.sun.management.jmxremote.authenticate=false -jar [YOUR JAR NAME]
I entered the following into a batch file and executed it. I then tried to connect using jconsole using the follow command
service:jmx:rmi:///jndi/rmi://ipaddress:port/jmxrmi
as suggested but still cannot (Connection failed: retry)/
I got the same issue but the reason was different, I was hitting http port instead of JMX port.
The error message appeared same as in your case but later I figured out it was port issue.
Since JMX process runs on different port so be careful while opening JConsole on remote server.
Resolved situation by setting hostname to ipaddress when calling process on linux
I faced this problem at localhost.
Wrong port was used.
So, I changed my JMX port to be different from application port in my run configuration and yet, the port changes did not take effect until the application container was restarted.
Fixing above resolved my issue.
Another possible reason for error message Connection failed: non-JRMPserver at remote endpoint: the RootCA-certificate of the server hasn't been added into the client's cacerts file.