My reason for snooping around my Firewall Logs .
Created a CERTBOT certificate and launched a local Django server behind Nginx and uWsgi . Everything was good till i called my ISP cable guy to come and have a look - help me with connecting 2 macBooks that i have installed Ubuntu on with ETHERNET cables - in place of the usual Wifi.
I want to connect the ETHERNEt cables directly into my STATIC IP modem , and not the DLINK DIR 816 Router.
The cable guy from ISP says thats not possible as all but one Ports are blocked on the ALCATEL modem . fair enough - he then upgrades my DLINK DIR 816 Router with another DLINK DIR 816 Router , with an upgraded version of Firmware ==1.09.
I check the ETHERNET n presume im good to go - next few days coding , not testing my access to Nginx >> uWsgi >> Django dev server.
Today no access -
$ curl https://digitalcognition.co.incurl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
$ curl http://digitalcognition.co.in
<script>
<!--
window.location.href = "/cgi-bin/webproc";
-->
</script>
$
havent changed much on the UFW side --- but surely the Logs have changed - for the better or worse still figuring that out ...
No comments:
Post a Comment