About ssl certificate and https://

franciccio-ITALIANO · May 7, 2019

Hi, I install processwire by softeiaculos because manually there was any problem.
But now the format https:// it's not active.
Is an simple http://mysite.com

How I can change it? The certificate is installed on server!

Thanks...

gmclelland · May 7, 2019

You should be able to change it in your .htaccess file. Look at section #9 in the file.

pwired · May 7, 2019

Quote

How I can change it? The certificate is installed on server!

Hi Franciccio,

The only part in Processwire you need to do is to uncomment 2 lines in the .htaccess file:

# -----------------------------------------------------------------------------------------------
  # 9. If you only want to allow HTTPS, uncomment the RewriteCond and RewriteRule lines below.
  # -----------------------------------------------------------------------------------------------
    RewriteCond %{HTTPS} off
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

The rest is done on your hosting server.

Many Hosters these days have an easy Let's Encrypt setup in their CPanel.
Unless your Hosting is Godaddy. I had a hard time not so long ago with Godaddy's support.
They conduct a very demotivational policy to let you setup Let's Encrypt.

rick · May 7, 2019

9 minutes ago, pwired said:

Many Hosters these days have an easy Let's Encrypt setup in their CPanel.

Even if you do it manually (depending on your host), the cron setup is simple. Letsencrypt does a good job of covering the bases.

franciccio-ITALIANO · May 13, 2019

Hi, I remove "#" and now the site is "INTERNAL SERVER ERROR - Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request"

RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

So, I re-put #

# RewriteCond %{HTTPS} off

# RewriteCond %{HTTPS} off RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

BUT NOW THE SITE IS ALWAYS "INTERNAL SERVER ERROR". All white.
It's autodistruct.

I don't understand.
How can I take the version precedent htpaccess?

franciccio-ITALIANO · May 13, 2019

My htaccess file is this:

#################################################################################################
# START PROCESSWIRE HTACCESS DIRECTIVES
# @version 3.0
# @indexVersion 300
#################################################################################################

# -----------------------------------------------------------------------------------------------
# 1. Don't show directory indexes, but do follow symbolic links
# 500 NOTE: Some cloud hosting companies don't allow +SymLinksIfOwnerMatch.
# Uncomment +SymLinksifOwnerMatch and comment +SymLinksIfOwnerMatch if you have 500 errors.
# If that doesn't resolve the error, then set it back to +SymLinksIfOwnerMatch.
# -----------------------------------------------------------------------------------------------

Options -Indexes
Options +SymLinksIfOwnerMatch
# Options +SymLinksifOwnerMatch

# -----------------------------------------------------------------------------------------------
# 2. Let ProcessWire handle 404s
# -----------------------------------------------------------------------------------------------

ErrorDocument 404 /index.php

# -----------------------------------------------------------------------------------------------
# 3. Handle request for missing favicon.ico/robots.txt files (no ending quote for Apache 1.3)
# -----------------------------------------------------------------------------------------------

<Files favicon.ico>
ErrorDocument 404 "The requested file favicon.ico was not found.
</Files>

<Files robots.txt>
ErrorDocument 404 "The requested file robots.txt was not found.
</Files>

# -----------------------------------------------------------------------------------------------
# 4. Protect from XSS with Apache headers
# -----------------------------------------------------------------------------------------------

<IfModule mod_headers.c>
# prevent site from being loaded in an iframe on another site
# you will need to remove this one if you want to allow external iframes
Header always append X-Frame-Options SAMEORIGIN

# to prevent cross site scripting (IE8+ proprietary)
Header set X-XSS-Protection "1; mode=block"

# prevent mime-based attacks via content sniffing (IE+Chrome)
# Header set X-Content-Type-Options "nosniff"
</IfModule>

# -----------------------------------------------------------------------------------------------
# 5. Protect ProcessWire system files
# -----------------------------------------------------------------------------------------------

