So I am getting this odd issue which is only on my one heroku instance. I have an rails/devise app deployed to heroku with a custom domain, and when I go to log in, it redirects to the herokuapp domain and not the custom domain. All other urls, links stay on the custom domain but anytime authentication is checked it redirects to the herokuapp domain. Is there something missing? Thanks in advance.
Related
My hosting company has implemented SSL on my account. It is a multi-site Drupal setup and the sites that are accessed directly via my domain registrar (Hover) are working correctly but one site doesn't ... the problem for that site appears to be that I forward that domain to FastMail to manage some email and from there I forward the domain to the web host. I get the domain name is not secure and this message: NET::ERR_CERT_COMMON_NAME_INVALID
Does anyone know how to change the configuration?
Thanks for the feedback however my host service was unable to set the site to use ssl because it went via a 3rd party mail server.
I have a Heroku app and am using a custom subdomain to point to it. Let's say my subdomain is blog.mysite.com.
When I navigate to the site, chrome throws the error: ERR_SSL_PROTOCOL_ERROR. In the address bar, it automatically reroutes to https://blog.mysite.com. Is this the issue? Why is it not just http://blog.mysite.com?
My domain is through bluehost if that matters.
If you are running a free dyno, you will not get TLS support on your custom subdomain. Upgrade it to at least the "Hobby" tier and it will provision a free certificate to match your custom subdomain.
As for why it automatically reroutes, that's something happening within your application or custom process configuration. Heroku doesn't automatically re-route from http to https.
For me, I'd neglected to set up Automated Certificate Management in Heroku. Enabling this fixed the problem.
So I inherited a domain for a client that has the same internal/external domain name (Server 2012r2). This caused a problem for users inside the domain trying to reach the external site.
After some research I decided to create an IIS redirect to the external website/IP, to enable people inside the domain to reach the external website. This worked just fine.
Basically did what is at this link: http://oddjobsintech.com/active-directory-tip-access-external-website-with-the-same-domain-name-as-your-internal-domain/
Basically, just created a www A record and installed IIS on domain controllers with HTTP redirect to the external site.
However, now they've acquired an SSL cert from GoDaddy, and I installed on the external webserver, which works perfectly fine outside of the domain. But once again, internally if you try to type "https:" the same issue with the page not resolving properly shows up.
Anybody know why this is and/or a possible fix (other than renaming the domain)?
An Domain Controller is the hearth from every Microsoft Active Directory environment and Microsoft did a lot to prevent the access to it like written here:
Domain controllers, by default, restrict the types of user accounts
that have the ability to log on locally. By default, only members of
the Account Operators, Administrators, Backup Operators, Print
Operators, and Server Operators groups have the Allowed logon locally
system right.
So you shouldn´t install an IIS on an domain controller. If the IIS will he hacked, the hacker has direct access to the whole domain!
According to your issue I would check the DNS environment if it is configured correctly.
I would like to make my azure web site as https enabled one. As exactly like https://mysite.azurewebsites.net. Though I have uploaded my SSL certificate in certificate section in web site configuration tab its not redirecting automatically. Is there any other settings I have to enable?
Appreciate your help.
So to clarify the sequence of steps:
After you configure your custom domain properly, then h_ttp://customdomain.com will point to mysite.azurewebsites.net.
After you bind an SSL certificate to a custom domain in a web app, then h_ttps://customdomain.com will point to mysite.azurewebsites.net, using the bound SSL cert. If you still can't access h_ttps://customdomain.com, then you need to check whether you've configured your domain records properly at the domain registrar.
At this point, h_ttp://customdomain.com will continue to work. If you want to enforce HTTPS for your web app, see http://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/#bkmk_enforce.
I am now managing a web service site as herokuapp.com domain name with Piggyback SSL.
And I am planning to migrate from the herokuapp domain to custom domain with custom SSL.
Here is a question,
Is it possible to use herokuapp.com domain name even after we set up custom domain SSL and get a SSL endpoint as herokussl.com domain?
Does anyone have experience of using both domains?
Thanks,
Masahiro
It should work fine.
Because you're only pointing your custom DNS entry at the SSL endpoint eg tokyo-2121.herokussl.com then the original herokuapp.com and ssl will still be accessible provided you're not doing any kind of domain checking and redirection in your code.