Announcement We are on the new hardware
- Thread starter Dan
- Start date
-
We had an issue with background services between march 10th and 15th or there about. This meant the payment services were not linking to automatic upgrades. If you paid for premium membership and are still seeing ads please let me know and the email you used against PayPal and I cam manually verify and upgrade your account.
Once again....another reason I am an advocate for my choices, life has been good to me in the last year haha
Maybe you should not answer "Go fishing!" once in awhile....!
And Dan... no videos please!
Both should watch out for crabs...
Class of 96
Bencher
Running fast now. I had a server moved from Ireland to Singapore a few years back and made a huge difference to reliability and speed.
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
Too much pornhub for you ......
HappilyManly
Journey Man
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
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.
Ha Ha Ha, none of that for me.
HappilyManly
Journey Man
OneEyedEagle
Bencher
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.
This 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 | L | PD | Pts |
|---|---|---|---|---|---|
|
7 | 6 | 1 | 54 | 14 |
|
6 | 5 | 1 | 59 | 12 |
|
6 | 4 | 2 | 53 | 10 |
|
6 | 4 | 2 | 30 | 10 |
|
7 | 4 | 2 | 25 | 9 |
|
8 | 4 | 4 | 73 | 8 |
|
7 | 4 | 3 | 40 | 8 |
|
7 | 4 | 3 | 24 | 8 |
|
7 | 3 | 4 | 17 | 8 |
|
7 | 4 | 3 | -8 | 8 |
|
8 | 4 | 4 | -60 | 8 |
|
8 | 3 | 4 | 17 | 7 |
|
6 | 2 | 4 | -31 | 6 |
|
7 | 3 | 4 | -41 | 6 |
|
7 | 2 | 5 | -29 | 4 |
|
7 | 1 | 6 | -87 | 4 |
|
7 | 1 | 6 | -136 | 4 |
