New answers tagged

0

No. A webmail page is just a normal web page. Of course, you could try to scrape the site and find file names and HTML fragments that can be associated with a webmail product, but this not reliable at all. Why do you want to do this anyway?


0

These two domains ideally considered as one. So they do not need two various certificates. At present, most of SSL certificates (Comodo, RapidSSL) support both WWW and Non-WWW version of domain name. So both version of your domain name example.com and www.example.com will be supported by HTTPS. Therefor you will have to set 301 redirection of example.com to ...


0

You misunderstand the "lack" of SNI support. First, nginx is generally fine for "wildcard" SSL setups. The support issue is in older clients (i.e. browsers), which are not capable of handling SNI.


3

It's easier to maintain if you have one certificate, and there are no real downsides. You can put as many unrelated domains as you like on a certificate, so putting the www subdomain on seems fairly reasonable. Just use one certificate IMHO.


1

Try hitting your site with the SSL Server checker on ssllabs.com. It looks like something about some SSL clients is causing them to abort the handshake. This could be various scanners, or it could be some clients are rejecting something about your SSL connection and are dropping it. Many clients will retry with a downgraded connection which is why the ...


1

I know it is a old question but i had the same problem and solved using this in squid.conf dns_v4_first on Regards


0

You can add this to your apache config at /etc/apache2/ports.conf: <IfModule mod_ssl.c> Listen 443 <IfModule !mod_authz_core.c> # Apache 2.2 NameVirtualHost *:443 </IfModule> </IfModule> (This ...


0

I ended up doing something different, and secured everything but a page that didn't work if it was protected: RewriteEngine On RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteCond %{REQUEST_URI} !^(.*loadFormImages.*) RewriteRule (.*) https://%{SERVER_NAME}%{REQUEST_URI} [L] #RewriteLog /opt/tmp/rewrite.log #RewriteLogLevel 3


1

Try this RewriteRule ^/protected-page/(.*) https://example.com/protected-page/$1 [R,L] reference : http://httpd.apache.org/docs/current/rewrite/intro.html


1

It turns out that it was simply an error in the web.config file. These two answers on SO were the solution: http://stackoverflow.com/a/26581326/1286358 And the reverse http://stackoverflow.com/a/26539003/1286358 Strange that it was working on both http and https once and then just stopped.... there must have been some other configuration changes ...


0

Using the SSLProxyEngine On will do the trick. What i actually did was set the vhost file on ServerA as per bellow: <VirtualHost serverA:443> ServerName serverA.example.com SSLProxyEngine On ProxyPass / https://serverB.example.com ProxyPassReverse / https://seerverB.exampe.com </VirtualHost>


0

Use the -nodes parameter, if this option is specified then the private key will not be encrypted, e.g.: openssl \ req \ -nodes \ -newkey rsa:2048 \ -keyout www.example.com.key \ -out www.example.com.csr \ -subj "/C=DE/ST=NRW/L=Berlin/O=My Inc/OU=DevOps/CN=www.example.com/emailAddress=dev@www.example.com"


2

but all the ones I found describe the creation of a certificate pair to decrypt/re-encrypt the traffic - something I do not want to do. What you are asking for simply isn't possible because of how the https protocol works. Your options are: Permit outgoing https through your firewall, and don't attempt to use any proxies Configure clients to use your ...


0

For an Ubuntu server (assuming you installed with apt-get install jenkins): You'll want to edit /etc/default/jenkins at the bottom of the file, edit Jenkins_args. In my args, I've disabled http access (using -1) and put SSL on the default Jenkins port (8080). The most important part here is that you sent an httpsPort and certificate/key (if you have one, ...


-1

I am glad to answer your question, but i don't clearly know about where the problem of you. Is dns or nginx.conf question? If possible, you should paste some part of nginx.conf file in your question and clarify which page is that you expect.


1

I think you're going to run into major issues running both IIS and VisualSVN, which installs and runs on Apache, on the exact same server. If I were you, I'd separate them out and give each web server their own VM. I know this doesn't directly answer your question but I'm wondering if your original posted problem is not a symptom of trying to run both web ...


2

Do you have routing and remote access service installed? If yes, try to disable it (RRAS uses SSTP by default and it listens for 443 port and lsas.exe process which is using port in your situation is used for IPSEC also).


0

In the http page, include a javascript file only available in https: <script src="https://example.net/redirect.js"></script> The content of the js file: window.location = 'https://' + window.location.hostname + window.location.pathname + window.location.hash; Note that this solution is faster for users who can connect to https (because it ...


0

I've done a little trick like this to open an image with https, and if success redirect to https version : <script> function redirectHTTPS() { if (window.location.protocol !== 'https:') { window.location = 'https://' + window.location.hostname + window.location.pathname + window.location.hash; } } </script> <img ...


1

If your clients are not updated browsers (or are not browsers at all), it is not sure that Letsencrypt's root certificate is configured on their side since it is pretty recent. On that issue, there is not much you can do from your side; the clients have to do their job and ensure that the root certificate used by Letsencrypt is configured. I tried ...


-2

Move certificate to web host store.


0

I had the same issue. But then I noticed that my elb-listener was configured incorrectly. I set up load-balancer protocol: https, load-balancer-port: 443, instance-port: 443, but forgot to change instance-protocol from http to https.


2

This was a real issue for me. But I found the answer here. Multiple Hosts and Misdirected Requests Many sites use the same TLS certificate for multiple virtual hosts. The certificate either has a wildcard name, such as '*.example.org' or carries several alternate names. Browsers using HTTP/2 will recognize that and reuse an already opened ...


0

remove the SSL config from nginx and enable it in 'magento' https://www.siteground.com/tutorials/magento/magento_ssl.htm


0

And if you want to force a network, just use regex like this : <If "%{REMOTE_ADDR} !~ /^regex$ SSLVerifyClient require SSLVerifyDepth 2 </If>



Top 50 recent answers are included