Letsencrypt domain validation requires folder with dot in it like .well-known/acme-challenge but Parse.com hosting's public folder deploy ignores folders with name start with dot char.
Dot character seem to be mandatory for the ACME verification.
Parse.com team should consider supporting folder name with dot to support Letsencrypt. Time being I wish to know any other alternative solution.
This is a odd workaround but might work if Parse.com allows you to issue redirects
Let´s Encrypt client will follow http redirects so you can redirect it to another place which contains the .well-known challenge. You might have to run it in standalone and put challenge by hand at the other place but it will work. You can try to redirect it to S3 bucket on Amazon AWS for instance or to your own PC running a miniserver.
But I don´t know Parse.com and if they support you to configure http redirects.
good luck.
Related
I have purchased a domain name through google domains (e.g. example.com). Separately I have created a website at a third party (wix). I am now trying to connect my domain name to the wix hosted site.
Setting up regular http was trivial: I copied the 2 custom name servers from wix to the DNS name server entries in google domains and then example.com immediately began routing to the wix site.
What are the next steps to setup https so that my domain securely routes to wix?
The help page for google domains states that I can go to Certificate Authority to obtain an SSL certificate, but then where does the certificate information go? In google domains or in wix? If the cert info goes in wix, do I have to change any settings on the google domains side?
Note: I am tyring to avoid doing redirect because I want the website url to always show "example.com", I don't want the address changed by redirect to "example.wix.com" while the user is browsing.
Thank you in advance for your consideration and response.
Eventually https began to redirect properly to wix as well. I was not able to discover the root cause, perhaps it was just a timing issue with DNS.
I have a heroku app hosted at https://rosalinep.herokuapp.com/ that I'm trying to move to the address www.rosalinep.com. (I'm not picky about redirections from rosalinep.com or https vs http, I just want to have this website launched without 'herokuapp' in the url right now.) I used Google Domains to get the domain rosalinep.com, and used the following configurations:
On Google Domains:
synthetic records image
custom resource records image
On Heroku:
domains image
Last night when I first tried to launch this, it worked, but this morning I'm seeing the following error page (which is a total bummer...):
broken website image
Running 'heroku domains' confirms www.rosalinep.com is in the app's custom domains.
I did some searching to try and fix this problem, and it looks like some people in similar situations have reported success in using CNAME like I used, but Heroku's documentation seems to say that an ALIAS or ANAME is necessary for root domain configuration, and those options are apparently not supported by Google Domains.
Because of how Heroku works, they do not release the IP addresses of the apps you create on it, so I can't directly feed it an IP address.
I've gotten pretty stuck and confused in trying to resolve this. Any info on whether I can get this working with Google Domains would be greatly appreciated. Also, if it can be helped, I'd like to not pay for any additional services.
If Google Domains is a non-starter for this though, well, I'm open to other Domain registration websites.
Fixed it! :) After all that, it was just four characters that caused all this headache...
The issue was that in the Google Domains custom resource records section, in the Data field I had 'www.(dns_data_here).com.' when it should have '(dns_data_here).com.'
The site is now up and running on the new url!
Not sure if the title is well suited but I am having three apps (static content) at the moment:
public
app
admin
public is just content which is just for the regular web, app is content which is rendered for mobile devices and admin is basically a tool for administrative stuff. They are all contained in the same Spring Boot application and talk to the REST API at example.com/api. Technically, I could just place them into resources/static such that
resources/static/public
resources/static/admin
resources/static/app
which would allow me to access the apps as such:
example.com/public/index.html
example.com/admin/index.html
example.com/app/index.html
However, my goal is to have the following structure:
example.com // For public
admin.example.com // For admin
app.example.com // For app
example.com/api // REST API
How can this be achieved or what can I do to make this possible?
It sounds like you have three systems: public, admin and app sharing a common REST api. Probably the best approach would be to serve the static resources for each of the three systems using a content delivery network (CDN) like AWS CloudFront or Google Cloud CDN.
Another approach, though less desirable, would be to use a proxy to redirect app requests (for example https://admin.example.com to https://internal-spring-boot-server/admin). You could use Apache mod_proxy with reverse proxy (see https://httpd.apache.org/docs/2.4/mod/mod_proxy.html), or NGNX reverse proxy https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
I think that there are two ways to achieve what you are trying to do you.
Either you will configure your subdomains in your DNS plesk/cpanel/.. to look a specific Document root (The path to the each of your apps home directory.)
for example when someone asks for example.com the request would ask for example.com/main, when someone asks for admin.example.com the request would ask for admin.example.com/admin etc. In this way, you essentially ignoring the subdomain in your Spring app and you manipulate the routes in the #Controller level using the RequestMapping values main/admin/etc..
Alternatively if you don't want to mess with the Provider's control panel, you could follow the steps of this answer. But then you'd have to implement these three custom RequestCondition classes and it may not be the most simple way to go.
Not the best documented answer but I hope I pointed you to the right direction.
I tried to add wildcard domain to my existing app hosting as mysite.herokuapp.com - without a custom domain. The point is it's my test app and application itself allows end users create apps that would be visible as subdomains.
So I configured custom domain and wildcard for main prod app, now I want it to be done for my dev (test) app - so here I need only wildcard but not custom domain. If I try to do it I have "Can't add an additional Heroku domain." What to do to fix it? Is it even possible? Thanks!
UPDATE I have the official answer from Heroku support. It's impossible, I can only add wildcard domain to my custom domain.
Can I use Let's Encrypt to generate SSL Certificate even if I don't own the domain name? The scenario is I have a site that lets user create their own sort of page inside my site which would be a subdomain under my main domain. Now, there's a feature that they can use their own domain name (using a different provider) that will point to the created page on my site so they can use any domain name that they want.
Will I still be able to provide SSL using Let's Encrypt to my user? Note: I'm new at this thing so I am not sure if I am asking the correct question, but I am asking as how I understand it right now.
Yes.
The validation occurs based on HTTP file retrieval or via DNS through TXT records.
I built Greenlock to be able to handle exactly that kind of use case. It will currently work for the scenario that you suggest and I plan to implement more DynDNS support in the future.