ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
Hi All,
Nothing untoward apart from a major power outage where our server is based. I assume there's a man in a JCB with a blackened face and charred hair somewhere, wishing he'd have checked the national grid records before pulling the 'dig' lever...
Anyway - we're back, and sorry for the hours in the wilderness!!
Lee
I was getting worried! Welcome back!
Beosound 9000 MK III, Beosound Century, Beogram 5005, Beolab 8000, Beolab 5000, Beolab 4000, Beolab 5, Beovision 8, Beovision 10, Beovision 5, Beoplay A2, Beoplay E8, Beoplay H6.
Good to know it was nothing serious.
Jacques
My productivity at work went up, because of this downtime. Now my boss my expect this level of commitment every day!
glad to have the site back
badgersurf:My productivity at work went up, because of this downtime. Now my boss my expect this level of commitment every day! glad to have the site back
Eclipse 65V1-32Beosound M5Essence MK2BLI
badgersurf: My productivity at work went up, because of this downtime. Now my boss my expect this level of commitment every day! glad to have the site back
Reminds me of the old saying, virtue is its own punishment. Do a job right once and everyone expects it again.
The way the threads here about the Eclipse and such have been going, I was wondering if the outage was due to a Denial Of Service attack originating in Struer...
Jeff
I'm afraid I'm recovering from the BeoVirus.
Jeff:Reminds me of the old saying, virtue is its own punishment. Do a job right once and everyone expects it again. The way the threads here about the Eclipse and such have been going, I was wondering if the outage was due to a Denial Of Service attack originating in Struer... Jeff Beovirus victim, it's gotten to be too much to list!
New: Beovision Harmony, Beolab 50's, Beolab 28's, Beolab 18's, Beolab 17's, Beosound Stage & LG, Beosound 2, Beoplay M3, Beoplay A1, Beoplay Portal, Beoplay H4 gen 2, Beoplay E8 3.0
Mikipedia on YouTube: https://www.youtube.com/c/Mikipedia
Mikipedi4 on Twitch: https://www.twitch.tv/mikipedi4
Mikipedia on Intagram: https://www.instagram.com/mikipedi4/
Old: Beosound 9000 mk3, Beolab 3's, Beovision Eclipse, Beolab 1's, Beolab 2, Beovision 10-46, Overture 2300, beolab 8000's, Beolab 4000's, Beovision avant 32" etc. etc.
Mikipedia: Jeff: Reminds me of the old saying, virtue is its own punishment. Do a job right once and everyone expects it again. The way the threads here about the Eclipse and such have been going, I was wondering if the outage was due to a Denial Of Service attack originating in Struer... Jeff Beovirus victim, it's gotten to be too much to list! Lol, but wouldn’t that be too much effort for them?
Jeff: Reminds me of the old saying, virtue is its own punishment. Do a job right once and everyone expects it again. The way the threads here about the Eclipse and such have been going, I was wondering if the outage was due to a Denial Of Service attack originating in Struer... Jeff Beovirus victim, it's gotten to be too much to list!
Beovirus victim, it's gotten to be too much to list!
Lol, but wouldn’t that be too much effort for them?
Maybe they outsourced it to China?
Mikipedia:@9 lee I have a question, since the power outage it seems like something changed in the app for me. Nothing mayor but still. I started the “beoworld travel thread” but it does not appear in my app. It does appear in my browser. Every other new thread does appear in the app for me, just not my own I was wondering if something changed, or if it’s just me. I’ve already deleted the app and reinstalled it twice to no avail. Thank you in advance!
Mikipedia:I was wondering if something changed, or if it’s just me. I’ve already deleted the app and reinstalled it twice to no avail. Thank you in advance!
Nothing was changed, it was just a major power outage which was not fixed very quickly.
I cannot explain the situation you have described and I checked the thread myself and I could not see anything wrong.
I can only assume that you may have been in that thread when the power went down and you received some kind of corruption.
You could clear your browser cache and try again in case you are actually currently reading the local version of the thread rather then from the Beoworld server. Whilst you are using the Beoworld App it effectively acts like a browser to receive the data, hence my suggestion about the cache.
Also, if any other members are seeing this problem, then please let me know.
Regards Keith....