I recently upgraded from free account to hobby account on heroku by using following command:
heroku ps:resize web=hobby
The I enabled the automated certificate management with following command:
heroku certs:auto:enable
after waiting a couple of hours i decided to run:
heroku certs:auto
and according to my status description it's running ok.
I even ran the following command:
curl -vI https://www.yaknchat.com
which tells me my server certification verification is OK.
However, when i enter https://www.yaknchat.com in the browser it tells me "this connect is not FULLY secure" as opposed to the usual response "this connect is not secure".
I'am doing something wrong. Should I go into my namescheap advanced DNS settings and change CNAME or AAA Record? Also, is it required to use SSL Endpoint (heroku addon) to get secure green bar for my app url?
you are linking to insecure resources:
<img alt="feature pic" src="http://~~~.png" width="286" height="180" />
You need to use https for your page, and any resources that it loads for your browser not to complain. curl works fine because it only fetches the html and not the linked insecure images.
Related
I recently downloaded an SSL certificate from zeroSSL.com and set it up in my Heroku CLI. Now the website still uses HTTP but it shows that an SSL certificate has been added on heroku.
If Heroku shows that the certificate was added, it should be available. Can you successfully browse to your site using HTTPS?
Note that Heroku doesn't redirect from HTTP to HTTPS for you. They recommend that you do that in application code:
Redirects need to be performed at the application level as the Heroku router does not provide this functionality. You should code the redirect logic into your application.
That page has several examples for how to redirect using common languages and frameworks. I'm not sure what you're using, but I suggest you start there.
Fail to load resource: server 503(service unavailable)
First thing, I am not sure whether I had set up the port correctly. My React frontend is running on localhost:3000 while my Express backend is running on localhost:3001
This is my .env file.
enter image description here
This is my server.js.
enter image description here
On the frontend side, whenever doing a HTTP request, I use Axios, the endpoint url is "http://localhost:3001/app/Member", something like that. I already had a MongoDB Atlas connected with the app, it is working perfectly on localhost:3001, but I have problem trying to deploy it to Heroku. Some people said there is connection problem between MongoDB Atlas and Heroku, they suggest using the MongoDB sandbox in Heroku to solve this problem, but I already have the database with all the data that I want to used with the app, is there any way that I can import the data from my database to the MongoDB sandbox?
I tried to use "heroku local" to test whether is working, the app is running on localhost:5000, I can see my signup and login page, but I am not able to signup or login with a user email and password like I did perfectly on development mode localhost:3000.
I deployed it to heroku live, it gave me a server 503 error(service unavailable). I logged out the error.enter image description here
I have an laravel app served with docker which until recently has been working fine, but since about 3 days ago it is not working. The problem is that I need to get data from a remote database, which is done with the guzzlehttp client used in the laravel framework. The SSL certificate is given automatically via. Let's Encrypt nginx proxy companion, and should be working, I have for example checked it on https://www.sslshopper.com/ssl-checker.html, and it says the certificate is valid, but I still get the curl error "cURL error 60: SSL certificate problem: certificate has expired (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)".
I have tried manually to point the guzzlehttp client to the cerficate file, and even downloaded the latest cacert file and used that, but no luck. Code looks something like this:
$this->client = new Client(["verify" => '/path-to-cert-file-in-docker-container.pem']);
Even more bizarre is that I have the same app running locally, and here I don't get the error if I use the certificate from the server or from https://curl.haxx.se/ca/cacert.pem mentioned above.
I should mention that we updated the let's encrypt container giving out the certificates on the server, so I run an older version locally. But the only thing that has changed is that we pulled a new image from docker, and I don't know what this should do to make a change here. I mention this since it seems that the error started after we updated let's encrypt, but I have been unable to find the connection.
Feel free to ask any questions or request code from the project.
Thanks in advance, Richard.
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