I configured my domain with Heroku and PointDNS but when trying it, deepdao.world, or www.deepdao.world, the result is
403 Forbidden You don't have permission to access / on this server.
This is my PointDNS setup:
The domain works with heroku.deepdao.world, but not without heroku. What am I missing?
EDIT: screenshots of my setup in domain.com:
Related
I have a heroku app set up on a .app TLD, and a custom domain through GoDaddy.
What I would like is to have something like this:
myapp.example.com resolves to my app, and does not redirect.
What I am currently experiencing is:
myapp.example.com redirects (with a 307) to my-example-app.herokuapp.com
What I have done:
Following the Heroku guide for custom domains, I've done heroku domains:add myapp.example.com -a my-example-app and also added a cname to though the Godaddy UI for my domain.
CNAME myapp some-heroku-dns-somehash.herokudns.com
Any help, advice or pointers would be appreciated.
Edit: The 307 redirect is just due to the app redirecting to /sign-in. The issue that I am trying to resolve is using the custom domain, and not the heroku domain.
The 307 redirect is just due to the app redirecting to /sign-in.
This causes me to think that your application thinks it should build URLs using the Heroku domain instead of the custom domain.
Does your application have a place where its domain is configured? You might just need to update that setting so it can build own URLs using the proper domain.
I have bought a domain name with Porkbun.com, I have added that domain to my herokuapp domains and received a DNS target. I have added an ALIAS record with host: 'mywebsite.domain' and target as the DNS target I received from Heroku.
When trying to access the domain I get 'bad Request (400)' error. I have then tried these three separate steps:
As instructed by Porkbun I added another ALIAS record with host: www.mywebsite.domain and target: 'mywebsite.domain'.
I deleted all the ALIAS records I had and added a CNAME record with host: 'www.mywebsite.domain' and target: 'mywebsite.herokuapp.com'.
Changed CNAME target to be the DNS record I received from Heroku.
In the three cases I receive a Heroku page saying 'There is nothing here' and titled 'no such app'.
Similar problem occurred to me yesterday when i tried to deploy a ghost app to heroku pointing to a custom domain name purchased through porkbun. After googling i found out that the IT TAKES ALMOST A DAY TO RESOLVE THE DNS POINTING TO THE CUSTOM DOMAIN in porkbun.
Solution
I changed the CNAME RECORD pointing to the herokuapp url;-"yourappname.heruko.com"
Add the host as WWW
You can also use ALIAS-CNAME RECORDING to point to the heroku app url.
heroku domains:add example.com
heroku domains:add www.example.com
heroku domains:add *.example.com
This is to point your domain name from heroku side
Check out this video its about connecting your domain name to godaddy. I think its the same way with porkbun youtube.com/watch?v=kKGSGT7mSnQ&t=75s
Please let me know if this does work for you
I have an app created on Heroku and I added subdomain to it:
some.page.example.com
www.some.page.example.com
Then, according to this, I've pointed these names to proper Heroku names with my DNS provider like this:
some.page.example.com CNAME some.page.example.com.herokudns.com
www.some.page.example.com CNAME www.some.page.example.com.herokudns.com
I'd like to serve this page under http, apparently Heroku internally redirects traffic to https - it returns 301 when trying to access page via http. Of course finally it fails (e.g. ERR_SSL_PROTOCOL_ERROR in Chrome or SSL_ERROR_INTERNAL_ERROR_ALERT in Firefox), after redirecting, beacuse there is no certificate set up on this Heroku app.
How can I prevent Heroku from doing this?
P.S. What's funny, I have other site on Heroku, with root domain pointing to this, and it works like a charm. :/
I followed every instructions from this site Google Dev Console site
and my web app was working well in http://localhost. No issues.
Now I deployed the web app in the AWS-EC2 server. I also added the Javascript Origins to show my 'subdomain.domain.com'. Upon hitting the button 'Google Login' from webapp on subdomain.domain.com, the google-authentication is not working ; shows the below error, where XX.YY.ZZ.AA is my AWS EC2 instance IP;
Error: invalid_request
Permission denied to generate login hint for target domain.
Request Details
redirect_uri=storagerelay://http/XX.YY.ZZ.AA?id=auth736964
response_type=permission id_token scope=email profile openid
openid.realm=
client_id=625394219770-q0qilkfl05m2fortt25j2j63e2dn6c1r.apps.googleusercontent.com
ss_domain=http://XX.YY.ZZ.AA fetch_basic_profile=true gsiwebsdk=2
That’s all we know.
I am asking for help on how to resolve this. Is it a EC2 forward issue, because the google error is not showing my subdomain.domain.com instead EC2-ip address. or something else?
I have set up a Parse Server on Heroku, with an MLab MongoDB. Everything works fine, & when I visit https://myapp.herokuapp.com I see "Make sure to star the parse-server repo on GitHub!".
I can successfully perform API functions through my Postman Console, for example logging in via the following REST API call: https://myapp.herokuapp.com/parse/login?username=admin&password=password.
I can also perform other REST API POST, GET, etc. as you would expect.
I'm now trying to use my own domain "api.mydomain.net". In the Heroku App > Settings > Custom Domains, I have set domain to "api.mydomain.net" & "myapp.herokuapp.com" as the DNS target.
I've also added a CNAME record to the DNS pointing "api" to "myapp.herokuapp.com".
When I visit https://api.mydomain.net I see the "Make sure to star the parse-server repo on GitHub!" message confirming that the CNAME record works, however when I go to perform the same REST API Login call https://api.mydomain.net/parse/login?username=admin&password=password I get the response:
Could not get any response.
This seems to be like an error connecting to
https://api.mydomain.net/parse/login?username=admin&password=password.
What am I missing?
You are trying to securely connect to the Parse Server with https. So you have to add a TSL certificate for your Heroku app in the Heroku dashboard.
Open Heroku app in Heroku dashboard
Open Settings tab
In section Domains and certificates click Configure SSL and choose Automatically configure using Automated Certificate Management.
Click Add domain to add the domain from which the request should be forwarded, e.g. api.example.com.
On your domain registrar's website set the CNAME for api.example.com to the domain in the Heroku app settings, e.g. api.example.com.herokudns.com
Wait until the status of the domain in the Heroku dashboard is Done