Search the Community
Showing results for tags 'ssl'.
Found 13 results
-
Hi, We copied the production source and configured it the same as the development source on the localhost. However, the website is not working on the localhost, whereas it is working fine on the production source. Please find the error attached. FYI - we have SSL for the production environment. Can anyone kindly help resolve this issue? Thank you
-
Hi there, I added a ssl certificate to my site and I'd like to redirect every single http url to its new https version So I added this code in the .htacces file, after the RewriteEngine On : Redirect 301 /about https://www.mysite.it/about Unfortunately this is now working: I get the "too many redirects" error. The following code works, but it's a bulk redirection to the home page, something I don't want for SEO reasons (https://moz.com/blog/save-your-website-with-redirects? RewriteCond %{HTTP_HOST} mysite\.it [NC] RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.mysite.it/$1 [R,L] Any suggestions?
-
Hi all, Just a quick question, when using the multisite module is there anything different that needs to be done in order to setup HTTPS for each of the domains its serving? Would a single SSL certificate for the main domain be enough to cover the others aswell or would you need multiple ceritficates one for each domain the mutlisite setup uses?
-
So, all of a sudden, Chrome is blocking all of my localhost sites, claiming my connection is not Private, blah blah..Here is the full text of what Chrome is telling me. I get no option to 'continue to this unsafe site'. It seems I have no option but to install SSL on my local sites. I have seen some articles on how easy it is to do in a Mac but I am on Windows. Anyone has pointers on how I can do this? Alternatively, anyone knows what this Chrome error is about? Bottom line is, unless I change browsers, I am not currently able to develop and test stuff locally. Grr! Thanks.
-
I think I've been through every GoDaddy related post on the forum but not had any success so far with this. Basically, a client's site started to throw various errors after a failed SSL install by their host. Accessing https://www.domain.com results in an error and a redirect to https://www.domain.not/cgi-sys/defaultwebpage.cgi Accessing http://www.domain.not gives a blank 500 page Im happy to side step the SSL issue at the moment if I could get the site up. I'm pretty sure it's a .htaccess issue as adding "blahdhdgdgd" to the start of the .htaccess file results in an "internal Server Error" Tried every .htaccess tweak I could find to no avail. Even restored an older .htaccess file from last week before the SSL issue doesn't work. It's a "real doozy", this one
-
I've noticed that the processwire.com website runs over SSL, but i also noticed that visiting the websites over http still works, and once using the insecure version the links are also relative pointing to non-ssl links. As a fix there could possibly add an auto redirect to the HTTPS site? This could potentially then take advantage of HTTP/2 speed.
-
Hello community, This is the first time I have enabled SSL with PW powered site so forgive the question. Templates are set to HTTP or HTTP so content is being processed. However all the assets do not load correctly eg. Failed to load resource: the server responded with a status of 404 (Page Not Found) https://site.com/site/assets/files/1/logo.png Any tips? Thank you!
-
Now that CloudFlare has free Universal SSL, I'd like to serve my site over https:// What is the recommended PW approach to do this? Is it just a matter of tweaking the .htaccess file to force https:// ? If so, how would I go about it? With one little tweak -- adding an "s" to the force "www." rewrite rule -- I can successfully redirect from http://domain.com to https://www.domain.com: RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] But how should I deal with the second scenario: redirecting from http://www.domain.com to http s://www.domain.com? Everything I've tried ends up in a redirect loop.
-
When installing ProcessWire out of the box (Softaculous), there is one minor mistake in making it truly https friendly. site/templates/_main.php - the http: has to be removed in order to load the google font accordingly to the site setup https/http. <head> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <title><?php echo $title; ?></title> <meta name="description" content="<?php echo $page->summary; ?>" /> <link href='http://fonts.googleapis.com/css?family=Lusitana:400,700|Quattrocento:400,700' rel='stylesheet' type='text/css' /> <link rel="stylesheet" type="text/css" href="<?php echo $config->urls->templates?>styles/main.css" /> </head> Great product! Continue the brilliance.
- 7 replies
-
- 3
-
-
- https
- out of the box
- (and 2 more)
-
We have installed an SSL certificate on our server for the domain its running on. There are several pages in the website that have user input like a form. How can i force that those pages only be accessable on https:// So that direct access to those URLs or links to the URL automaticly be redirected to https:// instead of http://
-
Hallo! I'd like to force SSL (port 443) for the back-end (./processwire/) and prevent the users from loging to the back-end using non-encrypted connection. What seems to be the best way to achieve it? Best regards, Mick
-
I tried to update one of my websites from 2.3.8 to 2.3.9 and noticed a problem. I'm using some contact forms, which templates are set up to use ssl only. The other templates are configured to use http only. If I'm moving back from ssl to non-ssl pages in frontend, I get the following error: "Moved Permanently The document has moved here." URL of this page shown in browser is like: http://www.mydomain.com:443/mypage/ (should be for sure: http://www.mydomain.com/mypage) It worked with 2.3.8, so I suppose the problem is somewhere in the file "/wire/core/ProcessWire.php", in function "getHttpHost(Config $config)" - this is one of the places of which "diff -r" is telling me that is has be changed between 2.3.8 and 2.3.9. -
I have a site that uses just one page for a checkout and as such it also uses SSL. However, after a user navigates away from the page, they are still viewing the site in https. Does anyone know how to set it so that they are in http after leaving that one page? Also, I screwed up when I set up the SSL certificate by using a naked domain name. So in my htaccess I set up this to correct it: # Allow form payment # RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^contact https://foo.com/application-payment/ [R=301,L]
