Subtle changes, bugs and feedback

Forgot about the wildcard SSL cert.

I get a 404 on http, too, but I guess that's because you're working on it at the moment.

Nope, that would be something else entirely

wtf is a "ping"

snapped knicker elastic?
broken spoke?
message alert on phone?
hotel foyer bell?

It's the noise the hammer makes when it hits the nail on the head.

Nope, that would be something else entirely

Oh.

This is pretty irrelevant, but an appeal to move the Mark All Threads button off the top page and maybe put it somewhere inside the User CP? On a minimised phone version of the forum, it sits right under the "New Posts" button, and one little slip of the finger and...

Is it used often? Is there any reason why it needs to be so available on the main page? Am I just a numpty with big thumbs?

+100 i do this all the time, very annoying

i did it yesterday too

i did it yesterday too

Try using something other than your hammer on your phone.

It's the noise the hammer makes when it hits the nail on the head.

that would be when you miss-hit it, and it "pings" off somewhere stupid, usually across the room.

Ah, the voice of experience. :)

ha

wtf is a "ping"

snapped knicker elastic?
broken spoke?
message alert on phone?
hotel foyer bell?

This.

Test

It's like shouting at a computer far away on the internet 'are you there?!'.

If you get a reply, it is.

I tried pinging it and I got a loop like this:

Last login: Sun Nov 14 10:10:36 on console
Petes-Mac-Pro:~ pete$ ping static.lfgss.com
PING static.lfgss.com (109.74.206.114): 56 data bytes
64 bytes from 109.74.206.114: icmp_seq=0 ttl=55 time=16.465 ms
64 bytes from 109.74.206.114: icmp_seq=1 ttl=55 time=15.269 ms
64 bytes from 109.74.206.114: icmp_seq=2 ttl=55 time=15.671 ms
64 bytes from 109.74.206.114: icmp_seq=3 ttl=55 time=16.247 ms
64 bytes from 109.74.206.114: icmp_seq=4 ttl=55 time=16.265 ms
64 bytes from 109.74.206.114: icmp_seq=5 ttl=55 time=16.267 ms
64 bytes from 109.74.206.114: icmp_seq=6 ttl=55 time=16.018 ms
64 bytes from 109.74.206.114: icmp_seq=7 ttl=55 time=16.049 ms
Request timeout for icmp_seq 8
64 bytes from 109.74.206.114: icmp_seq=9 ttl=55 time=16.070 ms
64 bytes from 109.74.206.114: icmp_seq=10 ttl=55 time=16.061 ms
64 bytes from 109.74.206.114: icmp_seq=11 ttl=55 time=16.042 ms
64 bytes from 109.74.206.114: icmp_seq=12 ttl=55 time=15.815 ms
64 bytes from 109.74.206.114: icmp_seq=13 ttl=55 time=15.827 ms
64 bytes from 109.74.206.114: icmp_seq=14 ttl=55 time=15.817 ms
64 bytes from 109.74.206.114: icmp_seq=15 ttl=55 time=15.851 ms
64 bytes from 109.74.206.114: icmp_seq=16 ttl=55 time=15.828 ms
64 bytes from 109.74.206.114: icmp_seq=17 ttl=55 time=15.589 ms
64 bytes from 109.74.206.114: icmp_seq=18 ttl=55 time=16.665 ms
64 bytes from 109.74.206.114: icmp_seq=19 ttl=55 time=16.210 ms
Request timeout for icmp_seq 20
64 bytes from 109.74.206.114: icmp_seq=21 ttl=55 time=15.406 ms
64 bytes from 109.74.206.114: icmp_seq=22 ttl=55 time=16.634 ms
64 bytes from 109.74.206.114: icmp_seq=23 ttl=55 time=16.390 ms
64 bytes from 109.74.206.114: icmp_seq=24 ttl=55 time=16.386 ms
64 bytes from 109.74.206.114: icmp_seq=25 ttl=55 time=16.414 ms

etc.

Request timeout means it has waited a while for the computer to shout back and it hasn't heard anything.

I think it's working now.

Panic over.

It is, my terminal window is now sans timeouts.

That and the website has stopped looking funny at the top.

lost

So... all good?

OK... so now I've set up the SSL certificates sooner than I was going to... LFGSS might as well have the new IP address.

109.74.206.114 www.lfgss.com static.lfgss.com

That's the new IP address for those domains, on both http and https.

So... all good?

Works fine now!

https://static.lfgss.com/

I can't log in at that address though I have checked my password

You shouldn't try. Everything on that domain is cached.

Fair enough. Obviously I have no idea what that means.

That little bump was me re-sizing the load balancer to add more RAM, and modifying the file system so that it was noatime and ext2.