 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Up date! I was wrong it wasn't my web server that put the S in the https.
It was my FireFox. You see I copied my web site address from the Email my server
send. It was just www...bla bla bla. So I pasted it in my goto box, got there,
then just bookmarked it.
FireFox don't you just Love It :0
Otherwise I've slow the graphics down a bit on the main page. And did a lot of
clean up. Now everything that I've got on there can be downloaded or viewed.
Have Fun!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 23 Feb 2019 22:58:18 -0500, Mike Horvath wrote:
> I will need to do SSL soon too unless I don't care if Google Chrome
> users can no longer access my site.
Take a look at LetsEncrypt. You have to install a new certificate every
90 days (downside), but it is free and if you're using most standard web
servers, it's easy to automate the updates.
Jim
--
"I learned long ago, never to wrestle with a pig. You get dirty, and
besides, the pig likes it." - George Bernard Shaw
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/3/2019 5:41 PM, Jim Henderson wrote:
> On Sat, 23 Feb 2019 22:58:18 -0500, Mike Horvath wrote:
>
>> I will need to do SSL soon too unless I don't care if Google Chrome
>> users can no longer access my site.
>
> Take a look at LetsEncrypt. You have to install a new certificate every
> 90 days (downside), but it is free and if you're using most standard web
> servers, it's easy to automate the updates.
>
> Jim
>
>
>
I may do that. I just got an email from my web host. They want an extra
$29.99 per year for an SSL certificate.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/8/19 4:21 PM, Mike Horvath wrote:
> On 3/3/2019 5:41 PM, Jim Henderson wrote:
>> Take a look at LetsEncrypt. You have to install a new certificate every
>> 90 days (downside), but it is free and if you're using most standard web
>> servers, it's easy to automate the updates.
>>
>> Jim
>>
>>
>>
>
> I may do that. I just got an email from my web host. They want an extra
> $29.99 per year for an SSL certificate.
Wow, that seems a ripoff. I use LetsEncrypt. I actually forget about
it until they emailed me with special instructions; they deprecated a
protocol. It was painless to setup and is painless to maintain.
--
dik
Rendered 1024 of 921600 pixels (0%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 08 Mar 2019 16:21:50 -0500, Mike Horvath wrote:
> I may do that. I just got an email from my web host. They want an extra
> $29.99 per year for an SSL certificate.
Yeah, I looked at the costs and the traffic I generate to my sites, and
decided it wasn't worth it - but I have an authentication system on my
sites, and don't want username/password info sent in the clear. LE is a
perfect fit for it.
And the system I use is completely scriptable, so I just have a cron job
that will run every 90 days to update the certificates automatically (but
troubleshooting it has been a pain - since I test with live certificates,
I generally only test when I need to update the certs).
The cool thing is they added wildcard certs, so now it's just a single
wildcard cert for everything.
DNS through AWS costs me $11/year plus about $0.50 per month or something
in that ballpark. It's weird to have a payment on that credit card (only
thing I use it for) of < $1 per month. :)
Jim
--
"I learned long ago, never to wrestle with a pig. You get dirty, and
besides, the pig likes it." - George Bernard Shaw
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/8/2019 5:51 PM, Jim Henderson wrote:
> On Fri, 08 Mar 2019 16:21:50 -0500, Mike Horvath wrote:
>
>> I may do that. I just got an email from my web host. They want an extra
>> $29.99 per year for an SSL certificate.
>
> Yeah, I looked at the costs and the traffic I generate to my sites, and
> decided it wasn't worth it - but I have an authentication system on my
> sites, and don't want username/password info sent in the clear. LE is a
> perfect fit for it.
>
> And the system I use is completely scriptable, so I just have a cron job
> that will run every 90 days to update the certificates automatically (but
> troubleshooting it has been a pain - since I test with live certificates,
> I generally only test when I need to update the certs).
>
> The cool thing is they added wildcard certs, so now it's just a single
> wildcard cert for everything.
>
> DNS through AWS costs me $11/year plus about $0.50 per month or something
> in that ballpark. It's weird to have a payment on that credit card (only
> thing I use it for) of < $1 per month. :)
>
> Jim
>
>
>
I have cpanel and a directory I use for uploading files via FTP. I'm not
sure I am able to run a cron job on the (shared) server. Not sure how to
find out if I am able to, too.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 11 Mar 2019 06:57:00 -0400, Mike Horvath wrote:
> I have cpanel and a directory I use for uploading files via FTP. I'm not
> sure I am able to run a cron job on the (shared) server. Not sure how to
> find out if I am able to, too.
If you have shell access, you can set up a cron job for your user - but
pulling the certs on the web server might not be practical. I run my cron
job on a local host (different than the hosts that I put the certs on - I
actually put them on my router, my personal VPN server, an access
management tool that manages external-facing websites for me, and the
system that links to the access management tool to provide the login
capabilities, since it uses TLS for that connection as well).
Jim
--
"I learned long ago, never to wrestle with a pig. You get dirty, and
besides, the pig likes it." - George Bernard Shaw
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/21/19 7:05 PM, Leroy wrote:
> Thanks for all the replies!
>
> I found a real quick fix drop the S from the https in the address
> https://leroyw.byethost15.com/
>
> My server gave me the certified address.
> And I have frames and wrote all those sub pages with lots of directories to hold
> stuff.
> It seem that the certificate doesn't transfer well from the frames.
>
> Well now back to work, Got clean up the site.
>
> Thank again!
Does this mean that the unencrypted HTTP will be the final protocol for
your new site?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/22/2019 1:53 PM, Jim Henderson wrote:
> Yeah, not using https would work, but your connection won't be encrypted.
>
> It's not a frame issue, though - you'd get a different message if you
> were serving up unencrypted data and encrypted data with the connection.
>
> Ultimately, the problem with the certificate is that it's self-signed,
> and as such, untrusted. SSL certificates work because they're issued by
> a trusted authority - self-signed certificates are placeholders intended
> to be replaced with a 'real' certificate with a valid chain of trust and
> encryption keys that are unique (many self-signed certificates are
> distributed with the web server, and are not unique or tied to the
> external hostname).
>
>
>
I was resigned to not using a certificate on my site and just hoping
people (and spiders) would visit it anyway. Then I heard about Let's
Encrypt and their free SSL service! Yay! But then I found out that my
host blocks Let's Encrypt and I am depressed again.
:(
Michael
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 13 Jul 2019 02:52:43 -0400, Mike Horvath wrote:
> I was resigned to not using a certificate on my site and just hoping
> people (and spiders) would visit it anyway. Then I heard about Let's
> Encrypt and their free SSL service! Yay! But then I found out that my
> host blocks Let's Encrypt and I am depressed again.
I wonder why they block it....It's a valid SSL certificate, with a proper
chain to validate the certificate as valid.
Maybe time to find a new hosting provider. :)
--
"I learned long ago, never to wrestle with a pig. You get dirty, and
besides, the pig likes it." - George Bernard Shaw
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
