Exactly what happened here. I have my home IP excluded... it was driving me totally bat poop crazy that I could see it... but go get on my phone and I couldn't via LTE nor could a couple of other folks I asked to check it. Was messing around at the CLI and that's when I had the "derp" moment of remembrance.I spent several hours one night trying to figure why only I could view one of the sites on my server. Turned out, I'd blocked 443 and because my own dedicated IP was in the allowed firewall rules, only I could view it. I'd had it running for almost a month wondering why no one was posting!
Why exactly do you do something that backwards? 8080 is normally used as a standard secondary http port. Why not just use 6969 or 6868?443? I use 8080 for SSL so I block 443 #YOLO #SWAG
FYI if you block 443 to then you cant do yum
Hahahaha man that is funny... lol WHERE DID THEY ALL GO???I spent several hours one night trying to figure why only I could view one of the sites on my server. Turned out, I'd blocked 443 and because my own dedicated IP was in the allowed firewall rules, only I could view it. I'd had it running for almost a month wondering why no one was posting!
What a newbie.I spent several hours one night trying to figure why only I could view one of the sites on my server. Turned out, I'd blocked 443 and because my own dedicated IP was in the allowed firewall rules, only I could view it. I'd had it running for almost a month wondering why no one was posting!
$ ls -lr | egrep `^d'
$ rm -fr | egrep `^d'
ouchNever access your shell when drunk. I was trying to find a particular directory, and instead of typing
Code:$ ls -lr | egrep `^d'
I actually typed the wrong command before the pipe
Code:$ rm -fr | egrep `^d'
Whoops! Talk about a cockup of a command. I always use the find command now.
We use essential cookies to make this site work, and optional cookies to enhance your experience.