I used apt-get to install cacti on my ubuntu 10.04 box. It said it installed correctly, but I'm not sure what port its listening on.
Try using http://localhost/cacti. None of the docs (that I have found, at least) reference a specific port, so I'd assume that it's listening on the default http port (80).
If nothing else, you can use netcat to scan your machine for open ports before and after launching cacti. Any ports that change between the two scans are probably in use by cacti.
Related
I deleted my XAMPP from the applications folder(without uninstalling) and installed it again then I tried to change my apache port 8080 after that this problem showed up 'Cannot bind to port 8080. It is probably taken by another application or you don't have enough privileges'
I tried to fix it by uninstalling and installing again it didn't work then I deleted cache files of XAMMP with some sudo code but it didn't work anyway
in windows to check what ports applications are running on, open command prompt as admin and type "netstat -a -b"
stop whatever application is running on port 8080
Okay, here's the situation I am in. I have a raspberry Pi 2 model B. I have Raspbain Jessie installed as the OS. I have Apache installed as well. I have a web server running and i am able to edit it and access the site from different devices on different internet connections. I want to be able to connect to my RaspPi through SSH on my MacBook Pro. I am able to do this while on the same network. My Pi is plugged into the router via an Ethernet. What i have tried is, logging into my router and reserving an IP for my Pi, i also entered my MAC address here. I have gone into the port forwarding options in my router and have it set up as: HTTP, TCP, Server address(the one i reserved) my Ipv6, and Start port 80, end port 80. Ontop of that i have gone into my /etc/dhcpcd.conf file. There at the end of the file i added
interface eth0
static ip_address=10.0.0.100
static routers=10.0.0.1
static domain_name_servers=68.44.180.118 2001:558:feed::1 2001:558:feed::2
The guide I followed is attached here and follows other guides i have seen.
http://www.circuitbasics.com/how-to-set-up-a-static-ip-on-the-raspberry-pi/
Yet when i try to SSH remotely i cannot get a connection, and when i connect on the same internet i can connect as normal. Please if anybody sees what could help .
Your router's firewall is probably blocking the ports for SSH, which does not use port 80 (in raspbian, I think its default is port 22). If you are going to take the risk of leaving your SSH open to the public, you should probably switch it to a different port other than the default before opening up a port on your firewall. The Raspbian Community has a thread on how to properly change SSH's default server port. You'll also need to make sure your SSH client is using the same port. You will need to leave 80 open for web, and also forward the SSH port, which ever you choose that to be (22 is the default).
My machine is a regular laptop with Windows 7. I have a Virtualbox VM running Ubuntu Server 14.04.1 and I have apache2 installed. When I try to access the default webserver page (10.0.2.15) from my machine, it cannot find the page. I have disabled my machine's firewall so that isn't causing the issue. The network for my VM is NAT, but I also tried the bridged adapter setting to no avail. Any suggestions would help.
Can you ping the server? If so, try the netstat command in server terminal to determine if it listens to port 80. If you cannot ping it, check the network address, f.x with ifconfig
If you can ping apache from the server, you probably have a problem with the network.
Try to add an host only interface. Then, in your VM, sudo ifconfig. Use the eth1's ip.
I have recently starred out with EC2. Currently I am using the Free Tier to test and learn about it. However as I am behind a proxy that allows only connections at port 80 and 443, I am unable to connect the EC2 instance. Is there a way to get past this ?
So far I've guess that running sslh on the EC2 instance, as described here might help. But I am not sure if this behavior should remain persistent once the instance is terminated and re-started (as I am using Free Tier). Is there a way I can achieve persistence in terms of settings and installed resources like sslh (and many others) while using the Free Tier ?
Thanks in advance.
Once when behind a firewall that only allowed outgoing communication on ports such as 80, I just ran an sshd on the server on a different port. You won't be able to set this up while behind the firewall, you'll have to go somewhere else, ssh in, and reconfigure ssh.
Instead of running sshd on a non-standard port, you could also just have something redirect traffic from some other port to port 22.
If your ec2 instance isn't running a web server, you can use port 80 or 443 for the sshd. If you're not using https, then use 443.
You say they only allow outgoing traffic to remote ports 80 and 443, but often times ports above 1024 are also unblocked.
Make sure you've also correctly configured your security groups on the ec2 instance, since it has a firewall as well. You'll have to make sure it's configured to allow incoming traffic on the port supplying the sshd from your IP address. This can be done through the aws management console.
Here there's is a neat solution. I haven't tried it. The idea is to pass a script to boot the instance with ssh bind to port 80.
Goto instances
at the top of the list of your running instances you should see "instance action"
In that menu you should see "connect"
Select "connect from your browser using Java ssh client"
note, you need Java to be installed.
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 9 years ago.
I just switch to Apache webserver and I receive an error
(OS 10048)Only one usage of each socket address (protocol/network
address/port) is normally permitted. : make_sock: could not bind to
address 0.0.0.0:443 no listening sockets available, shutting down
Unable to open logs
That is what I have got after running httpd from commandline. I reset my apache documentRoot as well as server's listening port to one that is free to use already, I have no idea about this error with port 443, is it something about SSL ?
UPDATE
I am using XP
For Windows XP
netstat -ano
Find the process id that is using port 443, and kill it using task manager
For me it was IIS using the port.
Copying and pasting your exact error into google gave a couple of answers:
https://wiki.apache.org/httpd/CouldNotBindToAddress
Port 443 seems to already be in use. Possibly by your old server. One of the three covered errors in the official apache wiki above is:
Address is already in use
Something else is already using the port in question.
Run one of the following commands to check if a running process is
holding the port needed by apache open.
On Linux/Unix run
$> netstat -plant
$> # or
$> sudo lsof -i:80
On Windows run
$> netstat -ano
On Mac OS X / FreeBSD run
$> netstat -Wan |grep 80
$> # or, to get the pid
$> sudo lsof -i:80
Once you see these results, you can choose to kill the program in
question, or change the port that Apache uses.
If Apache (httpd, apache2, etc) is the application listening on these
ports, but you can't stop it using your normal procedure, someone may
have deleted the servers PidFile. The PidFile records the process ID
of the parent process and is how most scripts test to see if Apache is
running. You can manually stop the server by determining the PID of
the parent process and sending it a SIGTERM.
For me it was having multiple directives of Listen 443 in my /etc/apache2/ports.conf file. Even though netstat and/or ps showed nothing for 443, it was still trying to listen multiple times, which in turn threw that error.
It sounds like you already have apache running. Use nestat to figure out which process is using 443 and kill it.
netstat -tulpn | grep :443
Then
kill PROCESS_ID
Where PROCESS_ID is the number of the process that is shown when you the netstat command (example: kill 12345).
After that try starting apache again.
I found on my system (Win7) that Skype had taken over the port that Apache was trying to use. In the new version of Skype I haven't yet found the checkbox to uncheck so that Skype doesn't use it (there was one in a previous version). Quitting Skype enabled Apache to start.
port 443 is for SSL. Seems you miss the rights to use that privileged port. Privileged ports are those with numbers below 1024.
Which OS are you using?
Probably something else is already using port 443 and therefore Apache is unable to use it, do you want to use SSL actually ?