IRC - irssi - "Invalid oper credentials" error - "Could not resolve your hostname" error reddit / irc ---------------------------------------------------------------------- v8ive · 2020-08-20 21:03 I'm still fairly new to this arena, but I'm attempting to learn how to set up/use an IRC. ​ Bind Address settings (inspircd.conf): ** ​ Oper settings (inspircd.conf): ** ​ I type "/oper" and the password as it's requested, and it gives me "Invalid oper credentials". ​ Possible 'need-to-know's': 1. I'm doing this on Kali (VirtualBox) 2. Everything is up-to-date (Running InspIRCd-3) 3. I get this error when I connect, probably has nothing to do with it, but still another error: *16:55 -!- Irssi: Looking up* [*irc.8anon.net*](https://irc.8anon.net) *16:55 -!- Irssi: Connecting to* [*irc.8anon.net*](https://irc.8anon.net) *\[*[*127.0.0.1*](https://127.0.0.1)*\] port 6667* *16:55 -!- Irssi: Connection to* [*irc.8anon.net*](https://irc.8anon.net) *established* *16:55 irc.8anon.net \*\*\* Looking up your hostname...* *16:55 irc.8anon.net \*\*\* Could not resolve your hostname: Request timed out; using your IP address (*[*127.0.0.1*](https://127.0.0.1)*) instead.* *16:55 -!- Welcome to the Localnet IRC Network v8ive!v8ive@127.0.0.1* ​ Any help is greatly appreciated. I'm happy to share any other details required, just let me know, thanks!! ---------------------------------------------------------------------- v8ive · 2020-08-20 21:07 Solved! Wow, sorry guys for wasting your time. I'll leave this here in case others come across this error. I had to specify the oper name. So "/oper 8root" in this case, then my pass worked! ---------------------------------------------------------------------- I-am-fun-at-parties · 2020-08-20 21:08 Your oper settings define the user '8root' but your username is 'v8ive'. That's the invalid credentials part. Since your system cannot resolve 127.0.0.1 the hostname part of your oper configuration would probably need to reflect that, too ---------------------------------------------------------------------- v8ive · 2020-08-20 21:11 Yea that's why I ended up trying to specify the name; so "/oper 8root", then the pass worked. Any idea why I can't resolve the hostname? ---------------------------------------------------------------------- I-am-fun-at-parties · 2020-08-20 21:19 maybe there's no entry for it in /etc/resolv.conf? ---------------------------------------------------------------------- v8ive · 2020-08-20 21:59 There wasn't, I went ahead and added it in but still getting the same result. ---------------------------------------------------------------------- I-am-fun-at-parties · 2020-08-20 22:44 Right, that was nonsense anyway as I a) had /etc/hosts in mind, not resolv.conf, but b) that only does forward name resolution anyway. I have to admit I've never questioned how 127.0.0.1 is reverse- resolved, I always assumed there to be some magic that does that locally but in fact now that I'm checking a bunch of servers they all seem to reverse-resolve 127.0.0.1 like they'd do any other address, they ask the configured resolver. So it would seem that yours simply doesn't do that (just checked, neither google's (8.8.8.8) nor amazon's (1.0.0.1) resolver do). Which one(s) are you using (they're in /etc/resolv.conf)? ---------------------------------------------------------------------- v8ive · 2020-08-21 12:09 The IP in question (127.0.0.1) had to be added in to resolve.conf, I can check when I get back home later to see if it's still using that configuration I had to add it a while earlier to even get the IRC up and running. I read somewhere that the hostname not resolving is nothing of concern, and that it's usually an ISP issue and that it shouldn't hinder anything major. I wouldn't doubt it, as I had recently changed my ISP, so I'll have to dig deeper into that end. Probably has something to do with why mine isn't able to reverse- resolve. Interesting. I may have missed something in the conf file, so ill double check when I get home after work.