firewall-settings section they have said that the ports 80 and 443 should be opened, but we have already installed the APACHE server on our Linux server and the ports 80 and 443 are occupied already by our APACHE server. So its a conflict situation. What should we do here?
mesibo on-premise server will detect and use other ports. You can ignore port warnings.
Related
I am attempting to set up an apache2 web server on my raspberry pi. I am able to connect to it by doing http://localhost:8080 (8080 because my router blocks port 80). Although when I do http://my.pub.lic.ip:8080 the connection times out. I set up port forwarding so that requests going to my router on port 8080 go to my raspberry pi on port 8080. This does not seem to work but I'm also not sure if the port forwarding is the cause or if it is something else. Any suggestions?
Is your web server configured to listen on the network interface besides localhost?
https://httpd.apache.org/docs/2.4/bind.html
For example, to make the server accept connections on both port 80 and port 8000, on all interfaces, use:
Listen 80
Listen 8000
To make the server accept connections on port 80 for one interface, and port 8000 on another, use
Listen 192.0.2.1:80
Listen 192.0.2.5:8000
You can try using nmap by finding your router's public IP and on the raspberry pi type nmap my.pub.lic.ip This will show you what services are actually being published to the world. This gives more insight to the problem.
I got the web server up and running although for some reason it appears that my isp would only allow it to be hosted securely (as an https page)(I'm not sure if that's the right way to phrase it). To achieve this for free, I used cloudflare's ssl service. A tutorial to set it up for apache2 can be found here
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.
I just want to know if I can forward port 80 or 8080 or 21 on my router just to check if those ports are open to public. I don't have a server running on my PC though. I'm sure it's possible if a server is running and configured.
This is a very detailed link on how to do it , but i guess it is also depends on the router you've got .
http://www.pcworld.com/article/244314/how_to_forward_ports_on_your_router.html
This is what I am trying to do:
Open a browser and start to browse any https website like Gmail or Google.com
I can see through Wireshark that the name resolution is being done by the DNS server.
But after that, the connection is directly established to port 443 (starting from TCP handshake)
One thing I am not able to understand is, how does the browser knows that it needs to connect to port 443, I tried exploring the DNS packet, but it contains only the destination address, and there is no info which tells that it needs to connect to port 443.
Even if say, the browser has a priority in querying for the first time, it sees that if the port 443 is open then connect to it or connect to port 80, but I am not able to see any such behavior if I connect to a normal HTTP website, in the sense that, if I go to a normal HTTP website, there is no traffic flow from the browser indicating that it had searched first the port 443 and then went to port 80.
I am sure that I am missing something here, but not sure what it is.
The presence of https: in the URL tells it that.
The browser (client) uses the HTTP or HTTPS in the address to determine which port to use...
However the server can be configured to require HTTPS, and to switch/redirect an HTTP port 80 connection to HTTPS port 443 with encryption & certificate. So if the browser connects to a server via HTTP port 80, the server can then immediately switch/redirect the connection to HTTPS port 443. The server may even be configured the other way around to switch/redirect a connection from HTTPS port 443 to HTTP port 80.
I think this is sort of like asking why does a FTP client use the FTP port
Unless you specify a port with "http://...:port" the browser uses 80 for http and 443 for https as thats what the protocol defines but....
A server may respond with a "Strict-Transport-Security: max-age=..." and the browser is then required to retry on https and remember this
In addition Chrome , see HSTS, ships with a large preseeded HSTS list
so even if you type http for a site in the HSTS list - the browser will look at its HSTS configuration see that the site is specified and instead change to HTTPS on port 443 without trying http on port 80 first
I am having problem with my ports, yesterday I opened port 80 and setup local area connection propeties for ipv4 to use static ip 192.168.1.4, I used ipconifg in cmd to check it first. I am using WAMP server on my pc with windows 7 64-bit. It worked ok.
But today ports are closed, and I didn't changed anything from yesterday. I tried to opened additional ports besides 80 like 8081,443, 8080 in my router with local ip 192.168.1.4 like same setings in my ipv4 propeties to see if give some result, I disabled router firewall, allowed ports to go trough windows firewall, and added all ports for tcp and udp to my norton internet security, I tried also disabling whole firewall but same result.
WAMP is running and listening on port 80, 8081, 8080, 443.
This is part of wamp apache httpd.conf file.
Listen 0.0.0.0:80
Listen [::0]:80
Listen 8081
Listen 443
Listen 8080
ServerName localhost:80
When I check which program is using port 80, it says Apache/2.4.9 PHP/5.5.12
I noticed that all other ports except 80 and 443 are closed, but 80 and 443 are refusing connection if router firewall is off, and if its on they are closed also. And yesterday I had router firewall on, norton firewall on, and no rules for windows firewall, and it worked.
Thanks for your help in advance.
Try to open the task manager --> processes and close all the process related to apache or JBoss or which ever server you are using. Then try to restart the application. If this does not work try to go the location of the server/ bin folder and run the shutdown.bat in windows or shutdown.sh in linux. It should start working.
It seems there is a Web server running on your PC. try to shut it down