Greetings All!
I have been trying to get this going, well it works on the BBS what I cant seem to do is get my my bbs on the list... I have followed wiki to the letter, ports are open etc... But when running check system I get that I am not on the list. Not adversed to reading docs so if there is somewhere else besides wiki you can point me to Im happy to continue my search.
Hope you are all well
* Forwarded from area 'sync_sysops'
Re: sbbsimsg
By: Rick Smith to All on Fri Oct 09 2020 06:28 pm
"entry": {
"created": {
"on": "2020-09-16T04:48:11.232Z",
"by": "Nitro",
"at": "WORMHOLE"
},
"updated": {
"on": "2020-10-10T05:11:34.889Z",
"by": "Nitro",
"at": "WORMHOLE"
},
"autoverify": {
"attempts": 48,
"successes": 0,
"last_failure": {
"on": "2020-10-09T07:51:06.325Z",
"result": "No connect: 1001",
"service": {
"address": "wh2.abon.us:2321",
"protocol": "Telnet",
"port": 2321,
"description": "Telnet"
}
},
"success": false
}
}
It's never been successfully verified and the address:port doesn't
match your origin line. That's step one of the requirements here: http://wiki.synchro.net/module:sbbsimsg#requirements
Rick Smith wrote to Digital Man <=-
"autoverify": {
"attempts": 48,
"successes": 0,
"last_failure": {
"on": "2020-10-09T07:51:06.325Z",
"result": "No connect: 1001",
"service": {
"address": "wh2.abon.us:2321",
"protocol": "Telnet",
"port": 2321,
"description": "Telnet"
}
},
"success": false
}
}
It's never been successfully verified and the address:port doesn't
match your origin line. That's step one of the requirements here: http://wiki.synchro.net/module:sbbsimsg#requirements
Forgive me but I do not see what is wrong thats my BBS's address,
so I went on my bbs to look at the list and it does seem correct
to me, I made one small change to my email address... However
when I go to save it I get "JSON.parse exception: SyntasError:
JSON.parse Edit aborted, so maybe what I have on this side never
updated on your end?
* Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323
"address": "wh2.abon.us:2321",
It's never been successfully verified and the address:port doesn't match your origin line. That's step one of the requirements here: http://wiki.synchro.net/module:sbbsimsg#requirements
Forgive me but I do not see what is wrong thats my BBS's address,
so I went
on my bbs to look at the list and it does seem correct to me, I made one small change to my email address... However when I go to save it I get "JSON.parse exception: SyntasError: JSON.parse Edit aborted, so maybe what I have on this side never updated on your end?
* Forwarded from area 'sync_sysops'
Rick Smith wrote to Digital Man <=-
"autoverify": {
"attempts": 48,
Dude. Are you blind?
Look at what DM quoted up there. It shows your system as:
wh2.abon.us:2321
Now look at your origin line that I quoted above:
bbs.abon.us:2323
Do those two seem to be the same? FFS!
* Forwarded from area 'sync_sysops'
Re: sbbsimsg
By: Rick Smith to Digital Man on Sat Oct 10 2020 06:00 am
"address": "wh2.abon.us:2321",
It's never been successfully verified and the address:portdoesn't
match your origin line. That's step one of the requirementshere:
http://wiki.synchro.net/module:sbbsimsg#requirements
Forgive me but I do not see what is wrong thats my BBS's address,
Which is your BBS's address? The BBS list has what I pasted above
while your origin line says: bbs.abon.us:2323, different host name, different port.
Were you hand-editing the JSON? That's not recommended. There should
be other menu options in sbbslist to change the values for your BBS
list entry.
Greetings Digital!
Saturday October 10 2020 13:12, you wrote to me about an urgent matter!:
* Forwarded from area 'sync_sysops'
Re: sbbsimsg
By: Rick Smith to Digital Man on Sat Oct 10 2020 06:00 am
"address": "wh2.abon.us:2321",
It's never been successfully verified and the address:portdoesn't
match your origin line. That's step one of the requirementshere:
http://wiki.synchro.net/module:sbbsimsg#requirements
Forgive me but I do not see what is wrong thats my BBS's address,
Which is your BBS's address? The BBS list has what I pasted above
while your origin line says: bbs.abon.us:2323, different host name, different port.
you can use either wh2bbs.us or wh2.abon.us on port 2323 my origin below has a different bbs name even because this is the point for my other system. Not the SBBS bbs that I am trying to get figured out
Sorry for the confusion.. this is just what I do my messaging on.
Were you hand-editing the JSON? That's not recommended. There should
be other menu options in sbbslist to change the values for your BBS list entry.
Not at first I did it the traditional way but I did note a mistake and did it edit it but from within the editor in bbs list on my bbs, but as far as like nano, no I didnt...
Maybe delete it and start over? I am just learning my way around SBBS so its completely possible I mucked it up...
Rick Smith wrote to Gamgee <=-
Dude. Are you blind?
Dude besides rude have you heard of someone that has multiple
boards?
Look at what DM quoted up there. It shows your system as:
wh2.abon.us:2321
Yep thats the one in question
Now look at your origin line that I quoted above:
bbs.abon.us:2323
Nope thats my mystic bbs which hardly applies to sbbsismg...
Do those two seem to be the same? FFS!
Nope because that would confuse my users... thanks for your help
tho... so thoughtful and kind...
Re: sbbsimsg
By: Rick Smith to Digital Man on Sat Oct 10 2020 08:23 pm
Maybe delete it and start over? I am just learning my way around
SBBS so its completely possible I mucked it up...
sbbslist won't let you save invalid JSON, so it should be fine. The problem is that the information for your BBS entry can't be verified
(no connection). When your BBS can be verified, then it may be added
to the instant-message list.
Re: sbbsimsg
By: Rick Smith to Digital Man on Sat Oct 10 2020 08:23 pm
Greetings Digital!
sbbslist won't let you save invalid JSON, so it should be fine. The problem is that the information for your BBS entry can't be verified
(no connection). When your BBS can be verified, then it may be added
to the instant-message list.
Greetings Digital!
Saturday October 10 2020 23:40, you wrote to me about an urgent matter!:
Re: sbbsimsg
By: Rick Smith to Digital Man on Sat Oct 10 2020 08:23 pm
Greetings Digital!
sbbslist won't let you save invalid JSON, so it should be fine. The problem is that the information for your BBS entry can't be verified (no connection). When your BBS can be verified, then it may be added
to the instant-message list.
So other SBBS syssops were able to send me telegrams manually (not sure if pertinent) so I deleted my entry and started over carefully verifying the information and when I viewed Json from within list editor all looked fine I hit ctrl Z to save and I got the Json parsing error.. My bbs is in the list on my end but not sure what is causing that error?
I and others can ping my
bbs, connect to my bbs, send mail, ftp, connect to it on the web etc...
Greetings Digital!
Saturday October 10 2020 23:40, you wrote to me about an urgent matter!:
Re: sbbsimsg
By: Rick Smith to Digital Man on Sat Oct 10 2020 08:23 pm
Greetings Digital!
sbbslist won't let you save invalid JSON, so it should be fine. The problem is that the information for your BBS entry can't be verified (no connection). When your BBS can be verified, then it may be added
to the instant-message list.
So other SBBS syssops were able to send me telegrams manually (not sure if pertinent) so I deleted my entry and started over carefully verifying the information and when I viewed Json from within list editor all looked fine I hit ctrl Z to save and I got the Json parsing error.. My bbs is in the list on my end but not sure what is causing that error? I and others can ping my bbs, connect to my bbs, send mail, ftp, connect to it on the web etc...
Re: sbbsimsg
By: Rick Smith to Digital Man on Sun Oct 11 2020 10:38 am
This tells me that yesterday, you had your Telnet address (hostname or
IP address) set to "wh2.abon.us:2321". Since that is not a valid
hostname or IP address, that would fail the verification attempt. The
port number (in your case 2321), goes in a separate property/field. I
see that now your entry has the address set to just a hostname without
the :port, so perhaps tonight's auto-verification of your BBS entry
will succeed. We'll see.
Greetings Digital!
Sunday October 11 2020 19:06, you wrote to me about an urgent matter!:
Re: sbbsimsg
By: Rick Smith to Digital Man on Sun Oct 11 2020 10:38 am
This tells me that yesterday, you had your Telnet address (hostname or IP address) set to "wh2.abon.us:2321". Since that is not a valid hostname or IP address, that would fail the verification attempt. The port number (in your case 2321), goes in a separate property/field. I see that now your entry has the address set to just a hostname without the :port, so perhaps tonight's auto-verification of your BBS entry will succeed. We'll see.
quick question about this, could I being to failing validation because binkp.net doesnt see my bbs in the nodelist?
I only ask and discovered this
because while trying to help someone else with a bink problem found that binkp doesnt see either of my BBS's, when pinged it reports that neither of them are in nodelist.286 however latest nodelist.283 shows both in there? Anyhow I know this isnt a binkp echo I just wondered if it was possible that issue I was having getting verified could be linked to that?
Re: sbbsimsg
By: Rick Smith to Digital Man on Mon Oct 12 2020 06:31 am
because while trying to help someone else with a bink problem found
that binkp doesnt see either of my BBS's, when pinged it reports
that neither of them are in nodelist.286 however latest
nodelist.283 shows both in there? Anyhow I know this isnt a binkp
echo I just wondered if it was possible that issue I was having
getting verified could be linked to that?
No, not relation. In fact, your system is not in the imsg list as of midnight.
No, not relation. In fact, your system is not in the imsg list as of midnight.
It appears to be working now.. So all is good? Thank you for your help, that is a slick feature.
| Sysop: | Rempala |
|---|---|
| Location: | Richlands, NC |
| Users: | 106 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 40:06:00 |
| Calls: | 205 |
| Files: | 6 |
| Messages: | 111,121 |