Introducing DigitalOcean Functions: A powerful, serverless compute solution

Related

How to set up my cloud/vps server using Ubuntu 12.04 LTS, Apache, MSQL, Phpmyadmin, PHP
Question
codeigniter PHP App on server. URL returns blank page
Question

Question

Redirect From HTTP to HTTPS

Hey, I recently installed Lets Encrypt SSL, its successful however it wont redirect whenever its on http. So how to redirect all to https??

Here method I already tried but it seems wont working: 1 .htaccess

RewriteEngine On RewriteCond %{HTTPS} off RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

  1. Redirect PHP Function

< ?php function redirectTohttps() { if($_SERVER[‘HTTPS’]!=”on”) { $redirect= “https://”.$_SERVER[‘HTTP_HOST’].$_SERVER[‘REQUEST_URI’]; header(“Location:$redirect”); } } ?>

  1. HTML Meta Tag

< meta http-equiv=“Refresh” content=“0;URL=https://www.example.com” />

Note*: This method works however it cause infinite loop and crash the server.

Subscribe
Share
Ph633k • February 21, 2019

It works for me too, thank you so much @KorencSoft !

KorencSoft • February 23, 2016

Just add this into apache site config and change the domain.

<VirtualHost *:80>
    ServerName example.com
    Redirect / https://example.com/
</VirtualHost>
KorencSoft • February 23, 2016

Just add this into apache site config and change the domain.

<VirtualHost *:80>
    ServerName example.com
    Redirect / https://example.com/
</VirtualHost>
KorencSoft • February 23, 2016

Just add this into apache site config and change the domain.

<VirtualHost *:80>
    ServerName example.com
    Redirect / https://example.com/
</VirtualHost>
KorencSoft • February 23, 2016

Just add this into apache site config and change the domain.

<VirtualHost *:80>
    ServerName example.com
    Redirect / https://example.com/
</VirtualHost>
KorencSoft • February 23, 2016

Just add this into apache site config and change the domain.

<VirtualHost *:80>
    ServerName example.com
    Redirect / https://example.com/
</VirtualHost>
KorencSoft • February 23, 2016

Just add this into apache site config and change the domain.

<VirtualHost *:80>
    ServerName example.com
    Redirect / https://example.com/
</VirtualHost>
KorencSoft • February 23, 2016

Just add this into apache site config and change the domain.

<VirtualHost *:80>
    ServerName example.com
    Redirect / https://example.com/
</VirtualHost>
Angel De La Cruz • March 11, 2018

Gracias funciono.

Fabricio Vargas • July 14, 2017

It works for me, thanks!

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Artem Negri • February 9, 2017

Nginx:

server {
    listen 80;
    server_name .example.com;

    location / {
        rewrite ^(.*) https://example.com$request_uri;
    }
}

server {
    listen {IP}:443 ssl;
    server_name example.com;
    ssl_certificate     /etc/ssl/certs/example.com/example_com.crt;
    ssl_certificate_key /etc/ssl/certs/example.com/example.com.key;

    root "/var/www/example.com";
    error_log  "/var/log/nginx/error.example.com.log";

    location / {
        try_files $uri $uri/ index.html;
    }
}
Ryan Quinn • February 22, 2016

Hey. letsencrypt’s auto option should do this for you so I am guessing it’s possible you do not have the rewrite module enabled. This can be fixed by running sudo a2enmod rewrite; sudo service apache2 restart

I have a fresh LAMP server I ran letsencrypt on the other day with a pretty standard configuration and redirects are working as expected so I’ll just share that config with you.

letsencrypt creates two configuration files if you opt for the redirect http to https option. The first is for the non-https (port 80) host.

<VirtualHost *:80>
 ServerName sub.example.org
 DocumentRoot /var/www/sub
 DirectoryIndex index.php
 <Directory /var/www/sub/>
 AllowOverride All
 Order Deny,Allow
 Allow from all
 </Directory>
RewriteEngine on
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
</VirtualHost>

Then the file created for the SSL (port 443) host:

<IfModule mod_ssl.c>
<VirtualHost *:443>
 ServerName sub.example.org
 DocumentRoot /var/www/sub
 DirectoryIndex index.php
 <Directory /var/www/sub/>
 AllowOverride All
 Order Deny,Allow
 Allow from all
 </Directory>
SSLCertificateFile /etc/letsencrypt/live/sub.example.org/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/sub.example.org/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateChainFile /etc/letsencrypt/live/sub.example.org/chain.pem
</VirtualHost>
</IfModule>
  • domain and directory path changed to protect my un-launched service’s identity :)
Ryan Quinn • February 22, 2016

Hey. letsencrypt’s auto option should do this for you so I am guessing it’s possible you do not have the rewrite module enabled. This can be fixed by running sudo a2enmod rewrite; sudo service apache2 restart

I have a fresh LAMP server I ran letsencrypt on the other day with a pretty standard configuration and redirects are working as expected so I’ll just share that config with you.

letsencrypt creates two configuration files if you opt for the redirect http to https option. The first is for the non-https (port 80) host.

<VirtualHost *:80>
 ServerName sub.example.org
 DocumentRoot /var/www/sub
 DirectoryIndex index.php
 <Directory /var/www/sub/>
 AllowOverride All
 Order Deny,Allow
 Allow from all
 </Directory>
RewriteEngine on
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
</VirtualHost>

Then the file created for the SSL (port 443) host:

<IfModule mod_ssl.c>
<VirtualHost *:443>
 ServerName sub.example.org
 DocumentRoot /var/www/sub
 DirectoryIndex index.php
 <Directory /var/www/sub/>
 AllowOverride All
 Order Deny,Allow
 Allow from all
 </Directory>
SSLCertificateFile /etc/letsencrypt/live/sub.example.org/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/sub.example.org/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateChainFile /etc/letsencrypt/live/sub.example.org/chain.pem
</VirtualHost>
</IfModule>
  • domain and directory path changed to protect my un-launched service’s identity :)
