Hot and humid. Got some rain in the afternoon yesterday which cooled things down a bit, depending on what part of town you were in. The area around the BOL reported about 4 inches in one hour… lots of regional and local variation in weather in the Lonestar state. I got a lot while driving around, but almost nothing at home.
Spent the morning poking at my non-prepping hobby club website. Learned some things. Got good tech support from both hosts, voice with india at homestead.com and chat with [somewhere probably not the USA] at bluehost.com. Both addressed my immediate issues although bluehost did a bunch of stuff without asking or telling me what he was doing. I had to figure it out afterwards. (he cleared my 301 redirects, and one of them was still needed.)
There are a lot of quirks in the whole, domain registrar/internet hosting service/SSL issuers/wordpress landscape. I’ve got one external link that gets a “/” appended to it, which breaks it. Dunno if it’s wordpress or my browser “helping” but it only happens with that one link. Had to add a trailing space to the xxxxx.pdf link to keep it from happening. And when I uploaded the xxx_xxx_xxx.pdf to my file system at the host, (to avoid having to have the external link and getting the security warning) something stripped out the “_”s in the file name which I didn’t notice, which broke the linking… found that and added them back in to fix it.
And after straightening out the residual redirects at the old host, I eventually discovered that somehow the old site had one nameserver changed to bluehost. A script must have done it when I changed the nameservers for the subdomain that I eventually transferred to the new host, bluehost… that’s been screwing me up since the change, I just didn’t know what was screwing me. Hopefully today everything will have propagated.
Because last night the site didn’t work at all on old IE. No idea why. Don’t really care, but someone might still be using it. Works fine on Firefox on windows and mint linux. And mostly works on chromium on linux.
———————-
During my troubleshooting I was running tracert and noticed that the second hop outbound is always followed by 3 or 4 timeouts before it continues. I think ATT fiber, which is really good old lightspeed.sbcglobal.net underneath, has an issue somewhere…
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254] 2 1 ms 1 ms 1 ms 172-14-48-1.lightspeed.hstntx.sbcglobal.net [172 .14.48.1] 3 2 ms 2 ms 2 ms 71.149.23.112 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 7 ms 7 ms 7 ms 32.130.16.255 8 * * * Request timed out. 9 9 ms 9 ms 9 ms 141.101.74.203 10 9 ms 9 ms 9 ms host77.ipowerweb.com [66.235.2xx.xxx] The 7th hop is always the same to the 4th quad then more hops... and there are usually several timeouts before it finally starts working toward the destination. Something regional at both ends that is broken?? They may still have sites down from the storms, they have temp gennies still connected to boxes in nearby neighborhoods. ------------- I am learning things. I wish I wasn't. I've got plenty else to do. And today, I'm doing my civic duty and reporting for jury service. City of Houston courts this time. The summons says it will take all day and to bring a lunch. Joy. But that's part of being a good citizen, participating in the process. I just have a particular aversion to stripping off all my weapons and tools and then walking around downtown. Oh well. We'll see how it goes. While I'm reading a book in the jury room, y'all should be stacking so you don't end up lacking... nick