# -----------------------------------------------------------------------------------------------
# 6. Override a few PHP settings that can't be changed at runtime (not required)
# 500 NOTE: Try commenting out this entire section below if getting Apache 500 errors.
# -----------------------------------------------------------------------------------------------

<IfModule mod_php5.c>
php_flag magic_quotes_gpc       off
php_flag magic_quotes_sybase       off
php_flag register_globals       off
</IfModule>

# -----------------------------------------------------------------------------------------------
# 7. Set default directory index files
# -----------------------------------------------------------------------------------------------

DirectoryIndex index.php index.html index.htm

# -----------------------------------------------------------------------------------------------
# 8. ProcessWire requires mod_rewrite
# -----------------------------------------------------------------------------------------------

RewriteEngine On
AddDefaultCharset UTF-8

# -----------------------------------------------------------------------------------------------
# 9. If you only want to allow HTTPS, uncomment the RewriteCond and RewriteRule lines below.
# -----------------------------------------------------------------------------------------------

# RewriteCond %{HTTPS} off
# RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# If using an AWS load balancer, use these two lines below instead of those above:
# RewriteCond %{HTTP:X-Forwarded-Proto} =http
# RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# -----------------------------------------------------------------------------------------------
# 10. Set an environment variable so the installer can detect that mod_rewrite is active.
# Note that some web hosts don't support this. If you get a 500 error, you might try
# commenting out this SetEnv line below.
# -----------------------------------------------------------------------------------------------

<IfModule mod_env.c>
SetEnv HTTP_MOD_REWRITE On
</IfModule>

# -----------------------------------------------------------------------------------------------
# 11. OPTIONAL: Set a rewrite base if rewrites aren't working properly on your server.
# And if your site directory starts with a "~" you will most likely have to use this.
# -----------------------------------------------------------------------------------------------

# RewriteBase /
# RewriteBase /pw/
# RewriteBase /~user/

# -----------------------------------------------------------------------------------------------
# 12. Access Restrictions: Keep web users out of dirs that begin with a period,
# but let services like Lets Encrypt use the webroot authentication method.
# -----------------------------------------------------------------------------------------------

RewriteRule "(^|/)\.(?!well-known)" - [F]

# -----------------------------------------------------------------------------------------------
# 13. OPTIONAL: Redirect users to the 'www.' version of the site (uncomment to enable).
# For example: http://processwire.com/ would be redirected to http://www.processwire.com/
# -----------------------------------------------------------------------------------------------

# RewriteCond %{HTTP_HOST} !^www\. [NC]
# RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

# -----------------------------------------------------------------------------------------------
# 14. OPTIONAL: Send URLs with non-ASCII name-format characters to 404 page (optimization)
# -----------------------------------------------------------------------------------------------

# RewriteCond %{REQUEST_URI} "[^-_.a-zA-Z0-9/~]"
# RewriteCond %{REQUEST_FILENAME} !-f
# RewriteCond %{REQUEST_FILENAME} !-d
# RewriteRule ^(.*)$ index.php?it=/http404/ [L,QSA]

# -----------------------------------------------------------------------------------------------
# 15. Access Restrictions: Protect ProcessWire system files
# -----------------------------------------------------------------------------------------------

