Hi all. So, I've been setting up my new board over the last couple of days, and had managed to get fsxNet working for both messages and files (I even
sent successful messages and received replies). Today, though, I was working on some automation scripts for polling, and I think I may have fubar'd my config, or inadvertantly got my IP blacklisted. I'm now getting
"authorization failed" when I run my fidopoll against 21:1/100. Does anyone know if there's any way I can confirm that this is what happened, and if so, does anyone know how to fix it? :)

Thanks in advance.

JayB from Technically BBS via Bottomless Abyss BBS :D

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

On 22 Jan 2021 at 08:14p, jayb pondered and said...

Hi all. So, I've been setting up my new board over the last couple of days, and had managed to get fsxNet working for both messages and files
(I even sent successful messages and received replies). Today, though,
I was working on some automation scripts for polling, and I think I may have fubar'd my config, or inadvertantly got my IP blacklisted. I'm now getting "authorization failed" when I run my fidopoll against 21:1/100. Does anyone know if there's any way I can confirm that this is what happened, and if so, does anyone know how to fix it? :)

First thing I'd suggest is send in an application and grab a node number of your own. If you use the 21:1/999 setup AKA there's always the chance someone else will poll and collect the reply you were waiting for.

That said, I checked the 21:1/100 HUB and there are no IPs in the blocklist.

I can see polling from you up until around 6am my time today. The last poll I saw was this one

[snip]

+ 2021.01.23 06:58:23 BINKP > Connect on slot 1/25 (99.253.242.40)
+ 2021.01.23 06:58:23 BINKP 1-HostName cpe704f57729de9-cm9050ca1845d0.cpe.net.cable.rogers.com
+ 2021.01.23 06:58:23 BINKP 1-Country Canada (CA)
+ 2021.01.23 06:58:23 BINKP 1-System Technically BBS
+ 2021.01.23 06:58:23 BINKP 1-SysOp jayb
+ 2021.01.23 06:58:23 BINKP 1-Mailer Mystic/1.12A46 binkp/1.0
+ 2021.01.23 06:58:24 BINKP 1-Queued 1 files for 21:1/999@fsxnet
+ 2021.01.23 06:58:24 BINKP 1-Sending: 0000fc7d.sa4 (4,386 bytes)
+ 2021.01.23 06:58:24 BINKP 1-Remote Queue: 0 files 0 bytes
+ 2021.01.23 06:58:25 BINKP 1-Session ended (1 sent, 0 rcvd, 0 skip)

[snip]

But I see no further connects to the server since then and it's now 8.31pm
the same day.

What do your fidopoll (or if you use 'mis poll 21:1/100' poll.txt) logs show?

have you changed anything in the echomail node settings for the 1/100 node?

Best, Paul

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hi Paul,

Thanks so much for the reply, and for checking that my IP wasn't blocked.
It's likely now that we'll find some silly thing I did. It's a mystery to me though, because it was all working so well.

I've already applied for my own node nubmer via email, so that part is taken care of (as long as I filled it out properly).

I've uploaded the output from the log files to my website (I couldn't get
them to paste into this message):

https://www.billingham.ca/bbs/fsxnet-errors.txt

I upped the logging level for the poll.log to the max and was able to
squeeze a bit more out of it. It seems to error out right after the PWD command saying "ERR Bad address or password". I can't imagine why it would
be a bad password though. I haven't changed any of the passwords I set since my initial config while following your videos.

I hope this helps, and I appreciate any help or suggestions you can offer.

Thanks!
Jay
bbs.billingham.ca (2323/2222) - Technically BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

Remember when I said we'd find out it was something silly? Well, you'd
better sit down for this one... my Echomail Address mysteriously went
missing. Very strange, because I don't remember going in there at all, and while I will be the first to admit that I may have "fat-fingered" something,
it feels very unlikely.

Either way, it's working again lol. Now I just wait for my application for
my own node number to be approved, and I should be fully in business.

Sorry to have bothered with all this, but at least this forced me to become a bit more educated in how the process works as a whole :) Silver linings :)

Thanks again.

Jay

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Technically BBS (21:1/999)