Ryan Quinn • February 22, 2016

Hey. letsencrypt’s auto option should do this for you so I am guessing it’s possible you do not have the rewrite module enabled. This can be fixed by running sudo a2enmod rewrite; sudo service apache2 restart

I have a fresh LAMP server I ran letsencrypt on the other day with a pretty standard configuration and redirects are working as expected so I’ll just share that config with you.

letsencrypt creates two configuration files if you opt for the redirect http to https option. The first is for the non-https (port 80) host.

<VirtualHost *:80>
 ServerName sub.example.org
 DocumentRoot /var/www/sub
 DirectoryIndex index.php
 <Directory /var/www/sub/>
 AllowOverride All
 Order Deny,Allow
 Allow from all
 </Directory>
RewriteEngine on
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
</VirtualHost>

Then the file created for the SSL (port 443) host:

<IfModule mod_ssl.c>
<VirtualHost *:443>
 ServerName sub.example.org
 DocumentRoot /var/www/sub
 DirectoryIndex index.php
 <Directory /var/www/sub/>
 AllowOverride All
 Order Deny,Allow
 Allow from all
 </Directory>
SSLCertificateFile /etc/letsencrypt/live/sub.example.org/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/sub.example.org/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateChainFile /etc/letsencrypt/live/sub.example.org/chain.pem
</VirtualHost>
</IfModule>
  • domain and directory path changed to protect my un-launched service’s identity :)
Ryan Quinn • February 22, 2016

Hey. letsencrypt’s auto option should do this for you so I am guessing it’s possible you do not have the rewrite module enabled. This can be fixed by running sudo a2enmod rewrite; sudo service apache2 restart

I have a fresh LAMP server I ran letsencrypt on the other day with a pretty standard configuration and redirects are working as expected so I’ll just share that config with you.

letsencrypt creates two configuration files if you opt for the redirect http to https option. The first is for the non-https (port 80) host.

<VirtualHost *:80>
 ServerName sub.example.org
 DocumentRoot /var/www/sub
 DirectoryIndex index.php
 <Directory /var/www/sub/>
 AllowOverride All
 Order Deny,Allow
 Allow from all
 </Directory>
RewriteEngine on
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]
</VirtualHost>

Then the file created for the SSL (port 443) host:

<IfModule mod_ssl.c>
<VirtualHost *:443>
 ServerName sub.example.org
 DocumentRoot /var/www/sub
 DirectoryIndex index.php
 <Directory /var/www/sub/>
 AllowOverride All
 Order Deny,Allow
 Allow from all
 </Directory>
SSLCertificateFile /etc/letsencrypt/live/sub.example.org/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/sub.example.org/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateChainFile /etc/letsencrypt/live/sub.example.org/chain.pem
</VirtualHost>
</IfModule>
  • domain and directory path changed to protect my un-launched service’s identity :)
Avinash Jaiswal • May 31, 2018

I have installed SSL manually on my website and configured apache2 virtual host. installation is successful but I am facing issue with redirection. What is it doing, it is combining the .com extention with the directive selected. Can anyone please help me troubleshoot this issue.

Code goes here.

<VirtualHost *:443> ServerAdmin admin@pinnacledu.com DocumentRoot /var/www/html ServerName pinnacledu.com SSLEngine on SSLCertificateFile /etc/ssl/certs/pinnacledu_com.crt SSLCertificatekeyFile /etc/ssl/certs/pinnacledu.com.key SSLCertificateChainFile /etc/ssl/certs/pinnacledu_com.ca-bundle <Directory /var/www/html> AllowOverride All Options FollowSymlinks </Directory> </VirtualHost>

<VirtualHost *:80> ServerName pinnacledu.com Redirect / https://pinnacledu.com/ </VirtualHost>

mahdipedram60 • April 12, 2018

This comment has been deleted

AglaTax • October 14, 2017

This comment has been deleted

Nextoons • September 16, 2017

This comment has been deleted

Nextoons • September 16, 2017

This comment has been deleted

App Platform: Run PHP apps without managing serversProduct

With App Platform, you can:

  • Build, deploy, and scale apps and static sites by simply pointing to your GitHub repository
  • Let us manage the infrastructure, app runtimes, and other dependencies
  • Get started by building and deploying three static sites for free

Related

How to set up my cloud/vps server using Ubuntu 12.04 LTS, Apache, MSQL, Phpmyadmin, PHP
Question
codeigniter PHP App on server. URL returns blank page
Question
App Platform: Run PHP apps without managing serversProduct

With App Platform, you can:

  • Build, deploy, and scale apps and static sites by simply pointing to your GitHub repository
  • Let us manage the infrastructure, app runtimes, and other dependencies
  • Get started by building and deploying three static sites for free