# Allow screenshot files (for install.php only: this 1 line below may be removed after install)
RewriteCond %{REQUEST_URI} !(^|/)site-[^/]+/install/[^/]+\.(jpg|jpeg|png|gif)$
# Block access to any htaccess files
RewriteCond %{REQUEST_URI} (^|/)\.htaccess$ [NC,OR]
# Block access to protected assets directories
RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets/(cache|logs|backups|sessions|config|install|tmp)($|/.*$) [OR]
# Block acceess to the /site/install/ directory
RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/install($|/.*$) [OR]
# Block dirs in /site/assets/ dirs that start with a hyphen
RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets.*/-.+/.* [OR]
# Block access to /wire/config.php, /site/config.php, /site/config-dev.php, and /wire/index.config.php
RewriteCond %{REQUEST_URI} (^|/)(wire|site|site-[^/]+)/(config|index\.config|config-dev)\.php$ [OR]
# Block access to any PHP-based files in /templates-admin/
RewriteCond %{REQUEST_URI} (^|/)(wire|site|site-[^/]+)/templates-admin($|/|/.*\.(php|html?|tpl|inc))$ [OR]
# Block access to any PHP or markup files in /site/templates/
RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/templates($|/|/.*\.(php|html?|tpl|inc))$ [OR]
# Block access to any PHP files in /site/assets/
RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/assets($|/|/.*\.php)$ [OR]
# Block access to any PHP files in core or core module directories
RewriteCond %{REQUEST_URI} (^|/)wire/(core|modules)/.*\.(php|inc|tpl|module|info\.json)$ [OR]
# Block access to any PHP files in /site/modules/
RewriteCond %{REQUEST_URI} (^|/)(site|site-[^/]+)/modules/.*\.(php|inc|tpl|module|info\.json)$ [OR]
# Block access to any software identifying txt files
RewriteCond %{REQUEST_URI} (^|/)(COPYRIGHT|INSTALL|README|htaccess)\.(txt|md|textile)$ [OR]
# Block all http access to the default/uninstalled site-default directory
RewriteCond %{REQUEST_URI} (^|/)site-default/
# If any conditions above match, issue a 403 forbidden
RewriteRule ^.*$ - [F,L]

# PW-PAGENAME
# -----------------------------------------------------------------------------------------------
# 16a. Ensure that the URL follows the name-format specification required by PW
# See also directive 16b below, you should choose and use either 16a or 16b.
# -----------------------------------------------------------------------------------------------

RewriteCond %{REQUEST_URI} "^/~?[-_.a-zA-Z0-9/]*$"

# -----------------------------------------------------------------------------------------------
# 16b. Alternative name-format specification for UTF8 page name support.
# If used, comment out section 16a above and uncomment the directive below. If you have updated
# your $config->pageNameWhitelist make the characters below consistent with that.
# -----------------------------------------------------------------------------------------------

# RewriteCond %{REQUEST_URI} "^/~?[-_./a-zA-Z0-9æåäßöüđжхцчшщюяàáâèéëêěìíïîõòóôøùúûůñçčćďĺľńňŕřšťýžабвгдеёзийклмнопрстуфыэęąśłżź]*$"

# END-PW-PAGENAME
# -----------------------------------------------------------------------------------------------
# 17. If the request is for a file or directory that physically exists on the server,
# then don't give control to ProcessWire, and instead load the file
# -----------------------------------------------------------------------------------------------

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !(favicon\.ico|robots\.txt)

# -----------------------------------------------------------------------------------------------
# 18. OPTIONAL: Prevent ProcessWire from attempting to serve images or anything in /site/assets/.
# Both of these lines are optional, but can help to reduce server load. However, they
# are not compatible with the $config->pagefileSecure option (if enabled) and they
# may produce an Apache 404 rather than your regular 404. You may uncomment the two lines
# below if you don't need to use the $config->pagefileSecure option. After uncommenting, test
# a URL like domain.com/site/assets/files/test.jpg to make sure you are getting a 404 and not
# your homepage. If getting your homepage, then either: do not use this option, or comment out
# section #2 above that makes ProcessWire the 404 handler.
# -----------------------------------------------------------------------------------------------

# RewriteCond %{REQUEST_FILENAME} !\.(jpg|jpeg|gif|png|ico)$ [NC]
# RewriteCond %{REQUEST_FILENAME} !(^|/)site/assets/

# -----------------------------------------------------------------------------------------------
# 19. Pass control to ProcessWire if all the above directives allow us to this point.
# For regular VirtualHosts (most installs)
# -----------------------------------------------------------------------------------------------
RewriteRule ^(.*)$ index.php?it=$1 [L,QSA]

