Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
We are running a Java based web-application, and were in the process of updating the site from http:// to https:// (by installing SSL cert),but encountered issues with bringing the site online.
On further analysis, we found that the port 443 was being blocked, which was preventing this site from being accessible on https://
We informed the same to the Network team, to open firewall on port 443. But the problem is, they keep coming back asking for the destination port.
We provided the source IP (IP of the application server)...what would be the destination IP (is there a specific destination IP if a site needs to be accessible on https://) ????
My question is, what would be the destination port, to open firewall to make a site accessible on https:// ??
Most likely they want to setup NAT so that incoming requests coming to NAT:443 are routed to :443 , and for this they do need an IP of the server within the local network.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
The website is reachable by host name but not by the ip adress specified in the A record. The DNS successfully resolves the request to the same ip specified in the A record.
Postman tells me: Error: Hostname/IP does not match certificate's altnames: IP: [...] is not in the cert's list.
Background: I have connected a Firebase application with a existing Domain. Firebase has generated a certificate for this website.
There are not enough IP addresses for all web sites to have a unique IP address. Firebase Hosting makes everyone's sites share the same IP address, and is able to distinguish requests for sites using the HTTP Host header from each request. This means the Host header is required. Postman will add that for you automatically if you use the domain name of your site, but it would have no idea what to use if you just provide an IP address.
See also: What is http host header?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I can access the web site from the local network (192.168.2.120 My Local IP)
but i cant access the web site from global network (95.10.239.XXX My External IP)
I opened 8080 port from the modem
IIS Edit Bindings Image
I opened 8080 port from firewall
Im using Windows 10
First of all you need to check if port 8080 is accessible from outside. You can use this tool: http://www.yougetsignal.com/tools/open-ports/
If it is accessible, then it should work, if you will try to open in browser http://95.10.239.XXX:8080/
If it is not accessible, then you might need to do this steps:
Set up port forwarding and(or) DMZ in your router. It depends on your router.
Open firewall on your machine. You mentioned that you did that already.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
until recently I was using lighttpd + openvpn + sslh, to provide both HTTPS and OpenVPN on port 443. But sslh has some significant issues with passing remote IP address to HTTP server and also it does not work well with Gitlab. So I moved to nginx and now I'm trying to achieve the same functionality with OpenVPN as before.
How to configure nginx to handle incomming HTTPS connections and forward unknown connections to OpenVPN?
I know OpenVPN can do this with HTTPS, but it does not solve problems with passing remote IP address to web server (correct remote IP address is more important for web server than for OpenVPN).
Other way around may be like Websockets do, to let OpenVPN to use HTTP upgrade or similar technique, but I haven't found anything about that in OpenVPN documentation.
Nginx is not capable of looking into SSL connections to determine the protocols used to further forward the connection to either an http/https upstream, or a VPN.
It can handle any arbitrary TCP streams now (and load-balance the connections without looking into payload), but unless you have more than one port or more than one IP address, you'll have to continue to depend on your sslh.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I understand that the job of IP in the TCP stack, when dealing with an outgoing message, is to resolve an IP address from a host name and add this address as a header.
Is this process that IP goes through equivalent to using a tool like nslookup for a given hostname?
Your understanding is incorrect. IP doesn't know anything about device names, it only deals with IP addresses.
An application can query a DNS server or a hosts file to resolve a name into an IP address. This must be done prior to using IP to forward a packet since IP can only use an IP address. Tools, like you mention, and other applications, such as browsers, query a DNS server (requires you have the IP address of a DNS server configured) or use a hosts file to resolve the name to an IP address.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I want to run a web server on my home network but my ISP doesn't let incoming requests from port 80, so I have to use port 81, is there a way I could hide the port number from my domain so that people don't have to type mysite.com:81 in the address bar?
I tried to use an SRV record but after failing so many times I realized that the browser needs to obey the SRV record and it doesn't so that's why it doesn't work.
Note
My ISP also wouldn't let me buy a static IP so I have to use a dynamic dns service provided by noip.com.
If your ISP blocks port 80, then you can't run anything, not even a port forwarder, on port 80. Which means your visitors will need to use the port number. Period. Sorry, but there's just no way to make the browser use a different port without telling it to.
One thing that some dyndns providers allow you to do is to create a page that's shown when the domain is offline. You could get jordanjones.noip.com and realjordanjones.noip.com, set jordanjones.noip.com to offline, and make a page there that's nothing but a frameset with one big frame that pulls in realjordanjones.com:81. Don't know if noip.com offers that service, though.
The only real answer is: get a decent provider.
You need to do either port forwarding or redirect requests on server.
For example run server on 8080 port and redirect all requests from port 80 to 8080.
See this: Apache VirtualHost: How to ServerName a port different from 80