More like the nightie after 15 years of marriage for me: up every now and then but mostly down.
Try it after 44 years!!
“ You want to what????”
More like the nightie after 15 years of marriage for me: up every now and then but mostly down.
Once again....another reason I am an advocate for my choices, life has been good to me in the last year hahaTry it after 44 years!!
“ You want to what????”
Try it after 44 years!!
“ You want to what????”
Both should watch out for crabs...Maybe you should not answer "Go fishing!" once in awhile....!
And Dan... no videos please!
Too much pornhub for you ......I couldn't work out how to start a thread so I posted in this one. Can someone tell me why I'm getting the below error when I go to www.silvertails.net
View attachment 11645
Because you added the wwwI couldn't work out how to start a thread so I posted in this one. Can someone tell me why I'm getting the below error when I go to www.silvertails.net
View attachment 11645
Ok, that worked. Weird thing is it's always worked in the past with www. I did change browsers to Firefox so maybe it works a bit different.Because you added the www
https://silvertails.net
To start a Thread
1) Click on the large circle with the pencil sign in it - hovers around the bottom right of the first page of each forum
2) add the Thread Title that we will all see
3) post whatever is of interest
4) Click the Create Thread at the bottom of the post
Ha Ha Ha, none of that for me.Too much pornhub for you ......
Silvertails is on the dark webOk, that worked. Weird thing is it's always worked in the past with www. I did change browsers to Firefox so maybe it works a bit different.
I couldn't work out how to start a thread so I posted in this one. Can someone tell me why I'm getting the below error when I go to www.silvertails.net
View attachment 11645
This is true.It wasn't routing through the secure web server the "S" at the end of the HTTP encrypts the data such as your username / password.
@Dan you should be able to route the the unsecured site via an SSL certificate so no one else gets the same error and automatically gets routed.
That’s almost exactly what I thought was happeningThis is true.
What happened was our certificate required a regular renew, this is automated however it failed because of the issuer and continued to fail until our renew attempts were exhausted
Soni had to go and buy a new certificste to tide us over until I can renew our normal one when our attempts are refreshed next month
When I did that I had to reconfigure our server settings to see the new certificates and in doing so I inadvertently ruined my 302 redirect to https only and bam problem ensued.
Right now it's sitting in a working state and I'm waiting until I have more time to break it all and pay the $160 odd it costs for a re-issue of a cert instead of the letsencrypt one....
Either way issuer bad, then my bad
Team | P | W | D | L | PD | Pts | |
---|---|---|---|---|---|---|---|
1 | Bulldogs | 7 | 6 | 0 | 1 | 74 | 14 |
2 | Storm | 7 | 5 | 0 | 2 | 78 | 12 |
3 | Raiders | 8 | 6 | 0 | 2 | 58 | 12 |
4 | Warriors | 7 | 5 | 0 | 2 | -4 | 12 |
5 | Broncos | 8 | 5 | 0 | 3 | 78 | 10 |
6 | Cowboys | 7 | 4 | 0 | 3 | -10 | 10 |
7 | Sharks | 8 | 4 | 0 | 4 | 39 | 8 |
8 | Sea Eagles | 8 | 4 | 0 | 4 | 36 | 8 |
9 | Tigers | 8 | 4 | 0 | 4 | 14 | 8 |
10 | Dragons | 7 | 3 | 0 | 4 | -8 | 8 |
11 | Rabbitohs | 8 | 4 | 0 | 4 | -44 | 8 |
12 | Dolphins | 8 | 3 | 0 | 5 | 16 | 6 |
13 | Roosters | 8 | 3 | 0 | 5 | -52 | 6 |
14 | Titans | 7 | 2 | 0 | 5 | -68 | 6 |
15 | Knights | 7 | 2 | 0 | 5 | -74 | 6 |
16 | Eels | 7 | 2 | 0 | 5 | -107 | 6 |
17 | Panthers | 8 | 2 | 0 | 6 | -26 | 4 |