BUNKEROFDOOM.com site??

[WBear2GCR]

Uh-oh.

Just went to see if Bunker of Doom had a manual... looks like it is down, unpaid, or something??

Anyone know what happened?
Trying to pull his name out, swapped emails some years back... he had a LOT of STUFF!!

                    _-_-bear

[w8khk]

Uh-oh.

Just went to see if Bunker of Doom had a manual... looks like it is down, unpaid, or something??

Anyone know what happened?
Trying to pull his name out, swapped emails some years back... he had a LOT of STUFF!!

                    _-_-bear

Bear, try sending a PM or email to Patrick, KD5OEI.  His email is listed on the zed.

[KD1SH]

  I'm able to access the site, but many of the links to manuals and such just lead to the dreaded 404. Not all of them, though; some of the links work fine.

[Pete, WA2CWA]

His web site comes up fine.
www.bunkerofdoom.com

[w8khk]

His web site comes up fine.
www.bunkerofdoom.com

Interesting.  At the time I answered Bear's post earlier today, the site did not respond.  But now it is responding.  At that time I verified DNS was not the problem.  

 nslookup bunkerofdoom.com
Server:  UnKnown
Address:  192.168.0.1
Name:    bunkerofdoom.com
Address:  206.130.102.170

Whatever it was, it is working fine now.  
There was no ping response at 21:06 EDT today.

Go figure.....

[Pete, WA2CWA]

Life can be a bitch at times!

[WD8BIL]

" NEW! ~
Please bear with us as we work to survive a migration. Some items may return errors during this time."

Found on his page at 8:15 this morning.

[WBear2GCR]

a ha!!

"migration"!

Seems that migration is also an issue with certain text messages by a certain entity...
...no wonder the rest of us have such troubles then??

                _-_-bear

[Pete, WA2CWA]

Maybe all the rain in Texas recently has caused him some problem. Dallas area so far this year has had about 30 inches of rain.

[Opcom]

His web site comes up fine.
www.bunkerofdoom.com

Email: pa...........................om

PLEASE DO NOT POST MY EMAIL ADDRESS ON A PUBLIC FORUM. PLEASE REMOVE THIS POST HASTE. I was wondering where all the extra spam was coming from. Thanks a lot what a sorry thing to do.

[Opcom]

Sorry to take a long time to log in here. Been busy. I assure all, it is not 'unpaid'.

Westhost 'migrated' all of their sites to some other server farm. Different IP address, who the heck knows what web server software they use. For that matter, what o/s, though it is likely some kind of Linux because that is free.

They announced this on a friday, after hours, and told eveyone to go update their DNS, mail, webserver config, etc.. within 3 days the original sites (many containing actual businesses and databases LOL). Clowns playing with peoples' livelhoods.

So in the webservers I'm familiar with, which are 'Apache' and 'IIS', there is a text type of file called .htaccess
This file contains directives to be obeyed by the webserver software. There is a directive called 'speling', which tells the webserver to ignore spelling errors in URLs. The usual result of a spelling error, when 'speling' is ON, is that the server will then offer the guest a choice of close matches, instead of giving a 404 error.

I don't have spelling errors in URLs. That is, not if the case is ignored - but wait, case isn't spelling. Last time I looked at human dictionaries, case or capitalization is not a spelling thing, but simply a grammar thing to denote beginnings of sentenced and proper nouns and acronyms, etc.

But that is not the main point. The other directive in the file is called 'caseonly'. If this is turned on, only case discrepancies are ignored. 'speling' must be on as well. So, it's like telling the web server to check spelling and react to errors, but ONLY if it is an upper/lower case "error", in which case ignore the case and deliver the target resource the URL calls for.

Some URLs and file names on the site have a difference of case - that is, the HTML code will ask for "/LIT/RCA_document.pdf", but the path and target may actually be "/lit/RCA_document.PDF".

So, it's a specific type of syntax error, if anyone wants to make that stretch.

o/s like the UNIX of old, and semi-clones Linux are inherently fussy about upper case and lower case, and get their shorts wound up about it. This is because of the age-old defect in those o/s of making commands uppercase and filenames lower case. This, I suppose, was originally to keep people from accidentally trashing the system. It's not a problem any more, not for many years. But that's how it was, and the convention has been kept, just like many other conventions in other o/s's.

High end o/s like VMS / OpenVMS don't care about case, never have. My humble site was born in the dim time of the internet, written and hosted on VAX-VMS, eventually got an IP address, and grew with some edits being made in Microsoft Notepad. Of course it workled perfectly. Being all manually written it loads up fast and there's no need for css, scripts, ads, tracking or other bloat for somerthing so simple.

When the traffic became too much for a business ADSL line in the actual bunker of doom building, I moved the site to remote host 'Westhost', which was on Linux, with the Apache web server. This very issue we see today popped up immediately. I was able to get someone on the phone, and they immediately told me what to do, and it worked for years.

Fast forward to now: They moved it, didn't set up DNS or anything -I had to figure that out (no support) and it does not work because of the case issue is apparently not respected on their junk farm. You can't get anyone on the phone, and service tickets are not addressed. If you call the number, some kind of hellish robot answers the phone and tells you to use chat or start a ticket, then hangs up. Chat, BTW, and a 45-90 minute wait time, no doubt because all their junk is broken.

Not only that, I can Telnet and or FTP in there, or log in with the web-based 'control panel', see in the directory where there is the .htaccess file, that it has numerous versions, and none have worked. So, they did try to make it work, but have failed. Apparently, they don't know why it doesn't work or it would be fixed. I also tried editing the .htaccess file for speling and caseonly, to no avail.

Now, the buffoonish people who are running the new server, and using whatever undisclosed goat-head-of-demons abomination o/s and web server software is installed, I would presume, are more knowledgeable than I. So perhaps there is some cock-a-mame rat-king swirling cesspool of steaming rack-mounted oobleck there, and they are too terrified to speak too many names lest something even worse rear its ugly head and drag them all down through the raised floor into a bottomless pit.

I'm at a loss to fix this, I don't know anything about abominations or witchcraft. One thing I do know is that there is zero motivation to rewrite the entire site to fix this, when there is an .htaccess file right there.

[Pete, WA2CWA]

His web site comes up fine.
www.bunkerofdoom.com

Email: pa...........................om

PLEASE DO NOT POST MY EMAIL ADDRESS ON A PUBLIC FORUM. PLEASE REMOVE THIS POST HASTE. I was wondering where all the extra spam was coming from. Thanks a lot what a sorry thing to do.

It came right off your home page.

[W1RKW]

it's an image of his email address.

It came right off your home page.

[KD1SH]

  Just for my own education: is showing an email address on a website as an image, rather than as a link, more secure since the 'bots are less likely to find it? Never thought about it before, but it seems like a good idea.

it's an image of his email address.

It came right off your home page.

[W1RKW]

web crawler indexing is text based.  the web crawlers look at text like hyperlinks and metadata within the HTML of a webpage(s).

[KD1SH]

Very good; thanks. I took a course in HTML way back in the 90's, but it seems like (and it was) a very long time ago.

web crawler indexing is text based.  the web crawlers look at text like hyperlinks and metadata within the HTML of a webpage(s).

[Opcom]

Thank you for removing the text. I understand the misunderstanding. There is indeed a big difference b/c crawlers and harvesters treat text differently from images and no one is analyzing images for (non-captcha types of) text because of the very small chance of reward.