https://hapothesis.com works, but www.hapothesis.com doesn't work.
The site is built on Ghost CMS. I guess I could just add an .htaccess file like explained on this thread?
Below are the settings on my registrar and host;
The registrar is Google Domains;
The host is Digital Ocean;
Related
I'm trying to find a current, up to date answer for setting up naked domain with Godaddy and Heroku SSL. My goal is for all pages to land on a secure page at https://www.example.com
https://www.example.com does go to a secure page.
example.com goes to an insecure page.
https://example.com does not work.
My current set up is as follows:
In heroku settings:
Domain Name | DNS Target
example.com | example.com.herokudns.com
www.example.com | www.my-domain.herokudns.com
Go Daddy Settings:
CNAME | www | www.example.com.herokudns.com
Forwarding settings:
Forward to: https:// | www.example.com
Yeah, it's a pretty stupid issue that some of the big DNS manager providers out there still have. The way to solve it is to have a server with an SSL certificate installed, and then point your naked domain to that static IP. The server then will redirect to the "www" version of your domain, which is now served under SSL by Heroku. Tedious.
If you don't want to do all that, just use https://www.nakedssl.com, which does exactly that – but automated (and for free for one domain).
Disclaimer: I'm part of the team that created NakedSSL, but I hope you take this as help and not as self-promotion. As explained above, the problem is as easy as tedious to solve, and I think NakedSSL is a pretty straight forward workaround.
Root domains on Heroku require the use of ALIAS ANAME or FLATTENING records.
Unfortunately, a number of popular DNS hosts such as GoDaddy, Bluehost, Google Domains, OVH, Hostinger and others do not support these types of records. Many of these Providers will tell you there is no such thing as ALIAS, ANAME or FLATTENING Records and many of these providers will tell you to set an A Record instead, however;
A Records do not work with Heroku for routing
A Records require static IP Addresses and static IP Addresses do not work with Heroku for routing, because Heroku (and many other cloud platforms) use dynamic IP's.
Instead, you can either:
Not use a naked domain and just use your www sub domain
Redirect/ Forward your HTTP root domain to your www sub domain. This won't work for your HTTPS root domain though
Use an Alternate DNS Provider. Heroku recommends the following: https://help.heroku.com/NH44MODG/my-root-domain-isn-t-working-what-s-wrong
Solved it.
Best way to get SSL set up is to use this package which automatically makes every page on your app SSL. Fantastic package. https://www.npmjs.com/package/force-ssl-heroku
Getting the naked domain set up with Godaddy easily: Set forwarding to your domain: https://www.my-domain.com. This will redirect non www to the correct place. :)
I believe naked subdomain or wildcards are not supported by heroku automated certs because of the let's encryption restrictions. So you need to set up a subdomain everytime you want to use Heroku's automatic certs.
ALSO VERY IMPORTANT! Don't forget to remove or edit any unsercured links to external assets. Otherwise browsers will jugde the page with those links unsecured as described in the Modzilla support page about mixed content.
I have my domain pointed in Cloudflare with SSL. My website runs with HTTPS protocol. The reason i mention them running is this.
I have my blog at blogspot and want to give it custom domain name which google allows. Unfortunately google wont allow HTTPS there. I had created my blog like this in DNS as blog.domain.com which runs as https://blog.domain.com and if i host this subdomain via Github, it opens correctly. The problem is when i use this subdomain in blogger, then there arises conflict and my site goes offline. Where am i mistaking in setting up all this?
Don't enable full or restricted SSL option in cloudflare. Use flexible SSL instead. This will setup things correctly.
I have many domains with different extensions, for example: website.com, website.net, website.org,...
the main site/domain is website.com where I have installed WORDPRESS
what I'm tring to do is to set all the others domain (website.net, website.org,..) to point on the main site/domain (website.com)
so, for example, if I go on "website.net" or "website.net/something" should I be redirect on website.com
I have cpanel so i guess that the first way is to add all the domains with the "addon domains" function, and then add in the wp-config.php:
define( 'NOBLOGREDIRECT', 'http://website.com' );
or another soluzion could probably be to simply park all the domains with cpanel function, or se the htaccess, but how?
what is the best solution in this case?
PS: the main website is in a subfolder (not root)
Just do a DNS forward and be done with it. Go to your DNS provider and just setup domain forwarding to your main domain name.
Forward website.net and website.org to website.com. When anyone goes to website.net it will redirect to website.com and same with .org. The domains will need to be parked.
If you host your DNS at a registrar like GoDaddy, then this will show you how.
http://support.godaddy.com/help/article/422/forwarding-or-masking-your-domain-name
Otherwise, the procedure is the same wherever your DNS is hosted. I suggest forwarding it without masking.
I've got the following problem. We have a SSL-certificate for a domain with a prepended 'www', like 'www.test.com'.
I've integrated that certificate with Plesk for this domain and it works fine, when somebody goes directly to 'www.test.com'. But when I enter only 'http://test.com', he won't recognize the certificate and shows a warning. How can I prevent this? Do I need an extra certificate (hope not) or can I redirect the domain within Plesk directly. A PHP-header isn't enough, because the redirection would take place after the browser tries to establish the ssl-connection.
And because the Plesk admin panel runs on this same domain, we have the same problem with 'http://test.com:8443' …
So basically:
'https://www.test.com' - fine
'https://test.com' - not working
'https://www.test.com:8443' - fine
'https://test.com:8443' - not working
Any suggestions would be nice, thanks a lot,
Carl
Try adding a this rule to .htaccess in the public root. It should redirect from test.com to www.test.com for SSL connections:
RewriteRule ^/(.*):SSL$ https://www.test.com/$1 [R,L]
Learn more about htaccess redirects
Typically, the certificate needs to be purchased for specific subdomain. Some Certificate Issuers do offer a cert for the .test.com domain that includes all subdomains (including test.com and www.test.com). If you're unsure, you should contact your certificate issuer directly.
Well first what plesk version with which OS you have, It's Linux or windows if Windows to Add reWrite URL in IIS setting on under particular.
If you have Linux with plesk any version because it's not matter either you have plesk or cpanel.
with Linux
Add ReWrite module in .htaccess for domain purpose only not for access plesk panel with specific port 8443
8443 port only configured with plesk shared license.
Use follow to avoid Trusted message
https://www.test.com - fine
https://test.com' - not working
in this case use URL rewrite redirection as above said steps.
=============================
Check Cname Entry in particular domain DNS record.
I hope this helps.
I'm looking to figure out how to replicate the functionality of GoDaddy's PreviewDNS when I'm moving a site to my own web host based in cpanel.
My setup is this: I have a wordpress multiuser site setup with a subdomain install, and a wildcard redirect.
I can't figure out how I can preview the website for an account before the DNS is switched over to my host from the old host.
I've been able to sorta do this by creating an A record of a subdomain over to my host, but I still have the issue of not being able to test the actual files instead of a copy in a subdomain.
I have two IP addresses attached to the server, one to the server itself and all the shared domains, and the other dedicated to the WP multisite.
When I go to http://ipaddress/~username/, I either get an error, or get redirected to the wordpress multisite's default "this site doesn't exist, sign up now to create it" page. I've tried this with both IP addresses with no avail.
Any ideas?
I think what you're trying to do is ensure that everything is working on the new server before having the DNS globally changed for all users? You could change your local computers hosts file to point the domain (and any subdomains you wish to test) over to the new dedicated IP address, which is essentially moving the DNS over for just yourself.
Here's a pretty good guide on how to do it: http://www.howtogeek.com/howto/27350/beginner-geek-how-to-edit-your-hosts-file/