# -----------------------------------------------------------------------------------------------
# 20. If using VirtualDocumentRoot (500 NOTE): comment out the one above and use this one instead
# -----------------------------------------------------------------------------------------------
# RewriteRule ^(.*)$ /index.php?it=$1 [L,QSA]

</IfModule>

#################################################################################################
# END PROCESSWIRE HTACCESS DIRECTIVES
#################################################################################################

# SP BEGIN php handler
<IfModule mod_fcgid.c>
AddHandler fcgid-script .php .php5 .php7 .phtml
FcgidWrapper /usr/local/cpanel/cgi-sys/sp-ea-php56 .php
FcgidWrapper /usr/local/cpanel/cgi-sys/sp-ea-php56 .php5
FcgidWrapper /usr/local/cpanel/cgi-sys/sp-ea-php56 .php7
FcgidWrapper /usr/local/cpanel/cgi-sys/sp-ea-php56 .phtml
</IfModule>
# SP END php handler

franciccio-ITALIANO · May 13, 2019

But it's wrong in anything because my site don't work...

Help meeeeeeeeee pleaseeeeeeeeeeeeee

Ivan Gretsky · May 14, 2019

@franciccio-ITALIANO, is there a direct link to your site? Could you post it for testing?

franciccio-ITALIANO · May 14, 2019

Certo, grazie. Una pagina del mio sito: http://permaculturaorganica.info/manifesto-sovranista/

I think that now I must disinstall all and reinstall... and forgo renounce https because the htaccess file is untouchable, it smash immediately...

wbmnfktr · May 14, 2019

Rename the old htaccess file and just add a fresh copy from the Github repository.

franciccio-ITALIANO · May 14, 2019

ok, but on github there is a htaccess.txt file text, I must change the extension, no?

I delete old file and create a new with name ".htaccess", then I cut-copy the body of htaccess on gothub, but not work anything. It is a drama unsolvable.
So, I must disinstall all the site.

I suggest that all readers never touch the processwire htaccess file again. It is not a normal file. You can't change a comma and put it back, because even if you put it back where it was, it's like you've written something completely new and different. Madness.

wbmnfktr · May 14, 2019

On Github is a .txt file, that correct. But its content should work just fine.

NEVER delete a file you might need again. Especially while debugging.

So as the new .htaccess doesn't as well... what were the last changes you made?
Did you install or change files aside from .htaccess?
Did you move folders?
Did you enable anything in your hosting panel?

It seems you tried to install SSL.
How did you do that?
Via hosting panel?
Manual cert files or something similar?

One change in the .htaccess can potentially break everything but it can always be reversed.

franciccio-ITALIANO · May 14, 2019

In my hosting pannell I haven't change anything because the server staff tell me that the application of ssl certificate was AUTOMATIC. Infact it work very well in a subdomain wordpress, and I don't do absolutely nothing.
But the ssl certificate Lets Encript is turn ON on my site from 9 months.
Yesterday I think about application it in first major principal domain processwire and so I ask informations here.

I open .htaccess by FILEZILLA and I remove 2 "#".
Stop.
All distruct.
Ok, I put back the 2 "#" and always all smash.

I haven't change anything neither in processwir panel.

Anyway, thank you very much for your help!

LostKobrakai · May 15, 2019

If this is a managed hosting and even a fresh .htaccess doesn't work contact the hoster to fix the issue. If it's not managed locate the logs for the apache server and see what it tells you.

franciccio-ITALIANO · May 16, 2019

So, I uninstall and reinstall the site.

I discover the problem.
I try to modify and remove i 2 "#" by pannell hosting, NOT BY FILEZILLA.

Now, my site work very well with certificate https://.

My personal lesson: NOT USE FILEZILLA FOR TO EDIT FILES!

Sign In

About ssl certificate and https://

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members