Australian (ASX) Stock Market Forum

Sorry about that downtime

Good afternoon everyone, I just got back onto ASF myself so I thought I should explain about the recent access issues that many have been experiencing.

Yesterday afternoon at around 3pm ASF began to experience what appeared to be a DDOS attack and page loading time began to suffer. I waited a while to see if it would pass but it did not so I decided to use Cloudflare to mitigate the attack. This involved changing ASF's name servers, or DNS. After doing this I had to go out and run some errands. I returned an hour later and found that I could not access ASF.

I made a decision there and then to change the name servers back and just forget about Cloudflare and hope the attack had passed. Unfortunately this has resulted in access issues for many, including myself. In retrospect I think deciding to use Cloudflare and changing ASF's name servers was a bad idea. But once you've changed them you've kind of opened a can of worms and you then have to wait until everyone's ISP has refreshed their DNS cache before everyone can access the site again. Some ISPs take a very long time to do this.

So that's why many have been experiencing issues accessing ASF since around 4pm yesterday. My apologies for the inconvenience caused.
 
Last edited:
ASF went down, market has taken a tumble, and so have I.........tripped on a piece of timber,went tumbling down the slope and landed under an orange tree. Grazed my knee, shin and hit my face in the dirt.......hope forum members are having a better day

Sorry to hear it. I hope there were a few stray oranges at the bottom of that orange tree as some kind of consolation.

Let's hope next week is a better week for us all.
 
Plenty of bat chewed oranges greeted me, Joe.........and don't worry, someone will get the blame for my mishap..........another case of suspect domestic abuse coming up....gonna be a shiner on my cheek next week! Have a great weekend, and let's hope next week will be better
 
ASF went down, market has taken a tumble, and so have I.........tripped on a piece of timber,went tumbling down the slope and landed under an orange tree. Grazed my knee, shin and hit my face in the dirt.......hope forum members are having a better day
Good afternoon eskys @ Keys,
Had some dramas with the slowness of system yesterday arvo, but wasn't for all that long really. So you went arse up ... that's no good, best happened on soil rather than concrete/bitumen, would have made a mess of your best looks :)

Been awhile!!! Hope you and the family well.

Kind regards
rcw1
 
Rob (@rnr ) got some issues to connect all day, I was slightly better off but fell again temporarily in early arvo.
All good now for me...
Not a good week, but especially sad to see 3 put options expiring on the ASX 3 days ago worth 0..
a few days difference would have made me very happy...
 
you then have to wait until everyone's ISP has refreshed their DNS cache before everyone can access the site again. Some ISPs take a very long time to do this.

As the owner of the domain name you can set the Time-To-Live (TTL) value that tells cachers the lifetime (in seconds) of items in the cache.

Your TTL is set to 3391 seconds
Code:
$ dig +nocmd +noall +answer +ttlid www.aussiestockforums.com
www.aussiestockforums.com. 3391    IN    CNAME    aussiestockforums.com.
aussiestockforums.com.    3391    IN    A    204.197.253.143
or 56 minutes.

Generally, before you make DNS changes, you should
  • Lower your TTL to a short value like 60
  • Wait for the original TTL value (e.g. 56 minutes) before you make your changes, to allow all caches to expire and cache the new shorter value.
  • Make your changes.
  • If there are any issues, you can change the record again and not worry about cache.
  • Once you're happy increase the TTL back to original value.

If you want to implement Cloudflare and need help, let me know, happy to do a screenshare while you go through it and point out any footguns.
 
As the owner of the domain name you can set the Time-To-Live (TTL) value that tells cachers the lifetime (in seconds) of items in the cache.

Your TTL is set to 3391 seconds
Code:
$ dig +nocmd +noall +answer +ttlid www.aussiestockforums.com
www.aussiestockforums.com. 3391    IN    CNAME    aussiestockforums.com.
aussiestockforums.com.    3391    IN    A    204.197.253.143
or 56 minutes.

Generally, before you make DNS changes, you should
  • Lower your TTL to a short value like 60
  • Wait for the original TTL value (e.g. 56 minutes) before you make your changes, to allow all caches to expire and cache the new shorter value.
  • Make your changes.
  • If there are any issues, you can change the record again and not worry about cache.
  • Once you're happy increase the TTL back to original value.

If you want to implement Cloudflare and need help, let me know, happy to do a screenshare while you go through it and point out any footguns.

You are correct. I should have adjusted the TTL value. However, I acted quickly and unfortunately this is not my area of expertise so I forgot about TTL. I will endeavour to remember it next time.

Thanks for the tip.
 
So you can be nice!
Awesome.
Do you have a special name for Joe ?
Joe is a nice person running an old school internet forum in 2022, he deserves all the help he can get.

How about Joey Jo-Jo Junior Shabadoo



Your favourites seem to be, in no specific order of course;
Turnip
Buffoon
Moron

Go on, you know you want to... ??

I just call 'em how I see 'em.
 
The lesson to be learned is, if you are going to make significant changes to your website (significant changes include DNS changes, installing plugins, or upgrading anything) don't do it just before you go out or before you go to bed. Murphy's Law will bite you in the bum and you will suffer the consequences.

Make important website changes on Sunday morning when nobody gives a ****.
 
The lesson to be learned is, if you are going to make significant changes to your website (significant changes include DNS changes, installing plugins, or upgrading anything) don't do it just before you go out or before you go to bed. Murphy's Law will bite you in the bum and you will suffer the consequences.

Make important website changes on Sunday morning when nobody gives a ****.
As long as you can get tech support then.?
 
Just discovered this thread. Because a certain dufus blocks me, I couldn't see it until now

Basically @Joe Blow the arbitrary block set up p1sses me off. If you don't want my input, I'll leave
 
Good afternoon eskys @ Keys,
Had some dramas with the slowness of system yesterday arvo, but wasn't for all that long really. So you went arse up ... that's no good, best happened on soil rather than concrete/bitumen, would have made a mess of your best looks :)

Been awhile!!! Hope you and the family well.

Kind regards
rcw1
Good morning rcw1, glad you found us and thank you for your post.

All considered, was lucky I did not sustain a fracture of some sort. Bit achy this morning, didn't realise I hit my jaw until this morning.......purple jaw with a tinge of blue.......would need some Lasonil no doubt. Falls and seniors do not go togehter, take care.........market down again last night..

Have a great weekend, rcw, and everyone
 
Just discovered this thread. Because a certain dufus blocks me, I couldn't see it until now

Basically @Joe Blow the arbitrary block set up p1sses me off. If you don't want my input, I'll leave
Hi Dona, how do we know when someone blocks us? Do we get notification from admin?

Sorry to read you had a block.......
 
Just discovered this thread. Because a certain dufus blocks me, I couldn't see it until now

Basically @Joe Blow the arbitrary block set up p1sses me off. If you don't want my input, I'll leave

I don't get it. The only way you could be prevented seeing a thread is if the thread starter blocked you. I started this thread and I'm not blocking you, so you should always have been able to see and read it.

Unless you are referring to not being able to see particular posts in the thread by someone that has blocked you.
 
Top