A
A
alexey_jurievich2016-10-19 14:32:36
Digital certificates
alexey_jurievich, 2016-10-19 14:32:36

It does not redirect from http to https, while the site is not accessible at all via http. My cant?

Hello dear masters. The essence of the problem is that the site is not accessible via the http protocol, it gives (after 2-3 minutes of loading) an access error and does not redirect to https. If you enter a direct address via https, everything works. Tried many constructs in .htaccess worked fine yesterday

RewriteCond %{HTTPS} off
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
none work today. The last one I tried
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www.)?site.com$ [NC]
RewriteCond %{HTTP:X-Forwarded-Proto} !=https
RewriteRule ^(.*)$ https://siite.com/$1 [R=301,L]

I also noticed an interesting problem, when adding a site to the bookmarks bar with https, the picture is white (more precisely, it is simply missing, but it should be so), and if you add it with http, it is red as soon as the domain was registered.
Please advise how to solve this problem? tired already.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Alexey, 2016-10-19
@alexey_jurievich

Purely by symptoms - port 80 was closed via iptables (packets are simply dropped - drop).
You can say more precisely if you see the patient and configs.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question